[Script] !reveal command

This is a chat API command I made that finds objects by "class", then moves them to the objects layer:

https://gist.github.com/rlittlefield/5493842?1=5

Usage: !reveal foo bar

or: !alter foo bar > {rotation:24.1,aura1_radius:5, aura1_color:"#44FF00"}

Will find every object on the player page, and move it to the objects layer if the name of the object has a class in it. It would be super helpful if we could tag objects with some kind of metadata for the API (like class), which would make this sort of script even more trivial, and could make things much faster. Once the "state" object is persistent between sessions, it could also be used to track items. It would be nifty to make something like !addclass Name Class, which could then find the object id by name, then add it to a classes variable on the state object.

When you type !reveal foo does that show up on chat to players? These scripts are just gonna create a bunch of spam if we can't use hidden commands.

!commands (any command starting with !) will not output to the chat, unless you specifically tell the Javascript to have a chat output. So the answer is: not in this case, because he did not add chat output to the code.

Yes, it should currently hide the command. I've just updated it to have a handy function for getting items by class, added "conceal" and support for command aliases (hide, show). If I can figure out how to get the embedded gist to update, I'd show it.

Update: I tricked the embedded gist into updating. I think this new version should be somewhat more robust, and could be a fun starting point for building a few commands to operate on groups of graphics.

Riley D. said:

Oh, also, for the gist updating, in theory it should be pulling the latest version from Github on each page reload, was it not doing that?

I just added a "!revealrandom", which picks a random graphic matching the class and that is currently on the gmlayer, and moves it to the objects layer. Maybe useful for when you can't decide which enemy attacks first?

Riley D. said:

Oh, also, for the gist updating, in theory it should be pulling the latest version from Github on each page reload, was it not doing that?

I've added some additional functionality. You can now do a command like:

!alter foo bar > {rotation:24.1,aura1_radius:5, aura1_color:"#44FF00"}

Using this script you could write some macros to perform basic alterations to the tokens, so some automation stuff could be possible by anyone with access to the API and the skill to write a macro. Admittedly it would never be as automatic as an event handler in javascript, but if you wanted to script actions based on the press of a button, it could be nifty.The above example rotates everything with .foo or .bar in the name, and adds a green aura. The syntax is fairly specific (no fancy parsing), so even things like extra spaces would probably break it.

Update: I'm now using the frowned-upon "eval" function on everything to the right of the ">", so it should be more forgiving of the property syntax now.