[Script] Custom Status Markers - thread 3

Starting a new thread, since I've updated the script, but the old thread is closed. Custom Status Markers v3.1 3.1 GMs can now set the size of the status marker icons through the script's chat menu. This script allows you to create your own status markers from any graphic you've uploaded to your library. From its chat menu interface, you can create new status markers, assign markers to selected tokens, give them a count, and even give them a tinted color. Available from One-Click installer. Demo: (Note: I haven't updated the demo gif yet from the previous version, so the new menu looks different) On the Marketplace: I'm pleased to announce the release of my new art set on the Roll20 marketplace - Custom Status Markers: The Script: The Art Pack. This contains 55 black and white (colorable through the script using the tinting properties) status icons for use with this script representing many common status conditions in several popular roleplaying games. You can check that out here: <a href="https://marketplace.roll20.net/browse/set/1841/cus" rel="nofollow">https://marketplace.roll20.net/browse/set/1841/cus</a>... Link to previous thread: <a href="https://app.roll20.net/forum/post/3574536/script-c" rel="nofollow">https://app.roll20.net/forum/post/3574536/script-c</a>... Roadmap: Import/Export saved custom status markers

Probably a good idea to call out the change in API commands. &nbsp;If users are entirely driving it with the macros, you'll want to delete the macros when you go to v3.0 and restart the API so it can make macros with the new commands. &nbsp;(otherwise, it will just silently ignore your button clicks. =D) Also, it's a small thing, but you should really check to make sure you are responding to api messages in the chat:message handler. &nbsp;Try sending this to chat... `!CustomStatusMarkersShowMenu =D I get player names from messages like this: const who=(getObj('player',id)||{get:()=&gt;'API'}).get('_displayname'); Which deals nicely with the '(GM)' problem. &nbsp;I was getting an issue for having a space in my name, but that might have been another script...

Ah... forgot about that.. I'll be sure to make it replace the macros with the updated commands in the next version.