Could Mook tokens point to original character sheet for use by macros.

I love use of @{target| } in macros for my players to speed up the game very nice when targeting NPC. But when targeting Mook limited to 3 bars and token_name. I use pathfinder so HP, AC & CMD allow a lot for them hitting things. But in practice AC flat footed, AC Touch, CMB, Alignment, to name a few. So could token remember the character it used to point too, or just have a flag in token to say it's a mook but retain the link to the character information. Could bar1, bar2, bar3 be token data, but attributes be character data and still be accessible through your lovely set of macros. As a work round At present if I recreate a hord of say zombies, all are mooks without names, except one which is not a mook which has a name which still retains the link to full list of attributes, by tweaking it once deployed back to non mook, at that point the token does remember what fields bar1, bar2, bar3 were originally referencing, so I suspect the data is already retained. My players have to remember to target it, if macro errors and needs more information & I have to target it, to get token linked macros which use @{selection Thanks

I am not sure I understand your problem. Tokens can already point to a character sheet. Edit the token and set the "Represents Character" field to the appropriate character sheet. This page may help: <a href="https://wiki.roll20.net/Linking_Tokens_to_Journals" rel="nofollow">https://wiki.roll20.net/Linking_Tokens_to_Journals</a>

But after you have setup your token say with say Represents Character field pointing at say Wolf and you have setup up Bar1 to an attribute like HP ( Which I have defined as attributes for character wolf) and bar2 to AC and bar3 to CMD etc you reset Represents Character field to None/Generic Token save it and save the token as the default in the character, as nicely described in your page. This then lets you lots of copies of wolf as a mook where the HP fields are independent for each token on the screen. But I can still write macro that use the @{target|bar2) in a macro to which for me is always AC to see if play players sword stroke hit the wolf. However it would be really useful to to allow macro's to access other fields in wolf even though the token is None/Generic. If you can't do that could you allow bar4 field which I could hold the AC touch say, even if there was not room to display it. To be honest I think you should have a field that says mook, leave Represents character field pointing at say wolf, if mook set true, for Bar 1 values are local to token and don't effect fields in the Character. Please accept my apologies for not expressing myself very clearly.

You can access any character field that you control by relaxing "target" with the character's name. You can't use target on a token that isn't linked to a character because that's not how that works at all, the system needs to know exactly what you want it to do. Also, make sure you unlink the default token's HP, otherwise all 4 wolves will change their HP when you modify one of their HP bars.

Duncan S. said: you reset Represents Character field to None/Generic Token save it and save the token as the default in the character, Sam said: make sure you unlink the default token's HP, otherwise all 4 wolves will change their HP when you modify one of their HP bars. This is the mistake you're making, Duncan. Reset the individual bars to represent nothing, not the entire token... leave the represents character field so it represents the character! THEN, UN-link the HP bar etc. This way, each token is still going to have the critter's base stats from the sheet, such as ACtouch if you like. However, the un-linked HP field remains independent in each token. Hope that helps clear things up. -Phnord

Thank you Phnord Prephect & Sam I was not looking at the problem the right way. I can now have the same macros target NPC's and Mooks alike. Thank you again you are a wise ones ! I withdraw my request since it is not needed. Duncan