Add player select permission for tokens

New to roll20, but a programmer and already looking at ideas for scripts. I am confused by the apparently limits of the token permissions, currently I have the option of allowing my players to either see or edit tokens. I'm really hoping someone will correct me and this functionality has just passed me by, but every forum post (and my own experiments) seem to show it's not currently possible. I am suggesting that a third token permission be added to allow player selection of tokens. This would not give the player any change to the existing behaviour as far as token UI or control (so no pop up bubble or options on selection, or ability to move the token, instead just some simple UI to show the token is selected) This would give a UI centric way to allow players to use macros, GMs to add scripts and macros and more importantly, script editors to add all sorts of useful features to allow more automation of combat and easier interaction between players and gm controlled tokens. This setting should obviously be scriptable, and possibly have some kind of global settings page options to either disable or enable by default for new tokens. Combined with my other suggestion ( <a href="https://app.roll20.net/forum/post/8785148/gm-controllable-token-types-with-default-permission-settings" rel="nofollow">https://app.roll20.net/forum/post/8785148/gm-controllable-token-types-with-default-permission-settings</a> )&nbsp;of settings templates based on GM configured (and possibly some default) token types, this would easily allow for different types to be made selectable for different types of tokens. Some ideas of things that would become far more user friendly: * Targetted combat scripts - Rather than forcing the need to for players to type the name of tokens to target enemies in combat, players could just click on their tokens and macros and scripts could use the "selected" option to reference, let the script editors (of which I will probably be by the point this would be implemented) loose with this and the scripting options would be expanded considerably! * Targetted chat macros, click token, click macro - the macro can be written to then target the person firing the macro and the token they have selected (much as GMs can already) - gives more options for providing easy, intuitive macros for players. * Other targetted scripts - the options here are pretty wide, easier interaction with scripted tokens for roleplay, traps, skill checks (really the imagination of the script author would be the limit ;) ) Whilst all this is already possible, an easy reference, provided via the UI from the players to a target would (from a quick glance) make things a lot simpler than it is today?

Are you familiar with the @{target} feature? <a href="https://wiki.roll20.net/Macros#Using_a_Targeted_Token_with_a_Macro" rel="nofollow">https://wiki.roll20.net/Macros#Using_a_Targeted_Token_with_a_Macro</a>

Rabulias said: Are you familiar with the @{target} feature? <a href="https://wiki.roll20.net/Macros#Using_a_Targeted_Token_with_a_Macro" rel="nofollow">https://wiki.roll20.net/Macros#Using_a_Targeted_Token_with_a_Macro</a> I am, and in my opinion it just feels like an unnecessary UI step that this simple change would prevent the need for. Happy enough to use it, but really don't see why we can't have a flag to just let players select certain interactable tokens without the extra step :) I can think of a number of applications where being able to use selected (especially with scripting callbacks) would allow for much nicer interactions for things like&nbsp;scripted levers or secret doors and interactable puzzles to allow interaction just from a player clicking on a thing. Maybe just personal taste, but figured it was worth an ask!

Rabulias said: Are you familiar with the @{target} feature? <a href="https://wiki.roll20.net/Macros#Using_a_Targeted_Token_with_a_Macro" rel="nofollow">https://wiki.roll20.net/Macros#Using_a_Targeted_Token_with_a_Macro</a> The target feature is very bad, have you seen how Foundry target system is superior?&nbsp;

I still do not see the distinction that this suggestion makes. What are you looking to do with this suggestion that @{target} cannot do? The one limit I would like to change with @{target} is to make it easier to click and apply to multiple targets, but @{selected} is limited to a single token for now.

I guess there's not much I can't do with target, I just feel the UI would be nicer if it were the other way around, as I say, this would also allow far more simple point and click interaction from the players, with the ability to script default callbacks on selection of a token with no need for the player to click anything else first in order to target them. It's more a convenience and UI tweak. My guess is that the UI changes to remove the bubbles for non-editable tokens would be non-trivial and that's probably why it's not been done. Given you mention multi-target, it would be easier to support that (given the UI already allows selection of multiple tokens, it would only be the selected selector that would need to change) compared to target, which would need to be entirely updated with changes to both the UI and the behaviour of the target selector itself.