RPTools.net

At one point while working on a Framework, I renamed a token property (which had been modified on a few tokens); immediately upon doing so, I got an input box (which never fully loaded, so I could never see its contents) which said "Input Value for Hydra" (the selected token).

If I tried to X out of the box, it would just come back, and having done this several times, sent me a Warning (which also did not load and I could not, therefore, read).

Eventually, I was forced to force the program to quit, and when I reloaded (and launched the autosave), I got the exact same problem.

If Maptool didn't automatically delete the autosave, I could have provided the faulty framework so that the error could be reproduced easily. Unfortunately, because Maptool deletes the autosave as soon as it's loaded, I no longer have the faulty framework or a great deal of work I did on it.

However, I did have the presence of mind to take a screen shot, and have attached it.

I'm inclined to think that the bug is related to renaming properties. What is supposed to happen when you rename token properties?

Boy it seems lately that whenever someone does something that violates one of Maptool's code rules and it causes an error, it has to be a bug.

I've gotten this same error a half a dozen times when I drop a token made in Veggiesama's framework into a campaign with DevNull's framework.
I assume and someone correct me if I'm wrong that the error is caused by properties having the same name between frameworks.
I've found that if I patiently click cancel umpteen thousand times it eventually stops throwing the errors. I then open up map explorer find the offending token and delete it.
After that all is good.

Well, I'm still learning; you seem to know a bit, so I'd appreciate some help:

Which code rule(s) did I violate? Don't rename properties?
I got this error while working 100% in a single framework; not a single thing from a different framework was involve (be it a token, code, etc.)

I gave a good few-dozen clicks to the error messages, but they showed no sign of stopping or changing, so I assumed it had something to do with the input value I was expected to provide (but could not see how to). Does it help to click more?

On an unrelated note, is it possible to change Maptool's setting so it doesn't delete the autosave on load?

After thinking about it, I might possibly know what caused the error.

I had renamed one property, but another property had been defined based on the previous name of the renamed property.

However, that doesn't explain why it kept asking me to input value over and over again for the same token...

Well the rule I was referring to was not duplicating property names. Every property ever set on a token stays even if you change the name.
For example if you have a property called HP and change it to MaxHP. Your token will still have the original property as a hidden property.
Recently the resetProperty function has been modified to wipe out or set to default a property hidden or visible.

I use the following little code to erase a token created in one framework for use in another.



Remove the resetProperty line to get a list of the property on your token.

PS. I'm just a moderate code dude, guys a whole lot smarter than me will probably post a better answer.

You may want to post the campaign file. Generally speaking, it looks like you're stuck in an infinite loop somehow. I'm guessing if a variable reference itself A = [A] or A = [B] B = [A] or if you have a frame open that uses onTokenChange or you have a stat box property that calls a macro or some variation of the above.

You can manually change a campaign property in the XML to probably fix it.

Unfortunately (or fortunately), the version of the campaign file I have doesn't have the problem.

There is a known issue properties that are defined as viewable when you mouse over the token, it maybe this that you are running in to. If you have one of these that has no value it prompts you, but the toke loses focus, then you move the mouse and maptool says hey mouse over token bring up stat sheet, and you get a prompt,and then you move the mouse and I bet you can see where this is going. Unfortunatley this is a limitation of how certain things are done and is unlikely to be fixable in 1.3. The solution/workaround though is proerties that can be displayed on mouse over should always have a default value. This also goes for any properties that are used in an equation or macro called in the default value of another property.

What Craig said. It sounds like you inadvertently renamed a property upon which another visible-on-the-stat-sheet property depended. When that happens, suddenly there's no value for a needed property, and MapTool will wig out when you hover over the token.

The only real solution is "Don't rename properties unless you're willing to go find every instance of that property name in all the macros." Especially in a framework, which, despite being nifty, are very fragile about things like that - it has no way to know that "HP" is now "CurrentHP" or whatever, unless you also recoded that.