RPTools.net

I believe there's a slightly simpler and equivalent macro you can use. If you roll N dice, and M of them are sixes, then each of the N-M dice that were not sixes have (had) equal probabilities of being any of the other numbers 1-5 (equivalent to rolling a d5). So you should be able to do simply: [h:...

I'm not sure, but I'd also guess that the die is re-rolled exactly once, rather than being rolled over and over and over again until the result is higher than the given limit. That means that rolling a one is perfectly possible, but a bit less likely.

I was thinking about the problem of movement out-of-turn and auto-reveal and such, and an idea struck me. MapTool can currently display the path a token followed when it LAST moved. What if, instead, it drew the path that a non-GM player PROPOSES for movement as well as the length of that movement (...

You can also turn of auto-reveal. That requires a little more work and doesn't keep the players from moving their tokens out of turn, but it does allow you to control the worst consequences of bad movement (revealing too much too soon).

Some operating systems only allow unprivileged processes to listen to ports above a certain value, restricting the lower ports for their, "intended uses," by system daemons.

You can also refresh a [dialog:] or [frame:] each time you add another die to the pool with a button or link, showing in a text label/field what has thus far accumulated, and hit an "execute" button on it when ready to let loose.

There are also the drawing tools, so if you don't mind improvising a quick and dirty sketched map, you don't have to try to plan out absolutely EVERYTHING ahead of time.

Well, probably you'll want to keep lists of what player is in what "room" in a property or properties of a library token. A frame can display the lists and give buttons or links or whatever that will execute a macro to pop up an input or dialog to enter a message to send to a particular ro...

Getting hands on a list of the cells ins the last path would be great. This would really improve the uses of this. Agreed. For a map without the grid, it could return just a list of the waypoints. Maybe that's not a bad idea for a map WITH the grid too, to keep a HUGE list from being returned and s...

I think you'll want ">1" instead of ">2" in this part:

mfrizzell wrote:

Code: Select all

if(AttackRoll >2 && AttackRoll<20)...

You could also select the attacker and all targets and then have the macro query which one is the attacker through an input dialog (if the user isn't a GM, the macro could allow them to select among only those tokens he/she owns, and if he/she own only one of them, the input wouldn't even be necessa...

Macros could also be used to create "rooms". Visualize a dialog that shows a choice of rooms, with a list of the players in each room. A link or a button allows you to enter a message to send to the room you are in (or perhaps to any room), thereby sending a whisper to all appropriate play...

It's just a name. Pretend it's called "default" rather than "basic". Then put whatever you want in it.

Any possibility that the vision blocking layer isn't what you expect? Did VBL get confused with FOW at some point maybe?

You could also try using Wiki: execLink() on a macro link constructed to use the desired token as the active one, instead of using [macro:].