Pak said: Thanks Keith and GiGs. I started out using resources at first. But each player wanted things shown differently on their respective sheet. One player didn't want to see rations and such in the resources and others didn't mind resource tracking but wanted to see it in a specific location. I didn't want to enforce a specific format on them so I figured I'd choose the more complex way of tracking the item in question while at the same time not taking away their sheet layout "flexibility". I spoke to soon on the last code I shared. I was able to get the API to only increment a portion of the characters listed on the list. But it took 4 or 5 tries to get it happen vs. my original shared code that bugged out 90% of the time. It's almost like the API isn't responding as fast as each command I run. Player 1 will increment and the last player (#5) will increment. But the players in between get skipped. Or the next time I try, only the last player increments and all the rest are skipped. I don't recall a situation where any of the players in the middle of the list are randomly incremented. Not sure if that's just coincidence or not... I did try the --sel operator out of sheer desperation, which worked, but spit out other errors. It cross referenced every repeating item I listed against each player I selected. When it couldn't find a matching unique row ID for the character, it just spit out a could not match error. So if I selected 5 players and had 5 unique ID's to increment, it resulted in 20 "no match found" errors, but 5 successful increment messages. So it's another way to circumvent the problem but isn't the most efficient nor elegant. Worst case I'll just revert back to reminding the players to "manually" track their items. Thanks again for the inputs! Not only is there a long standing bug they have never fixed where api commands only fire once out of a macro and it ignores most of the others, but now in the chat input box for pasting a live set of commands roll20 now ignores the majority of the paste if its using api calls, attributes, /fx, /emote, and other non normal chat line breaks.