Instant tags mean another action can be executed after a tagging action during an AI tick.
It also applies to tagging actions.
So you can have several tagging actions followed by a classic action during an AI tick.
Tagging actions rely on the existing tags.
During a single AI tick, you can chain instant tagging actions having the knowledge of what you just tagged or untagged.
Instant actions for a single bot are evaluated sequentially.
Team tags are shared.
The AI evaluations of two different bots are (virtually) simultaneous.
So if you give them both access to team tags modifications, they can't rely on the existing team tags to decide which tagging actions to execute.
That's why only one bot per team should be able to modify instant team tags.
So I skimmed the beginning of this message and thought it only explained how instant tags would work, which already sounded like what I already said it should be, so I stopped reading. I guess there was more to the post, particularly why there would only be the leader who could manipulate team tags.
First off, I guess I should explain why I think (as a whole) one bot class shouldn't be the only bot with team tags.
The importance of team tags mainly could be used to filling in the gap of what the refactoring update was supposed to give: shared information between bots.
I know firsthand that one bot can't figure out what any other bot can see and team tags is the easiest way to implement that without actually having the feature. However, if only one bot had team tags, it would basically remove most of the use of team tags' usability, and hurt the options any bot has (and if bot tags wasn't instant, it probably would lead to tags being worse than what they are currently). Not only that, but it also puts all of our trust for tags in one bot, which further weakens the use of team tags if it was limited to one bot class, hence my message:
mcompany wrote:Honestly I doubt that would end up happening unless there was some REALLY good reason to rely on the leader, but I doubt just team tags without any other way to gain the information is going to make that happen
As for the actual problem at hand (tags can't be relied on because how do you get it to happen simultaneously), that's been a problem since 6.1. I don't actually have a good solution to it (besides the one class limit, which like I said, has major problems of its own), and at the very least one could potentially just make thing use the same flawed system we already have: not care that later bots will overwrite earlier bots and continue playing oblivious to it