RPTools.net

Being able to select Text or Corner Text as the Type for a State does sound like a nice addition, especially if the text could be changed through macros.

Pretty sure roll options aren't case sensitive.

You don't need port-forwarding if you're not running the server, which it doesn't sound like you are. But you need to provide more information about what exactly you are doing and how you're doing it. 1) Were others able to log into your GM's server? Yes hers now works 2) What OS are you using? Win...

I feel cheated.

I recruited two allies, then went on a hunt.. and got my butt handed to me.

The default separator for [count:] is a comma. You'll need to tell it to use an empty string as the default separator if you don't want anything separating each iteration.

palmer wrote:Plus Google gives MapTool the respect it deserves.

Honest query: What sort of information would you expect WA to give you about MapTool?

Okay, I created a new campaign and then a test token. I set the value of that token's Strength property to the following in an attempt to make it a little "meatier" Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam nonummy nibh euismod tincidunt ut laoreet dolore magna ali...

Just go ahead and use getProperty( prop, id ) and setProperty( prop, value, id ) every time you're working with token properties, and you'll feel much better about it. :D On a tangent, what kind of performance do you see when using get/setProperty()? I rebuilt my framework for D&D using get/set...

I just tried your updated code, and called it using [r: Attack()] and it worked exactly as it should. /shrug

Ah okay, I see now. There are a couple things of note going on; first, when you call your custom dice() with something like dice(1d6) your custom dice() isn't doing anything besides returning the result of the 1d6.. as in, it's not even rolling, that occurs just before the function is called. So, us...

EDIT: Decided not to derail this thread.

In the code you posted, the default will be whatever value the variables Intellignce, Strength and Presence contain.

The problem is 'layered' tooltip data. When you have a macro call [Attack()] it's giving that roll it's own tooltip/expanded output, and there are rolls inside Attack() that are creating their own tooltip/expanded output. Try using [r: Attack()] when you call it.

You could create a user-defined function, or you could just do something like this: