Roll20 uses cookies to improve your experience on our site. Cookies enable you to enjoy certain features, social sharing functionality, and tailor message and display ads to your interests on our site and others. They also help us understand how our site is being used. By continuing to use our site, you consent to our use of cookies. Update your cookie preferences .
×
Create a free account

Combining Combat Master and Tokenmod Inconsistancies.

I am trying to use a combination of Combat Master and Tokenmod to allow players to place conditions on Enemy tokens. I can set up the Tokenmod Script to place the status marker on the token. I can add the specific status marker to Combat Master. The problem comes in that when I use one of the standard status markers such as the blue circle it transfers the  status marker to the one set up in Combat Master giving the proper count down and announcement in chat when it is that token's turn.  However when I try and do the same thing with one of my own status markers it doesn't work, it puts the status on the target, but doesn't convert it to the Combat Master one. I've checked that all the names are identical, number of rounds is identical, but it still isn't working for my own status markers just for the standard ones. Has anyone got any ideas on why there is the difference,  how to sort it out, or a way for Combat Master to allow a player to place a status marker from its menu onto a target token (but not onto their own) Thanks in advance for any help.  If it didn't work at all I could understand more than if it worked for some status markers, but not for others.
If I'm not mistaken to use other status markers in combat master you need to change the icon setting for the condition to Token Marker, if is set up to Combat Master it will only see the default markers.
I can set up the markers on Combat Master no problem, and using Combat Master they work fine.  The problem comes when I try and apply them using the targeting option in token-mod, it applies the markers fine, but the standard blue dot then transfers to the Combat master set up, counting down with the turn order, but the markers I’ve created don’t seem to be recognised by Combat Master, even though they are set up exactly as the blue dot is in that API.
I’ve not found a way for a player to put a marker on a token they don’t control with CM, they can only put it on a token they can select, or am I missing something.
1753135595
timmaugh
Forum Champion
API Scripter
I am not sure how CM handles applying markers, but if it is a matter of being able to select the marker and you want to get around that, you can install the Metascript Toolbox and then add this tag to your command line: {&select @{target|token_id} } That will replace your batch of selected tokens with the token that you choose through the Roll20 targeting interface.
Thank you, I'll have a look at that. Normally CM just applies the status to the token you have selected which is no good for players putting a status on an enemy token.
I've added Metascript Toolbox, and come up with this command This is the basic command that CM goes through to put a marker on a token !cmaster --add,condition=vuln 2,duration=?{Duration|1},direction=?{Direction|-1} Changing it to  !cmaster  {&select @{target|token_id}  --add,condition=vuln 2,duration=?{Duration|1},direction=?{Direction|-1} makes it ask for a target, go though the duration and direction queries, but then it doesn't add the status marker to the token. It seems like it is missing some little bit to make it work.
1753297139
timmaugh
Forum Champion
API Scripter
Looks like you're missing a closing brace: } Effectively you're using a SELECT tag: {& select } ...and putting *into* that the tokens to select (by identification or criteria). So both the targeting statement AND the SELECT tag need a closing brace: !cmaster  {&select @{target|token_id} } --add,condition=vuln 2,duration=?{Duration|1},direction=?{Direction|-1}
1753298498

Edited 1753298534
I'm an idiot, you were right, I had missed the second closing curly bracket that works perfectly now. Thank you.