Access Status Marker values in macros

It would be great if we could access the value of a status marker in a macro. That would let you give token specific benefits without needing to prompt constantly for a potential bonus. Something like: /r 1d20+@{selected_status|blue} While I can duplicate this functionality with an API script, it would be so much more useful if character sheets could take advantage of this directly.

That's a pretty neat idea! A lot of people don't realize how to set the number on a statusmarker, though -- but that's an issue of training. If it's implemented, I do think that a statusmarker without a number on it should count as "1" while absence of a marker counts as "0"; that would let you use the markers as a flag in addition to using it as a simple number, eg /r 1d10 + @{selected_status|blue} * 1d6

Ooh! Totally agree.. (adding that to my notes on a script to do just this...)

Could have and extra qualifier: /r 1d10+@{selected_status|blue|on} * 1d6 Results in 1d10 + (1 * 1d6) for having the marker, 1d10 + (0 * 1d6) for not having it Then have: /r 1d10+@{selected_status|blue}d6 just using the value from 0-9.

I don't think the 'on' tag is necisary. if you want it to have a !blue functionality, then you could just make it: (1-@selected)status|blue})*d6 That way, if it's 'true' it becomes 0 and if it's 'false' it becomes 1.

One thing to note is that status markers are specific to tokens and not characters, so it would have to be tied to the @{selected} token in the current sense, unless there was a way to introduce keeping the status markers at the character level similar to the way the bars can be tied to representing an attribute on the character.

Epsilon, Brian is talking about the fact that turning on a status marker has the value of 0. What you've got would (ostensibly) be true if the marker was either missing or set with no value (0), but not if it was set with a value of 1-9. The best indicator of this relation ship is from the API docs: obj.get("status_red"); //Will return false if the marker is not active, true if it is, and a string (e.g. "2" or "5") if there is currently a badge set on the marker

Aaron said: One thing to note is that status markers are specific to tokens and not characters, so it would have to be tied to the @{selected} token in the current sense, unless there was a way to introduce keeping the status markers at the character level similar to the way the bars can be tied to representing an attribute on the character. @{selected} is tied to tokens already, it simply lets you tunnel into the character that token represents, if there is one. @{selected|token_id} and @{selected|character_id} are both valid values, for example (assuming the token is representing a character).

Yeah. I was just thinking about the possible confusion if you set a status on your character on one page (with the intent to use it in a macro), but then it isn't propagated to another. With @{selecterd...}, you're generally getting a value for a character or getting from something that could be backed by a character. (Like a bar) Since there is no way to have the statuses "represent" statuses on a character, this is a deviation from past conventions. A conceptually simple way of handling this would be to add represents as an option for status markers. I wonder if that automated status tracker API script has that problem.

The status tracker script (at least, the one I use) simply updates whenever the token changes; that includes movement.

Yeah, can't explain it... I think the ToFront() is being preempted by the set in the status script.

Whoops. Totally thought you were replying to another post I made. Pardon my crazy. :)

+1

It would also be most effective if you could set them to negative values as well as positive.