RPTools.net

Post your code and I'll take a look.

Yeah, it's a bug. Unfortunately it's not entirely straightforward to fix, but I'll work on it.

I'm working on a fix, but it looks like I'll have to make some modifications to the parser library. Should have a patch sometime this weekend.

Yeah, the new options aren't supported in the statsheet. At some point I may evaluate the possibility of changing that, but for now they won't work.

The chat parser isn't catching the roll for some reason, so it's displaying it literally, header data and all. Can you post exact steps to reproduce this? I'm not seeing the same behavior.

Just for clarity... Is it possible to do a varying level of detail output on the same roll? e.g. gm sees "A attacks B. Roll is 3 vs. skill 15. Success by 12. Critical success" player sees "You hit B with astonishing authority!" other players see "A hits B." Well, you c...

Documentation has been added to the wiki.

* Updates: [s: ] - only display to self [g: ] - only display to GM [w("name"): ] - only display to specific player [st: ] - only display tooltip to self [gt: ] - only display tooltip to GM These can be combined, so, for example, the output of [s,g,st: ] would appear to yourself and the GM...

These should be in b58, which Trevor claims will be available next week.

Wow, apparently I started a trend of developers suddenly reappearing after being gone for over half a year.

I just checked and it's working fine for me. So you have: A library token (name begins with "Lib:") On this token, a macro called CharSheet_css that contains the CSS On the same token, another macro with the code to generate the character sheet and running that macro creates the character ...

Okay, the patch has been sent off. In addition to [s: ], [g: ], and [w(): ], I added [st: ] and [gt: ] for tooltip visibility. [w(): ] can be used in a few different ways: [w("name"): d20] [w("name1", "name2"): d20] [h: names = json.fromList("name1, name2")][w...

/me casts Thread Necromancy So, uh... hi again! I guess I kinda disappeared there for a while, and so the parser changed rather drastically. (Nice job k.fan, by the way; it definitely needed to be cleaned up, and it looks a lot nicer now.) So, after getting things figured out, I redid and finished t...

Hmm, /discard must not have made it in yet. Should be in the next build, I suppose.

Try adding either /discard or /do to the beginning of the macro; this should execute it without displaying any output.