Dummy Caster v1.4

[Moderator]

16:00, 25th Oct 2012
Magtheridon96: Approved.

 

[Almia]

~Reserved
The line the creates the game text is just experimental.

 

[doomhammer99]

4/5 - Spell Idea
5/5 - Trigger-Less
3/5 - Description

Carrion Swarm - Sucks, always casted on the right

 

[Almia]

Of course,im just using position of caster,just use offset and your problem is done

 

[Magtheridon96]

You can call ApplyDummyCaster directly inside your Order functions.
It would make things easier for the user.

Also, the user should be able to set the level as he pleases.
It shouldn't be set to the level of the caster.
What if the dummy abilities are not made to have a linear relationship with the caster's level?

 

[Almia]

Done.

 

[doomhammer99]

You're getting good, I think you're the next spell moderator.
(I think)

 

[Almia]

LoL,i have been here for almost 8 months and i have only 11 months of experience in triggering and coding

 

[mckill2009]

Doesnt support summonings and channeling.

- You should coz not all abilities are instant cast like flamestrike, it has a delay...
- Since you are using custom script, it is better to use coordinates to reset and create the dummy...

 

[Marsal]

/off how the hell did you do that multi page description?

 

[sonofjay]

he use the new tab codes.

 

[Marsal]

Ohh I found it Thanks for the info.

 

[Almia]

Mckill2009,flame strike is a channeling ability
im using location instead of coordinates because it might cause bugs.
ex.when i used coordinates,the units selection circle is moved,but not the model

 

[mckill2009]

Mckill2009,flame strike is a channeling ability

that's what I said >>> coz not all abilities are instant cast like flamestrike, it has a delay

im using location instead of coordinates because it might cause bugs.
ex.when i used coordinates,the units selection circle is moved,but not the model

use SetUnitPosition instead os SetUnitX/Y

 

[Almia]

Its okay.
Also,i mentioned it before im not supporting these kind of abilities because im only using 1 Dummy

 

[Kingz]

Well i guess this might be useful, even tho it exists already in vjass.

 

[Almia]

Yeah right,but i feel sad because GUI users dont have it :/
Thats why i created it.

 

[defskull]

How can you approve this bugged system ?
Try let the Dummy casts Slow (Sorceress) to multiple picked units (or even single unit).

You'll notice, it can't.

Why ?
Because it only corresponds to only (Triggering player)'s unit which in this case, it will only cast the spell if the dummy's owning player is the player casting the spell.

Solution:
Create each player their own dummy unit and make it array for each instance.
Dummy[1] for Player 1
-----
Dummy[12] for Player 12

Just noticed this just now while I was experimenting some things.
And please, before you start any argument, I think you should try it first (I was weird too).

Also, it is better this way, create each player their own dummy unit, why ?
Because certain game (such as DotA) will count as Player Kill like dummy casting Storm Bolt that deals damage. So, what if the dummy kills the unit ?
The trigger interprets as Neutral Passive kills the unit, does that mean NP will get the gold ? No.
This is why it is nice to have each dummy for each player.

 

[Almia]

Ok ok

 

[pred1980]

use XE.09 !

 

[BPower]

Your thunderclap example does not work unless you use stormbolt Ex first

 

[Almia]

really? How come? That works fine to me

@pred

xe is a dump.(yes i said it,no offense)

 

[KILLCIDE]

Sorry for the update. Just updating the tags.

 

[Neet]

hey what does set udg_DC_AddedAbil = 'AUcs' mean? I tried copying it and I got errors

 

[Pyrogasm]

hey what does set udg_DC_AddedAbil = 'AUcs' mean? I tried copying it and I got errors

It sets the integer variable DC_AddedAbil equal to some ability ID, in this case that of default Carrion Swarm. Internally an "ability code" variable (different from an ability variable) is really just an integer variable because a rawcode like like 'AUcs' is actually a base-62 number (A-Z, a-z, 0-9); specifically 'AUcs' is 2501010 in decimal (base-10) notation. You can see every ability's rawcode in the editor by pressing ctrl+D to toggle between 'raw data' view mode. So while you can know an integer and ability code variable are the same type, GUI really limits you and will not let you treat an integer like an ability code, and vice-versa as well. GUI will literally not let you assign the integer that corresponds to Holy Light to an integer variable because GUI 'thinks' that abilities and integers are not interchangeable like they are.

Even though you can't set it with GUI, you can set it with a custom script line, which is what you see. The rawcode must be within two apostrophes like 'xxxx' so the computer knows it's base-62. The udg_ prefix in the variable name is there because that gets added to every single variable made with the variable editor, to avoid any possible naming conflicts (udg = user defined global). You must include this prefix before every variable when referencing them with custom script lines.

What is the purpose of the variable DC_AddedAbil? It's the ability that will be added to the dummy unit before it is ordered to cast it. This is something you should be setting with a trigger as part of your usage of the system. Why are you getting an error? Probably because the variable literally doesn't exist in your map (yet). There is a WE setting called "create unknown variables when pasting trigger data" which does exactly what it sounds like it does. However, it can't look for variables in use in Custom Script lines, and as far as I can tell that variable is only ever referenced in custom script lines. Therefore it was not automatically created when you pasted this system's triggers into your map.

So the line is referencing a variable that doesn't exist so the compiler can't proceed and throws an error. How do you fix it? Well, create the variable. Make an integer variable named DC_AddedAbil and you should be able to save. But IMO that's not the best solution. Instead you should simply change it to be an ability code variable rather than an integer. This won't change how anything interacts with the variable in the custom script lines, but it will allow you to set the variable normally as a GUI Set Variable... action rather than having to use the custom script line and type in the rawcode manually.

---

All of that being said, I really would recommend that you not use this resource at all, and instead learn how to use and manipulate dummy units for casting yourself. It's very easy. This system was fine in 2012 and it was probably fine up through its last update in 2016, but it's really not up to modern standards. It's a little annoying to work with, has little flexibility, and requires you to manually interact with in a bunch of ways that basically mean you do as much setup as managing the dummies manually would be! IMO a much better use of your time is understanding how to use dummy units simply and properly without a system like this to do the (small) steps for you.

 

[Almia]

All of that being said, I really would recommend that you not use this resource at all, and instead learn how to use and manipulate dummy units for casting yourself.

That pretty much summarizes my feeling about this. Time for my resources to have a rest

 

[Bribe]

That pretty much summarizes my feeling about this. Time for my resources to have a rest

Your resources are awesome though!