demonnic wrote:Not sure, but I may have found a bug in the input() function. I noticed today while editing my macros for skill usage that if the token name was "Grum" then it wouldn't read the token properties into the varFromStrProp() function, but if it was "Grum " (yeah, that's a space at the end) or Grum with anything after it, it would read it fine. The Grum here is unimportant, I tested with all my tokens =)
Could you explain this in more detail? I don't really understand what you're describing, so I'll need some help.
- Is the bug in input() or varsFromStrProp()? The two functions have almost nothing to do with each other.
- The varsFromStrProp() function doesn't read from token properties. Are you saying that it doesn't write to token properties?
Strange that MapTool will allow you to give your token a name that ends with a space. That should probably be changed.
If you can give a sequence of steps that reproduces the problem, beginning with starting up MapTool, that will be very useful. For example, I just tried this:
- Start b45
- Drag a token on the map
- Edit Token: Name it "Grum", and set its HP property to 20, AC property to 30.
- Impersonate the token
- Type [varsFromStrProp("HP=5; x=3;")]
Result: The token's HP property changes, as expected.
There is one issue that might be causing confusion. If you rename your token while impersonating it, the Impersonate panel does NOT refer to the newly-renamed token any more. You can even delete the token entirely, and the Impersonate panel will still happily tell you you're impersonating someone who doesn't exist, and even let you run macros from the deleted token! Note that the chat window also thinks you're still impersonating the old token.
So if you were playing around with renaming tokens, this might have been involved in what you were seeing.