[FINISHED] Spells&Systems Mini-Contest #13

[donut3.5]

Congrats to our multi-time winner DoL!

Question on leaks:
1.) By leak do you mean I forgot to set the variable to null, or I didn't remove the unit from the game?
2.) Does an exploded unit get removed from the game since it technically doesn't have to decay?
--donut3.5--

 

[PurplePoot]

1. You didn't remove or kill or explode or etc the units
2. Any method of killing them eventually does. In fact, RemoveUnit is frowned upon due to the conflicts it causes with about everything in existence.

 

[-Berz-]

No comment............................................................................................................................................................................................................................................... about 150 letters.................................................

 

[Herman]

On a sidenote, Disciple becomes the first person to have won more than once! Congrats to him!

Not gonna pretend here, but I think DiscipleOfLife's ridiculous triggering skills makes this challenge hard as hell ><

I got really good at triggering (or better at least) for JASS, but I don't like vJASS because I think I figured out how structs work, and it could be re-created in regular JASS easily, without using HandleVars (which I also hate using)

I'm probably gonna switch to vJASS when I get good at it, but for the moment, would it be bad if I used global arrays + a data system for my spells? or would that count as using unnecessary space, or is this the wrong place to ask altogether? (or perhaps that was a dumb question...)

 

[donut3.5]

Pooticus, check their HP regen. I've found setting it to a negative number is more preferable to adding in code with expiration timers.
--donut3.5--

 

[Herman]

Yeah, but what about a heros regen... like +11HP per second, would be a little conflicting if you changed it...

 

[donut3.5]

For dummy units I meant.. If you set it to -100 and they have 100 life, its the equivalent to giving them a 1 second expiration timer.
--donut3.5--

 

[Just_Spectating]

i always use 10 HP with a variable -regen, so we can have easy time checking,(BTW decimals work!)

 

[Herman]

For dummy units I meant.. If you set it to -100 and they have 100 life, its the equivalent to giving them a 1 second expiration timer.
--donut3.5--

Oh that is very good, far far better than using expire timers

I'm gonna start using that method henceforth

I'm thinking I'm gonna stop making spells for the most part, because I started to understand data, data systems, hash tables, etc. and for the kinds of upper-scale spells I wanna make, it would require me to do an extensive amount of code and data

Reveal Ramblings

like things for adding FX to attacks, I'd probably use a data system + an enters map event, then set global arrays based off some kind of data system that coordinates between the units ID [I have a fairly crappy one atm that works, but leaks strings like nuts, which I was thinking I could fix with a small VB outside program] then all kinds of code to use the data, like the Degree_Arc function I made recently, I simply do not trust vJASS and their pre-made DD + PUI systems

 

[spiwn]

Congratulations DiscipleOfLife

Not surprised at all with my poor triggering, am just new, but learning.

 

[marven15]

Congratulation DoL! XD

I am satisfied with the points that I got. ^^ XD I promise that i will follow your advices PurplePoot. ^^

 

[DiscipleOfLife]

thx thx

win came down to 1/10 in triggering points

lucky me that triggering isn't rated from 0 to 5 anymore

 

[PurplePoot]

Well donut,

At least try to make it more apparent next time then, please (Put a comment in the code or somesuch).

 

[donut3.5]

Bah, Documentation is </3 for me
--donut3.5--

 

[GhostWolf]

For dummy units I meant.. If you set it to -100 and they have 100 life, its the equivalent to giving them a 1 second expiration timer.
--donut3.5--

It is not as it kills the unit instead of removing it (ruining the coolness of the spell).
That is, unless you make a trigger that takes a unit that died of your dummy type and remove it, which destroys all the point of it.

 

[raft_pl]

Gratz Disciple (a bit late, but i just got back home...)
And yay, 26p - third place, when checked the others results too Didnt think i could get so many points, thought Eccho and Just_Spectating will push me down in the ranking...

 

[-Berz-]

Congratulations DiscipleOfLife.
You all stop using GUI and expect to make MUI abilities, FOOLS !
Now go learn Jass and vJass and make awesome spells. This is an order !

so what i'm a n00b GUI user... so this makes my spell the worse?
Some people dont just g33k in notepad++, and spend the whole day in front of PC...eeeh it doesn't matter, Dol grats from my side.

 

[Ciebron]

jass it the same as GUI really, u know GUI u know jass.

 

[GhostWolf]

so what i'm a n00b GUI user... so this makes my spell the worse?
Some people dont just g33k in notepad++, and spend the whole day in front of PC...eeeh it doesn't matter, Dol grats from my side.

This doesn't have anything to do with notepad++. About being a geek and spending the whole day on a computer, you said g33k - now lets see who spends more time -.-

Now for the matter, "learning" Jass is simply learning the basics of programming (functions, locals, blablabla), which is one of the... eh... easiest things ?
This should take you about 1 hour to master. Then for the oh-so-hard-syntax, you have function lists (or you can browse through blizzard.j and common.j).
Not to mention that the names of about 99% of the functions describe what they do (for example, I always wondered what KillUnit(unit value) does, can you tell me please?).

And no, I didn't say your spell is bad or anything about you, but it is a fact that a code in Jass and further more vJass will always be better then GUI (unless the coder is an idiot which then would have made also the GUI crappy which means that this is a useless comment).

 

[PurplePoot]

I'm always more lenient with GUI than with Jass, due to the lack of Jassers here, and thus the marking is different. A 'Jass' spell which was, in fact, converted from a GUI that would earn 10/10 would probably have trouble earning 5.

Notice how no GUIers got punished for BJs, etc, because they are unavoidable in it.

And you don't even have to have learned GUI first. They both take time to learn, and one is eminently more useful. The problem is that most haven't heard of it until long after they start, and also that programming is not for everything (But then again, neither is GUI).

 

[donut3.5]

It is not as it kills the unit instead of removing it (ruining the coolness of the spell).
That is, unless you make a trigger that takes a unit that died of your dummy type and remove it, which destroys all the point of it.

Expiration kills, doesn't remove instantly..
And Poot just said killing is better than removing
--donut3.5--

 

[PurplePoot]

Removing is deprecated due to the fact that it bypasses any form of detection and thus causes a lot of leaks and other bugs.

Apparently Hide+Explode is the new rage.

 

[DiscipleOfLife]

I just tested and found out that Kill+Remove triggers death events!

call KillUnit(whichUnit)
call RemoveUnit(whichUnit)

vs

call ShowUnit(whichUnit, false)
call SetUnitExploded(whichUnit, true)
call KillUnit(whichUnit)

If that death event thing is the only buggy thing with RemoveUnit, I'd say the first one is better.

 

[PurplePoot]

Disciple, do the death events stlll reference the unit, though, or a null unit (due to remove)?

 

[DiscipleOfLife]

The death event fires in between the kill and remove calls, so yes it still references the unit since it hasn't been removed by that time. I also tested if the unit still had its user data during the event just to make sure and it did.

 

[donut3.5]

The appeal for exploding units for me is that you can create art effects by setting their "Art - Special" field to something cool.
--donut3.5--

 

[Herman]

Wait.... the remove unit causes a leak, somehow??

Who figured that out exactly, because it doesn't seem to make sense to me

The only thing I can think of is if your using data systems that need the unit to die to clear the leaks, then, yeah the KillUnit() fires the death event, and the remove unit clears it from the game (skipping decay rate)

 

[PurplePoot]

Herman, it causes leaks if you have anything attached to the unit, seeing as it doesn't give you a chance to clean that stuff up.