Tagging Question

[MGBlitz81]

Ok so there are instant tags now, I get that. But I'm having an issue that should be simple to solve and I'm not sure if I understand the new tagging system enough. Anyway, this is the scenario...

All my tags initiate before every other command including my untag commands. I am trying to tag any enemy when he is at short range. I'm using a simple two node command to do this and I'm using "add Team Tag A". Now team tag A is also used for other tagging purposes but I always use "add Team Tag A" instead of the exclusive tag. If my bots are attacking someone tagged A, they won't initiate the tag on a short range enemy. My untag conditions are not met so it isn't an instant Untag issue. They should be tagging this short range enemy and its driving me nuts!

Am I missing something here?

[sollniss]

How about you show us the nodes?

[MGBlitz81]

Ill try. I have to figure out how to do it first.

[pier4r]

to make a screenshot on android, your device should provide a manual were it is written.

In the worst case you can install AZ video recorder that does also screenshots.

Then you can upload them on imgur (assuming they are big) and link them here.

[MGBlitz81]

Hope this works...

I assure you that these are the first nodes to activate. The short range tag node is first and the Untag node is second. The only thing you are not seeing is more commands to add the "add Team Tag A" in other scenarios. I'm creating a priority based system and tag A is reserved for emergency situations.

[sollniss]

Untag furthest A will untag all bots.

First your sniper will untag the furthest, then your MG will untag the remaining furthest, etc. (I made up the order).

[MGBlitz81]

Except the enemy at short range is attacking me. The Untag reads so it ignores enemies attacking or moving to me or allies.

[MGBlitz81]

Actually I figured it out. Its the dann "or" condition, not the furthest. I need to create several nodes to cover each "or" condition separately and string them together.

[pier4r]

I reuse the thread for a follow up question.

So say I want to count with 2 tags. Bot tag 5 and bot tag 4.

I use as register the ally base tagged A (it is only one).

I set the bt 5 (1 tick)
then I remove bt 5 and I set the bt 4 (2 tick)
then I add the bt5 (3 tick)
now I want to remove them and my problem is: if I don't use an additional information, I cannot remove both tags otherwise the cycle starts again with setting tag 5.

So far to avoid this I have to use another tag on myself. If myself is not tagged 5, remove bot tags, then tag myself.

Does anyone that spent a bit more time with tags was able to do the cycle without any additional tags for counting? So using only bt 5 and bt 4 but without falling in the cycle again and again.

[B_head]

Please refer.
(Edited because it was too careless)

Examples of counting single.
Cycle stop with 31 counts. not used additional tag.

20180811202000_1.jpg (277.39 KiB) Viewed 1200 times

Example of counting multiple in parallel.
Stop the cycle for tag 3 and tag 4 with 12 counts.
Temporarily use tag 5. tag 5 can be reused as a temporary tag in elsewhere.

20180811202010_1.jpg (278.86 KiB) Viewed 1200 times

[pier4r]

Thanks bhead and welcome back!

In your examples you set incrementally the numbers but you don't go remove them. What I did is a cycle with a stop (that is, that stops the cycle). Only the stop part needed an additional tag.

Maybe is better if I post a screenshot later.

[ElvenMonk]

Examples of counting single.
Cycle stop with 31 counts. not used additional tag.

20180811202000_1.jpg

OMG thats amazing!
I mean using connection to prevent node execution from other branches.

[ElvenMonk]

@pier4r Answering your question


(Edited) I feel that you dont need cycle with 4 states, but something else instead. Why your cycle code would interfer with stopping code. Usually counter is either started or stopped depending on exclusive conditions. Can you describe your use case more precisely?

[pier4r]

Ok no screenshot but I try to expose the problem better to explain what I mean. I use an example that is similar to what I want to achieve.

Let's say I want to count only when I retreat from an enemy.

So trigger: - I am retreating from an enemy.
Clean up conditions: I am not retreating from an enemy, or more than 4 ticks are elapsed.

Ideally it would works so:
- I start to retreat from an enemy, I count 1
- still retreating, I count 2
- still retreating, I count 3
- still retreating, count 4 and clean up the count independently from the fact that I still retreat or not.

- If I am retreating and counting, and then I stop retreating, then I clean up everything.

I can achieve this, but with 3 tags not with 2. As I need 2 tags to count and one tag to decide "ok now the cycle has to stop, we counted long enough".


B_head and elvenmonky are providing beautiful ways to count up. Say to count up to 4. That is not the problem (although I appreciate your beautiful code). The problem is to clean up the count once I get more than 4 ticks without restarting it. And this using 2 tags, not 3. I don't see how can I achieve this.

[ElvenMonk]

If I get you correctly, while you are retreating for a long time, you still need to keep the fact. that you already counted somewhere.
There is no way to know if you last action was the same as before.

What you may want is to have 5 states:
- not tagged because not retreating
- not tagged because retreating 1st time
- tagged 5 because retreating 2nd time
- tagged 4 because retreating 3rd time
- tagged 4, 5 because retreating 4th time

To do that you need to keep old counter value until all conditions using it are executed and only increment counter before actual action. It is really difficult to use, I know

[pier4r]

What you may want is to have 5 states:
- not tagged because not retreating
- not tagged because retreating 1st time
- tagged 5 because retreating 2nd time
- tagged 4 because retreating 3rd time
- tagged 4, 5 because retreating 4th time

You got the states properly. You missed one though
- not tagged because retreating 5th time or more

Do you also see the need of an additional tag to keep the state?

[ElvenMonk]

There is no way to distinguish:
- not tagged because retreating 1st time
- not tagged because retreating 5th time or more

So yeah you need additional tag for that.

[pier4r]

Yes I saw the same but people sometimes have great ideas so it is always better to double check.

[Chilio]

Well, in the first tick, you don't see yourself as retreating, while in the fifth tick you do.

[ElvenMonk]

In my example, it was "first tick already retreating"