HoneyBadger said: Riley D. said: This was a bug, it should be fixed now. What will happen if someone has a character name with the same name as an attribute? If I understand your question properly, this only applies to variables that are used in Character abilities. In abilities if you just put for example @{Dex} it's smart enough to add-in the @{Riley|Dex} part silently for you. What was happening was it was assuming that @{Dex|max} meant "character named Dex, attribute named max". I just put in a little code for the special case of "max", treat it as @{Riley|Dex|max} in Riley's character abilities. So really this would only be an issue if you had a Character named the same as an ability *and* you had an attribute named "max" *and* you were trying to access that attribute from another character's abilities. And honestly I don't think it's very common to call other Character's attributes from inside another Character's abilities, anyway, since there was a bug that caused it to be somewhat broken until yesterday and no one noticed until we introduced the @{selected} variables. If that's not what you meant, let me know.
