Tokens are "system agnostic". That is, there is nothing "5E-centric" about bar1, bar2, bar3, or bar4; nothing Pathfinder-unique about auras; and nothing Champions-only about status markers. All of the basic properties of a token are functional no matter what system you're playing. Character sheets are where things get system-specific, so the only implications that matter for tokens come in when you link bars to particular attributes on the character sheet... but even then the act of linking the bars or the act of modifying the bars is all universal. The act of giving sight, providing light, designating how much light and in what direction... all of that is universal. What I'm trying to say is that TokenMod is, itself, system agnostic. Your macros from 5E should work in a Shadowdark game... PROVIDED... ...you interact with the VTT in the same way (if the macro requires a selected token, you should have a token selected when you run it) ...you change any references to an in-game resource to match a resource actually in your Shadowdark game (e.g., changing a token-ID that references a token in your 5E game to point at one in your Shadowdark game) ...you perform any necessary extra-script setup your game requires (ie, setting up maps for dynamic lighting, enabling macros to be run by players, etc.) If you get that far (copying over a TokenMod command line, making sure things are set up properly, and running the command) and there is still a problem, then there's probably a base reason we can help you discover and correct.
