RPTools.net

The above will work; If may make a suggestion though in the [C: n ; ] syntax I don't think that the C: is needed. I think any [ ] starting with a number then; (or . or what ever delimiter) could be taken as roll n times as long as its not ambiguous. See Lindharin's quote below. [D; ] while nice, is...

Okay, assuming we go with knizia.fan's proposal (which is not a given at this point, but it seems to be popular), here's what we've got: [ ] gets the new tooltip behavior. Just shows the output of the roll, blue text, light grey background. When you mouse over it, you get a tooltip showing the full ...

1. Having a tooltip on something no one is going to mouseover isn't that big of a deal. Well, as currently implemented, tooltip rolls are colored blue and have a light grey background, same as expanded rolls (so that you know that you can mouse over it for the tooltip), so it's not just that they h...

Yes they will. Any macro using { } as it is right now is a potential source for cheaters to cheat with. In addition the inclusion of tooltips will force pretty much everyone to rethink how they want to craft macros since they can use tooltips now. A few points: first, not every macro that uses { } ...

How about a chat checkbox that shows the whole forumla for [] or hides it and makes it available via tool tip? The reason I like this is that it allows you to debug easily but gives you the option to hide the clutter. Desirabiliy of this feature aside, implementation would be... interesting. At lea...

Regarding the pipe | character, I suggested it because I think it looks good between the [ and ] characters. But I agree with folks that a shifted key is slightly more annoying, and of course most normal human beings don't even know that the | key even exists! I suggested the semicolon as an altern...

Holy crap, this post exploded. Here are a few comments while I wait for the dust to settle. Okay, so. Yes, we need all three types of roll semantics. I was wary about changing the behavior for { }, but that seemed to be what the community wanted. Now that more of the community has weighed in, I thin...

Okay, I've sent Trevor the updated patch. { } uses the new tooltip behavior, {{ }} uses the b40-and-earlier { } behavior.

I suppose it could make sense for { } to have the tooltip and {{ }} to inherit the current behavior of { }, as long as Trevor's okay with changing the default behavior. I'll see about throwing together a new patch tonight or tomorrow.

I did initially just modify { }, but there are circumstances in which you don't want the full expansion (sometimes it's just not necessary, sometimes you don't want the expression to be visible—for example, DMs may want to display results without exposing all of an NPC's modifiers). Also, by creatin...

The <span title="whatever"> is seperate from the [[ ]] syntax (and behind the scenes, the latter is implemented using the former). So just typing <span title="This is a tooltip!">Some text here</span> will give you the text with tooltip, while typing [[d20 + StrBonus]] will give ...

My group and I have been wanting a way to keep macro output concise while still being able to see detailed roll breakdowns. To that end, I added tooltip support to the message frame and added a new syntax for rolls. (I submitted a patch to Trevor a few days ago but haven't heard back; I assume he's ...

I was actually discussing the drop-down idea with another member of my campaign today, before coming across this thread. I had come up with a couple ideas: [var = {"foo", "bar", "baz"}] [var = {"foo" : 2, "bar" : 1, "baz" : 3}] The first on...