MUI and MPI

[lh2705]

I know what they stand for but which is more efficient?
Pros and Cons?

 

[SFilip]

Well MUI means that one spell can be casted by any unit at any time.
MPI means that it can only be casted by one unit per player at time...obviously MUI is better (yet harder to achieve) but it all depends on the map itself...it doesn't have to be MUI for a rpg map in which one player has one hero.

 

[lh2705]

But I know MPI is very troublesome to do..Arrays instead of variables with the index of Player number of Owner of Triggering unit/Triggering Player. Ok, Thanks.

P.S. You haven't approved my latest batch of spells

 

[Chocobo]

MUI is simply more extensible than MPI (and also more dynamic), but more harder to be done.

 

[TheDamien]

Always aim for MUI unless you have a good reason not to. MPI is usually very ugly and will probably leave you feeling unsatisfied with your work.

 

[lh2705]

Always aim for MUI unless you have a good reason not to. MPI is usually very ugly and will probably leave you feeling unsatisfied with your work.

Yeah, I agree. MPI triggers are so messy and troublesome to do...

 

[Rinpun]

Not really, if you know what you're doing anyway. For my Carrier hero in WotU (all players start with a flagship, which is initially the Carrier type; you can switch it at a special building), MPI was the most efficient way. There's a Carrier Full unit that is required to exist for the player in order to use the Carrier's abilities, and using one of them kills the unit, because the Carrier uses all of its ships inside. The ships eventually replace, and so does the Carrier Full unit, but why should I allow players to spam the Carrier's super powerful moves with magically restored units? Basically, casting an ability sends the ships to go out and do something, and you shouldn't be able to use them for something else without canceling the other abilities out there. Because a lot of the abilities work off of timers and such, it's rather hard to do so. So, the simplest solution is to go MPI to check for the Carrier Full unit.

But yes, most of the time MUI is better & easier to do than MPI.

 

[martix]

NoI means one variable
MPI means an array variable
MUI means local variable
So yea, most of the time MUI is easier to do.

 

[Chocobo]

NoI means one variable
MPI means an array variable
MUI means local variable
So yea, most of the time MUI is easier to do.

MUI is sometimes harder to do than MPI. "sometimes" only.


Single-Unit Instanceable can use simply a return to work (Triggering unit.. variable storage).

Multi-Player Instanceable uses almost all the time an array variable (2d or sometimes 3d matrices).

And Multi-Unit Instanceable is 99% of the times local variables or permanent returns (such as Triggering unit, ..)