@Journal or @Me for character sheets

I've got two suggestions in one here. The first is more important to me than the second. My first suggestion is @me  which is simply a new keyword to automatically call for the Journal's associated character_name, akin to how @{selected} allows you to call for the token's associated character_name. The second suggestion is more class resource attributes  which would allow for linking more class resources than the default @{class_resource} and @{other_resource} @Me!!! To preface this, this could have been already implemented somehow without my knowing, but it is my finding that this is not a feature yet.  My conundrum is this: I have created many strange macros built within character sheet attack buttons due to the ravages of homebrew, and as DM it is annoying for me to continuously click from one token to another just to call for that character within the macro . I have been trying to make efforts to make things run as quickly as possible both in sessions with my friends, and the time I take to make sessions on my own time. I don't want to waste time moving a character sheet out of my way just to click on the corresponding token, if I am clicking on an attack from a character sheet (I don't like the clutter of an ability filled screen), it would be massive for it to simply use that character sheet's character_name as the target for the macro. There are two main reasons this would help me a LOT. 1) I could easily copy fundamental macros to a multitude of characters without having to change the character_name within each macro, saving me a lot of time when creating characters that have similar setups (I won't delve into the horrors for your sake.) 2.  It would allow me to circumvent the @{selected} issue of having to physically waste 2-10 seconds finding and clicking the correct token, which adds up when you have a lot of characters fighting in a big battle at once. This is definitely more of a DM problem than not, but even my players have mentioned annoyance at having to click their guy to have their attacks work. More Class Resource Attributes! It would be useful in my game if we could call to other "class resources" rather than just the attribute {class_resource} and {other_resource}. I've got a lot of homebrew things that we track, some of them being used in weirdly convoluted macro-esque abominations I have created. Being able to have a quickly modifiable class resource that I could use as an easily accessible attribute would be (and is) very helpful, because I wouldn't have to be limited by just two options for this purpose. Unnecessary context: one of my characters has a homebrew mechanic wherein his damage varies based on Output and Strain. I have turned many of his character-sheet attack buttons into macros basically, and they call for his Strain and Output to determine damage. The fact that both his Strain and Output have to take up these class resource spots means that Mana and Fire points (more homebrew stuff), have to be on attribute-less spots, I can't link them up to the token for easy editing. I could put the Strain and Output as a custom attribute in the character sheet, but then I have to dig around the attribute list to find the dang things- which defeats the entire purpose.  Final Note: Please 😭

Hi JoshyBoi T.,  Regarding the "@me" how would the system know which character is the one you want?  Without using the character's name, or selecting a token that is linked to a character there is no way for the system to know which one you want.  Regarding "class resources", there are more, if you hit the + button it creates additional resource lines. You may also use those in macros (and I do so regularly). Here is the link that provides the names of those.  Summary: @{repeating_resource_$0_resource_left} or @{repeating_resource_$0_resource_right} Where 0 is the first line below the "Class resource" line. 1 would be the second line, etc.  Regarding the problem of moving character sheets out of the way, I use popped out sheets to deal with that.  Ultimately, this sounds like a perfect situation for Token Actions. Click a token, the macro appears as a token action. You cannot not have it selected, and using a Macro Mule means I don't have to duplicate the macros on every token in the game (assuming I am not using Token Action Maker to make them, which I do).

I appreciate the information about class resources, thank you. The @me thing would just use the character sheet itself as the method for knowing which character to use. Since I'm clicking the attack *from the character sheet itself* I feel like it wouldn't be impossible to create a function in which it can actually tell where the attack is coming from in the first place. So rather than it being that you select a token and that token points to the character sheet, it would be you click an attack from the character sheet and it keeps track of who that attack came from . I don't like how Token Actions appear and I have a lot of attacks I don't want to port over to a token action. This is just one character, I've got like 15 I'd have to do this for. Maybe for many people an @me function is unnecessary since I'm probably one of an extremely few people that put macro-esque commands into the character sheet attack buttons, but this way is what works for me. 

I think you might have missed something as there is no reason to use selected or the character's name from the sheet.  A fun fact about Ability macros is that they do not need the name of the character to be included in the macro 99% of the time.  It automatically fills the name in if there is not one present.  Example:  When you reference the Character "George McFly"'s attribute @{dexterity_mod} in a Collection tab macro you need to write it like this: @{George McFly|dexterity_mod} or @{selected|dexterity_mod}.  But, when you write it in an Ability you only need to put @{dexterity_mod} and the system will add the name turning it into @{George McFly|dexterity_mod}. Similarly, if you use an attribute in some calculation in the character sheet itself you do not need to put a name down. So in your example above you do not need a name to call the Strength attribute. Just write @{Strength}, the sheet knows the name to put in. 

This makes the second time you've changed my life in roll20 effortlessly. You may just be the goat of all time Gauss. That's both my problems solved. Thanks.

Thanks for the suggestion! After 30 days, Suggestions and Ideas with fewer than 10 votes are closed and the votes are refunded to promote freshness. Your suggestion didn't build the right momentum this time, but feel free to submit it again! We find that the best suggestions describe the problem you are having, and the solution you want. You can learn more about the process of making suggestions on the Roll20 Wiki! More details can be found here .