Orchard wrote:I get the same (essential) error for setInitiative(), so I think there are some problems EITHER with my implementation or the function list. What's going on here.
Jay, if you could clarify these, it might help.
The setInitiative() function is only available if there is a token available (token macro etc.)
Okay, this is definitely a bug.
If you have multiple tokens with the same PC name, and use the setInitiative() function like such as a token macro:
Code: Select all
[P:token.name] has initiative of [Init = 1d20]
then you can get some strange results. Here's exactly how to replicate this.
Take a token (the troll from the default library is a good choice). Put it on the map, then add the above as a token macro. Duplicate the token numerous times, then add all the duplicates (but not the original) to the initiative list. Select any one of the duplicates and run the macro. You get this error:
Code: Select all
Could not execute the command: The token is not in the initiative list so no value can be set
Delete the original, select a random one of the duplicates, run the macro, and it SEEMS to work. This is deceptive BECAUSE it is simply firing on the FIRST duplicate. This is actually very easy to test by creating the duplicates with incremental numbering, then watching as this happens. If you keep deleting the duplicates in the order they were created it will cascade down the list. At NO TIME can you actually use this to set the initiative of more than one of the duplicates, even if they are all in the initiative panel, which is very frustrating. The ONLY way to set the initiative of multiple tokens is if they all have unique player names OR to do it manually.
I'm filing this as a bug, since it needs to be possible to do this for large-scale battles. I don't mind setting unique player names for 3-5 monsters, but if you are fighting a horde of orcs, there's no way. Or a legion of undead skeletons? Not only no thanks, but it doesn't make sense--they conceptually wouldn't have different names.
And formians really are nothing more than Formian Worker #3423. I'm sure this applies to other games as well. Thanks.
0+0=1, for very unstable CPUs.