[Trigger] Making a spell MPI

[Tiche3]

Hello guys, thanks for reading this post, i wanted to ask you how to make a spell MPI (multi player instansable) without any hashtables.

It is probably indexing, so can you teach me how to index not to make a spell MUI, but at least MPI.

And yes, i have searched The Hive for tutorials and i only found hashtables <.<

Any help is required, i would like you to give me a testmap on how to make a spell MPI, because theory doesn't really affect me.

Tiche3

 

[Raven0]

Easy, just put any variables you use into a size 12 array and then use player numbers to refer to whichever one you want.

 

[Noobsmoke]

there are a lots of exemples

 

[Tiche3]

there are a lots of exemples

"Any help is required, i would like you to give me a testmap on how to make a spell MPI, because theory doesn't really affect me."


Actually i've seen only very complicated MUI spells and i need only MPI and there is a difference between them. For me it is nessecary to get an example

 

[GhostThruster]

Just remove all the 'Index' indeces (eg. Unit[SpellIndex]), and replace with 'Player number of Owner of Triggering Unit'. If you want a sample, find me a spell to edit.

 

[Noobsmoke]

MPI means one trigger for every player or using 'Player number of Owner of Triggering Unit' as GhostThruster said ... btw you know indexing ?

 

[defskull]

MPI and MUI
What's the difference ?
I mean, if the spell is already MUI, other unit/player can cast it at the same time as well, right ?
I mean, 2 units at the same time casting a spell of the same type, but 2 different Player Group
That is already considered as MUI/MPI, am I right ?
As far as I know, SYSTEM trigger uses MPI-type trigger, spell system doesn't use it, right ?

 

[Bribe]

MUI -> Multi-unit-instancing -> can be done many times at once.

MPI -> Multi-player-instancing -> used by people who don't know how to do something MUI or anyone who simply doesn't need more than one instance per player.

 

[defskull]

Which owns ?
MUI > MPI ?
But I still think each has its own advantage

MUI
For spells

MPI
For System Trigger like Respawning/Waves/Multiboards

 

[Garfield1337]

MUI is always better,a spell/system that is MUI cannot be non-MPI (it can,actually,if you do it intentionally). Also it's obviously better to have something working for each unit rather than to work only for 1 unit for each player or only for a player.
For spells,there should be a term like SUMI (Same-unit-multi-instancing) - meaning single unit can cast a spell multiple times before the previous effect finishes (In case spell effect isn't instant).

 

[defskull]

Animation Cancelling ?

 

[Bribe]

SUMI is nice, looks similar to the word "struct" which tends to be the popular choice to achieve it.

 

[Tiche3]

Just remove all the 'Index' indeces (eg. Unit[SpellIndex]), and replace with 'Player number of Owner of Triggering Unit'. If you want a sample, find me a spell to edit.

Mhm mhm, but what about time - every 0.04 seconds

how would you use 'player number of owner of triggering unit' ?

YAY, 400 posts >

 

[GhostThruster]

When using loops, don't change the index, leave it as 'Integer A' or whatever. Only the 'setup' trigger (usually the one with 'A unit starts the effect of an ability) needs the indeces changed.