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

Macro FX

March 06 (3 weeks ago)

Edited March 06 (3 weeks ago)

Hello

I try to make simple macro but it seems I'm wrong as my macro don't work well !

/fx glow-charm @{target|token_id}

This is an easy macro. But I cannot target a token that is under my control (cliquable token). I don't understand why :(

Do you have some insight ?

Thank you !

EDIT :

As DM, this macro is executed perfectly

As player, this macro is executed perfectly if I can select the token. It's failed if I try to target an other token that I cannot selected,


March 06 (3 weeks ago)

That macro works for me but you have to click a token after you execute the macro command. This one here you click on the token first then run the macro.

/fx glow-charm @{selected|token_id}

March 06 (3 weeks ago)

Edited March 06 (3 weeks ago)

How can I do to have the effect on a token that I cannot selected : ennemies ?

I have modify my first to include this specificity.

March 06 (3 weeks ago)

Try installing TokenMod and check the "Players can use --ids" in the API page of the game.

March 06 (3 weeks ago)
timmaugh
Pro
API Scripter

Sorry, Surok... that won't change the /fx behavior.

The "players can use --ids" setting for TokenMod only applies to commands intended for the TokenMod script. When the script runs, it tries to make sure you have the rights to do what you're asking it to do to the tokens you have indicated. If you are using selected tokens, it knows you have access to control them, so everything works. The reason to need the --ids argument is to specify tokens that you *can't* select (there are other reasons that make it nice to have this argument, like being able to execute a command without having to select the tokens, but those are just value-adds; the necessity for it is to reach tokens you can't select).

Since we're talking about tokens you can't select, we're talking about non-GMs (or players). So this is TokenMod's way of letting a GM specify whether to let their players use this argument... but, again, it's *just* for TokenMod commands. It will not affect anything else.




I don't have a ton of time to investigate this, Ombres, but I think what is happening is a z-order problem with the effect. The "glow-charm" effect is sitting behind the token you "control", and it's so small that you don't see it because the token is in front.

To test this, try this command, instead:

/fx nova-frost @{target|token_id}

Target a token where the glow-charm command doesn't seem to work, and see if you see the frost effect. That effect will be big enough that even if you select a token you control it will expand beyond (at least beyond a 1x1 square) so you should be able to still see it.

March 06 (3 weeks ago)

You don't need TokenMod to be able to call @{target|token_id} from tokens you don't control. I tested the macro in the OP and it works on tokens I do not control, and on tokens I do - though the effect is beneath the token and hard to see in legacy VTT, especially if there is a health bar above the token. I suspect the effect being under the token is unintended behavior, but regardless, the macro as given in the OP should work on all tokens. However, if you're using a Beacon sheet, that complicates things - I tested this in legacy VTT and Jumpgate, and Jumpgate with the 2024 D&D beacon sheet. In the last case, the sheet refuses to divulge token_id from the target if it's not controlled by the player.

March 07 (3 weeks ago)

Edited March 07 (3 weeks ago)

@Timmaugh : I had tried with nova-gel and this is the same. In the chat, I have this message :

@Tuo : Yes, I use Jumpgate and 2024 D&D beacon sheet (but on 2014 rules if that change something) :(

March 07 (3 weeks ago)

Edited March 07 (3 weeks ago)

Yeah, there's your issue, the beacon sheet is crud. Switch to a non-beacon sheet (like the sheet that I consider vastly superior in every given way, the 2014 D&D 5e by Roll20 sheet) and it'll work just fine.

Roll20 work on balise on beacon sheet ? Or not ?

In term of design, I prefer the new one :(

March 07 (3 weeks ago)

The macro you're using relies on an attribute call (specifically a pseudo-attribute), Beacon sheets do not support attribute calls by default and the support implemented in the 2024 D&D sheet is lacking, as evident here. As there is no real other way of accessing the token id, in short, the 2024 D&D sheet does not support the fx tool.

March 07 (3 weeks ago)
timmaugh
Pro
API Scripter

Have to agree with Tuo RE: the 2024 sheet. This has been my view since Roll20 started offering it to the user base:


March 07 (3 weeks ago)
Gauss
Forum Champion

Ombres, in the future when asking about macros please specify which character sheet you are using (D&D 5e 2024 by Roll20). 

That will save everyone some time and effort. 

Short version is, the D&D 5e 2024 by Roll20 sheet is not ready for the kind of macros you want to use. Someday it might be, but not today.