Note: recursive redirection (e.g., "root,target,time") is not supported.

Enemy, Cond(NumHelper, Helper, Cond(1, ID, 0), 0) 
;returns enemy’s first available helper’s player ID

Enemy, Cond(NumHelper, Helper, Cond(1, ID = 99, 0), 0) 
;returns 1 if true.

Enemy, Cond(NumHelper, Helper, Cond(1, ID, 0), 0) = 99 
;also returns 1 if true.

Enemy, Cond(1, Var(GameTime%60) := 0, 0)
Enemy, Cond(1, FVar(GameTime%40) := 0, 0)
;sets all of enemy’s root vars and fvars to 0.

but because of priority, p1 sets player2 vars to 0, p2 sets vars to normal value in the same tick if the vars are refreshed every tick.

Enemy, Cond(NumHelper(33333333), Helper(33333333), Cond(1, Var(0) := 999, 0), 0)

Cond(NumHelper(33333333), Helper(33333333), Cond(1, Var(0) := 999, 0), 0)

Code:

[State -2, DisplayToClipboard]
Type = DisplayToClipboard ;Lag Test
Trigger1 = time = 0 && Cond(NumHelper(33333333), Helper(33333333), Cond(1, Var(0) := 999, 0), 0)
trigger2 = time > 0 && Cond(NumHelper(33333333), Helper(33333333), Cond(1, Var(0) := 444, 0), 0)
Text = "Helper(33333333),var(0) = %d"
Params = Helper(33333333),var(0)

[state time] ;Set your helper Var from root, to match root,time.
type = null
trigger1 = Cond(NumHelper(33333333), Helper(33333333), Cond(1, Var(15) := root,time, 0), 0)
ignorehitpause = 1

Trigger1 = var(15) = 0 ; acts as Root,time = 0

Root, Cond(NumTarget, Target, Cond(1, time, 0), 0) 

Late reply, but adding more to it:

Explaining a bit on how it actually works, without any of the examples Ink posted.

Cond was made with the intention to get information out of the source, check if its true/false and return a or b

Code:

Cond( Condition, a, b)
Cond( Condition = true, return a, b)
Cond( Condition = false, a, return b)

(IfElse works similarly but won't work for this kind of application).


with that in mind you can almost see how it works

If I Write

Code:

Cond(1, ID, 0)

100% of the time, that code will get me the ID value, since the info that cond is checking is ‘1’, which means ‘true’, it will return the id. if 1 would be considered ‘false’ then it would return 0 (but that won’t happen. (Unless you’re from a parallel universe lol).

But, why would you use cond that way? because all we care about its the “return a - b” scenario.

The other way around to do that would be by writing:

Code:

Cond(0, 0, ID)

this will prefetch the b-data.

and using that with other instances inside mugen, give you the same. Catch my thought yet?

What if we could get the id of a helper that’s attacking the player in just 1 line?
We need to do as it follows:
-Check if there’s a player nearby
-Check if that same player, has an active helper with attacking properties
-If everything above is true - return it’s ID.

 Coding that in game:

Cond(NumEnemy,
Cond(Enemy, NumHelper,
Cond(Helper, MoveType = A
Return ID.

I’ve separated just so you get the jist of it.

Lost?

All we are doing is redirecting data inside other objects(players/helpers) until it gets to the object you need. Its like a chain of redirects that go 1 by 1, until it reaches it's destination. That's why there's cond on top of conds.


The var setting using the := operator also works using this method:

Code:

Helper(200), Cond(1, Var(10) := 1, 0)

This will set the var 10 of that Helper(200) to 1. Remember that, mugen works like this:

Check condition > if true, apply whatever effect from whatever sctrl; While true, do not check for any more objects that this is not true.

What does that mean in practice? That’s gonna check for the first spawned helper(200), and set its var while the helper is ingame. if by any chance another helper 200 is summoned. it won’t get the same effect as long as the first helper is still there. To overcome this problem, there’s a lot of different solutions. I’ll leave that as an open topic.



This exploit was found in mid-ish 2018. Me and a couple of friends have stress tested this and we can say it's totally reliable. (As long as you know how to use it, and you're fully aware of how mugen checks conditions).

Funny enough, Electbyte coded Cond, because IfElse had problems with how it had try to check the conditions, and to fix that they created Cond, which makes it possible to cross-redirect any type of data in between all available ids. Helper from your team or not, it can be accessed and their info can be checked directly from any id without any kind of hacking code that would only work on full games. IfElse on the other hand, can't be used to do that. It wont work.

Also it’s kinda weird that i've just came across this exploit 10 years later since the first time Cond was actually introduced but oh well.

You'll have to be much more specific. Which helper's ID are you trying to get etc.

feel free to post the code you have tried and I'm sure we can help you with it. *Sorry for the late reply