Disable global variables assignment through webhook trigger

[Golem64]

Hello, this might seem kind of a weird request but i think not being able to set the global variables with the webhook trigger would be nice
Basically, if we need anything to be stored in variables with webhooks, we can use local variables. Global variables are more of like a persistent storage, and for a macro I'm working on it would be very annoying if users can modify global variables for security reasons.
Before this could be prevented by naming a local variable the same name as the global one so it would be prioritized, but it seems that it's now impossible to do due to a recent update
I hope you understand my point of view, thanks

 

[Golem64]

Also maybe have this as default? Generally speaking, macros that interact with the phone or other security things that uses the webhook trigger could be impacted by just a variable change, and disabling this would make things more secure

 

[Endercraft]

Since when can you set global variables with webhooks? I didn't even know that was possible... There should be an option to mark variables to not be modified by webhooks and set variables that can change directly in the trigger.

 

[Golem64]

Since when can you set global variables with webhooks? I didn't even know that was possible...

I discovered that a while ago while doing some security testing

There should be an option to mark variables to not be modified by webhooks and set variables that can change directly in the trigger.

Good idea, that could also fix the problem, it would have to be a remembered parameter even when you get the macro from the store

 

[Golem64]

Btw idk If this is the right channel where i should have posted this ? Depending on the way it is handled, it might be more of modifying an existing feature than adding a new one