state controller: NULL right usage?

Started by Jessy, September 18, 2011, 09:43:49 PM

Previous topic - Next topic

Jessy

I ask what if the right usage of that NULL used sometimes instead Changestate, I think worked in similar way...then I ask...when can be used too...
-I hate haters and S.o.S chars.....
-time to migrate from winmugen...

Cobra Caddie

People use null when they temporarily wanna disable a state controller. So the purpose of it is, for example, if you wanna disable a changestate to test something in the state. It works for replacing all state controllers, and is easier than putting a ; in front of all the lines, and is better than deleting everything and then having to retype it all to put it back.

GT

Some ppl use null in order to assign variables with the ":=" operator.

Cyanide

Null is still evaluated. It just doesn't do anything. So if you have a bad trigger in a null sctrl. It'll still crash. Or cause debug. The most common use is instead of varsets

type = null
trigger1 = time = 0 && var(0) := 3
trigger2 = time = 0 && var(5) := 1
trigger3 = time = 0 && var(2) := 2
trigger4 = time = 0 && var(8) := 9


In M.U.G.E.N there is no magic button

They say a little knowledge is a dangerous thing, but it's not one half so bad as a lot of ignorance.