Anything can be done. The more complex (or large... however the spell has been built), the more integers you will need. Of course, if you are able (this takes thought, so a lot of people can't do this), then you can make anything multi-castable (even the more complex spells).
Comments
19
Allright, what i meant was, that when you get into doing more complex things ( lets say making a unit jump to a point ) is that Arrays will not work, as in GUI you will need multiple triggers so it will not look horrible. There is no way to tell which array to use at what time between triggers. With locals, there is.
Ok, after viewing all of them... the tornado is already multicastable. Most of the others are just simple conversions of my multi-cast system (not really mine, but the one that is posted here). What is the point of challenging me to make them multi-castable? It's not about being able to do it, it's about whether the method which I have provided works or not (thus proving my point that Jass isn't required).
the Arcane Competition Spellpack that won DC and had time stop, hows that for starters?
---btw that ones fairly easy, if you get it right ill make a harder challenge---
I'm not interested in playing games with you and wasting time on challenges. For the sake of not looking like an idiot, I will make the arcane spell pack multicastable (I gotta find it and check out what it is).
What I am interested in is proving my point... that is, if you still disagree with me. If you can't remember my MAIN point, then read back... (what seems like way back...)
[EDIT]: Do you want me to do all of the spells? It's a little repeditive. I'd rather you pick one spell... I'll do what I can in the time I have, anyways.
... Lol... I started on the wrong Arcane spellpack.
the Arcane Competition Spellpack that won DC and had time stop, hows that for starters?
---btw that ones fairly easy, if you get it right ill make a harder challenge---
---btw that ones fairly easy, if you get it right ill make a harder challenge---
I MEAN... any kind of spell using more than one trigger.
Well... yes, I can convert it to work with spells using more than one trigger.
Maybe you can refer to a spell that is easily to line-read in the wc3sear database that I could look at, and make multicastable (any example you like, as long as it is easy to line read).
I MEAN... any kind of spell using more than one trigger.
What you mean by some kind of jump? Example?
i meant a multitrigger spell, like some kind of jump.
@PurplePoot:
The trigger I put in makes the archmages blizzard at the exact same time. This map proves that it works simultaniously. It can handle functions taken in at the exact same time (if you want, I can repost this map so it will display each archmage's number in the array).
The trigger I put in makes the archmages blizzard at the exact same time. This map proves that it works simultaniously. It can handle functions taken in at the exact same time (if you want, I can repost this map so it will display each archmage's number in the array).
Allright, heres a scenario My spell uses two triggers. how does the second trigger know which array number to use? BAM! shot down!
Allright, heres a scenario
My spell uses two triggers. how does the second trigger know which array number to use?
BAM! shot down!
There, i said that, but MobKing is getting pissed that i am using the Entangling Inferno thing to do it, so ill post it here
lol, you still arent avoiding it completely. What if 100 units use the same thing at once? BAM!
you are stubborn, arent u?
@PurplePoot: All you have to do is increase your limitations from 50, to whatever number you wish. The arrays will resize themselves, so there is no worry there. If you really expect this will reach such a high number, try setting your array high, and setting the reset at 1000, or 2000, or whatever you wish.
Do you really expect more than 1000 units will be casting a spell at any one given time? lol. And if they do, do you expect the game won't lag no matter what's going on? Lol... Just 1000 units actively being in the game can cause lag.
It is unrealistic to expect more than 200 units to be casting the same spell at the same time, anyways. If you do, you have a VERY special case...
lol, you still arent avoiding it completely. What if 100 units use the same thing at once? BAM!
you are stubborn, arent u?
you are stubborn, arent u?
Ok i understand
For some who dont know how to do it its good....
For some who dont know how to do it its good....To the person who said "wtf", as well as anyone else who doesn't quite understand:
Try creating a trigger enhanced (not using Jass) skill that does this: On casting, the unit is paused. There is a wait of 5 seconds game-time. The unit is then unpaused.
Now, try having multiple units do this. It will not work (it will leak).
This "system", or whatever you would like to call it, is a way to work around this problem. Normally people would use Jass. This is just a simple fix, without having to use Jass. What this does is it allows multiple heroes to cast the same skill, without any leaks (it will all work out well).
NOTE: This system can only be understood by someone who can trigger edit. Otherwise, it is just something that makes a bunch of archmages cast blizzard in the middle of the map.
Try creating a trigger enhanced (not using Jass) skill that does this: On casting, the unit is paused. There is a wait of 5 seconds game-time. The unit is then unpaused.
Now, try having multiple units do this. It will not work (it will leak).
This "system", or whatever you would like to call it, is a way to work around this problem. Normally people would use Jass. This is just a simple fix, without having to use Jass. What this does is it allows multiple heroes to cast the same skill, without any leaks (it will all work out well).
NOTE: This system can only be understood by someone who can trigger edit. Otherwise, it is just something that makes a bunch of archmages cast blizzard in the middle of the map.
@Empiredeath & anyone else confused about what this is:
What is special here is what I did in the triggering. If you were try to create a trigger that pauses a unit when it casts an ability, then waits 5 seconds, then unpauses that unit, it wouldn't work if multiple units cast that ability. This is a system that allows you to have any number of units cast the same spell, be paused, wait 5 seconds, and unpause them, without having to use locals or otherwise.
Anyways, just look at the triggering if you want to see what is so special. (It's fairly simple, too)
What is special here is what I did in the triggering. If you were try to create a trigger that pauses a unit when it casts an ability, then waits 5 seconds, then unpauses that unit, it wouldn't work if multiple units cast that ability. This is a system that allows you to have any number of units cast the same spell, be paused, wait 5 seconds, and unpause them, without having to use locals or otherwise.
Anyways, just look at the triggering if you want to see what is so special. (It's fairly simple, too)
i only think its useless ?if i type test all cast on a point ? nothing more happenslol
I made this to attempt to prove a point... Ummm... I hope I did. Anyways, I had troubles with adding descript and screenshot. Like I said, this is a system that allows you to cast spells multiple times (as many as you like) without having problems with leaking and such.
Hopefully this helps someone...
BTW: There is no real need for a screenshot anyways... no actually skill to show (unless if you want to see an archmage blizzarding, for no reason).
Hopefully this helps someone...
BTW: There is no real need for a screenshot anyways... no actually skill to show (unless if you want to see an archmage blizzarding, for no reason).
Sry, the screenshot I gave didn't work (I tried converting to an acceptable file-type).
Anyways, this is a multi-cast system/trigger that allows you to cast multiple times without any problems. This is to avoid using locals (in this given situation).
Anyways, this is a multi-cast system/trigger that allows you to cast multiple times without any problems. This is to avoid using locals (in this given situation).