"Else" line in condition nodes

[DjSapsan]

Request: add "Else" line in condition nodes. When condition is true - regular output will executing. When condition is false and node has a line from "Else" output - regular output will be skipped and "Else" output will executing.
You should say that you can put nodes after this condition or create copy of first node with inverse. But in some cases its not working. Lets look.
I have setup. One bot trying to set tags on other bot. Before this case targeted bot has tags 1 and 5.
In next step i have insulting situation - bot got wrong tags. In screenshot i catch this moment. First condition was true and targeted bot is tagged 3 now. Its intended behavior. But then next condition is true now! Its instantly remove tag 3 and put tag 2 for bot C. In battle i even cant see that targeted bot has tag 3. Bot instantly has tags 1 2 5.

123.jpg (83.62 KiB) Viewed 1678 times

"Else" line can solve this issue (and other problems too). With current logic its impossible to have correct order in one tick... instead i should use twice harder logic for split operations in several ticks + waste tags.

234.jpg (138.72 KiB) Viewed 1678 times

[Norljus]

+1

[GFX47]

Your bug exists because tag actions don't stop AI check.

[Norljus]

Your bug exists because tag actions don't stop AI check.

But an else path might still be usefull, isn't it.

[GFX47]

Yes but it would be confusing to mix the existing "counterclockwise check" principle with it.

[Norljus]

Yes but it would be confusing to mix the existing "counterclockwise check" principle with it.

Not when the else exit of a condition is to the right of the normal exit. Or what do you mean ?

[DjSapsan]

Yea I dont mind about bug. Its just request. Clockwise and counterclockwise principle doesnt matter indeed. I can put output in any side any direction. Guess will look better with "else" ouptut in right side.

[GFX47]

Yes it matters! The whole system is based on it.

[DjSapsan]

i mean its for me doesnt matter. You will decide what there will be in which order. We just asking for "else" output without additional requests. Some way to ignore next nodes if first condition is true.

[masterplayer]

GFX47 +1
else -1

[DjSapsan]

will this request put to the roadmap?

[GFX47]

I don't recommend this feature so, sorry but no.

[DjSapsan]

how to stop execution then?

[GFX47]

Stop execution?

[Monger81]

Isn't the counter-clockwise evaluation already an "else"?
Actually an elseif, I guess.

[ElvenMonk]

Isn't the counter-clockwise evaluation already an "else"?
Actually an elseif, I guess.

Well, not for intantly executed actions (like tagging). And tagging actions simply don't deserve such an exception from common AI evaluation logic.

[Monger81]

Well, not for intantly executed actions (like tagging). And tagging actions simply don't deserve such an exception from common AI evaluation logic.

Well, this bears the question why tagging behaves differently, at all. Tagging could require aiming, or could wear off, or could have a cooldown effect, or...it feels kind of cheap that it doesnt require time.

[masterplayer]

Well, this bears the question why tagging behaves differently, at all. Tagging could require aiming, or could wear off, or could have a cooldown effect, or...it feels kind of cheap that it doesnt require time.

We had this. Tagging was kind of useless back then.

[DjSapsan]

I guess that everyone misunderstand me. "Else" line not related to order of execution. Im not talking about "Else" node. Im asking about line. Order of execution will remain the same - from left to right. Conditional node will have two outputs for true and false:

else.jpg (111.87 KiB) Viewed 1328 times

Its similar to two independent nodes and have regular execution order:

unknown.png (57.3 KiB) Viewed 1328 times

But "Else" output will solve some impossible cases that described above. I repeat, execution order will remain the same.

[pier4r]

Yes doing an else with separated nodes is not always that easy.