Tomorrow's Update Re: Status Effect Icons and the API

This is not live for Free accounts, right?

Are there plans to give access to the API for supporters at some point?

EDIT: Nevermind, I figured out my problem... sheesh.

Quatar said: Are there plans to give access to the API for supporters at some point? They answered this on the Wednesday live chat thing, basicaly no plans atm.

Well damn... that was easy. I fixed my !mark script by deleting + "marker" in two spots. And here I was worried I was going to have to do a major rewrite.

Found an interesting bug. In my !mark script, if I type !mark target skull@10, it adds a skull without a number badge. If I repeat this command, it keeps adding skulls as shown above. This also works however, for numbers less than ten. Instead of replacing the existing badge and number, it just adds a new one. So if I were to enter: !mark target skull@1 !mark target skull@2 !mark target skull@3 I would have three skulls on the token with a 1, 2, and 3 showing.

HoneyBadger said: Found an interesting bug. In my !mark script, if I type !mark target skull@10, it adds a skull without a number badge. If I repeat this command, it keeps adding skulls as shown above. This also works however, for numbers less than ten. Instead of replacing the existing badge and number, it just adds a new one. So if I were to enter: !mark target skull@1 !mark target skull@2 !mark target skull@3 I would have three skulls on the token with a 1, 2, and 3 showing. That would be a problem with your code, its a coma separated list so if you have "skull,skull,skull" then it will have 3 skulls, you need to check the list and replace it if it exists.

Eh... I like the "bug" and will consider it a feature. Two skulls on a -10 hp D&D 4e character to mark that is has failed two death saves has more visual oomph than a skull with a red two on it.  And I don't believe it is a problem with my code, but with the backwards compatibility code that Riley put in. I'm not using the comma delimited list for setting status markers. I'm just using "status_" + StatusMarkerName in my code.

HoneyBadger said: Eh... I like the "bug" and will consider it a feature. Two skulls on a -10 hp D&D 4e character to mark that is has failed two death saves has more visual oomph than a skull with a red two on it.  And I don't believe it is a problem with my code, but with the backwards compatibility code that Riley put in. I'm not using the comma delimited list for setting status markers. I'm just using "status_" + StatusMarkerName in my code. Are you converting skull@2 to obj.set("status_skull", "2"); or obj.set("status_skull@2",true);

TargetToken.set("status_" + StatusMarkerName, true); So... the second one.

HoneyBadger said: TargetToken.set("status_" + StatusMarkerName, true); So... the second one. That's your problem it should be the first.

It's not a problem. It's a feature.

HoneyBadger said: It's not a problem. It's a feature. sure it is ....

I like it as a feature! :D p.s. Feature is what we called bugs back in the EverQuest 1 days... I am sooo old...