Meteor Strike v2.01

[Moderator]

16:48, 18th Dec 2015
http://www.hiveworkshop.com/forums/spells-569/meteor-strike-v1-03-a-273139/index2.html#post2764648 http://www.hiveworkshop.com/forums/spells-569/meteor-strike-v1-03-a-273139/index2.html#post2767868

Rating: 3.5 -> 4

 

[KILLCIDE]

Was in an extreme rush to get this uploaded ;_; I aplogize for any small mistakes you see. The spell, however, is fully functional!

 

[IcemanBo]

I can see a slope .

 

[Deleted member 238226]

oh, invoker inspired? very nice

 

[Regent_Artiman]

Wow.

I love DotA Spells man. Good 5/5

 

[KILLCIDE]

I can see a slope .

I told you I wasn't trolling! ;D

oh, invoker inspired? very nice

I love DotA Spells man. Good 5/5

Thank's guys, but I tried my best to not make it similar to Chaos Meteor xD my effects are better!

 

[ssbbssc2]

nice looking spell. but sometimes units got knock-backed but didnt take any damage (or if u aim above units head)
there isnt any initial damage from falling also, and i was thinking about some periodic fire damage

 

[KILLCIDE]

nice looking spell. but sometimes units got knock-backed but didnt take any damage (or if u aim above units head)
there isnt any initial damage from falling also, and i was thinking about some periodic fire damage

That's because the knockback AoE is different from the damage AoE xP you can play around with the config variables. I can add initial fall damage later on maybe. You might want to make the Damage AoE slightly bigger than the knockback since the knockback will likely push them away from the damage AoE

EDIT: I also forgot to mention that the damage is dealt EVERY 1 second, it doesn't deal damage with the periodic loop.

 

[San]

This is awesome!

 

[ILH]

This ain't original, but still nice and well triggered <3

 

[KILLCIDE]

This is awesome!

Thank you!

This ain't original, but still nice and well triggered <3

What do you mean D: this is the only spell of its kind on the Hive! Unless you're referring to the "Chaos Meteor" from DotA? That spell doesn't have a knockback nor does it have an "explode" feature my effects are also 500x cooler. Look at that smoke!

 

[Legal_Ease]

This is the best rolling boulder spell short of the commercial version in DotA2. Definitely the best on the Hive! 5/5 +rep

EDIT:

2. Copy and paste the dummy unit and two custom abilities, and import the dummy model into your map

This should really read, "Import dummy model, then copy and paste Custom Abilities into your map, and then copy and paste dummy units."

That way the dummy unit will have a model and abilities, before you import it. Otherwise, it will have an ability "Unknown," and you will have to reset those too. However, I do like your import instructions they are easier to read than some, and the spell itself is easy to import which is really great.

 

[Eagle XI]

Expected to see it finally explode and split into multiple shrapnels upon reaching the end whilst watching the .gif

However that isnt really necessary, probably more balanced as it is and cool enough.

 

[KILLCIDE]

nice looking spell. but sometimes units got knock-backed but didnt take any damage (or if u aim above units head)
there isnt any initial damage from falling also, and i was thinking about some periodic fire damage

Check out the new update! I added the initial fall damage and also made the damage flow smoother with the knockback.

This is the best rolling boulder spell short of the commercial version in DotA2. Definitely the best on the Hive! 5/5 +rep

Thank you for the SFX suggestions! It definitely made this spell look way better.

Expected to see it finally explode and split into multiple shrapnels upon reaching the end whilst watching the .gif

However that isnt really necessary, probably more balanced as it is and cool enough.

Ohh trust me, I had soo many ideas for this spell. However, to keep it from being complicated and OP like you said, I had to hold back ;_;

 

[Legal_Ease]

You use this line in MS_Init

• Unit - Create 1 Dummy for MS_player[MS_indexMax] at MS_dummyLoc facing MS_tempAngle degrees

Which is fine, but you have a variable (udg_MS_Dummy) set in MS_config. Why not use it? When I imported it changed it on me. Now, normally this would be fine, but you are so good at setting everything in variables usually your spells don't do this to me and import perfectly.

If you changed it already, just disregard this message.

 

[KILLCIDE]

You use this line in MS_Init

• Unit - Create 1 Dummy for MS_player[MS_indexMax] at MS_dummyLoc facing MS_tempAngle degrees

Which is fine, but you have a variable (udg_MS_Dummy) set in MS_config. Why not use it? When I imported it changed it on me. Now, normally this would be fine, but you are so good at setting everything in variables usually your spells don't do this to me and import perfectly.

If you changed it already, just disregard this message.

I pseudo-coded the spell before making all the configurables I must have forgotten to change it when I made the variable for the dummy. Thank you for the find!

There were 3 Unit - Create 1 Dummy errors in the triggers o: one when when I preload the dummy, 1 for the meteorSFX, and 1 for SFXFall. Make sure you fixed all 3 if you don't feel like downloading the new one.

 

[IcemanBo]

• The structure of the loop should look like this:
  Pseude code:
  

  If (DeIndexCondtion == False) then
  ----
  ---- Then
  ----
  ---- ---- Do Actions 1
  ---- ---- Do Actions 2
  ----
  ---- Else
  ----
  ---- ---- Deindex
  Endif

  The condition for deindexing is the first check that has to be done.
  If it's time to deindex, then it has to be done immediatly,
  and no further instance operations should be done or checked.
  Use a KillTree system or adjust it correctly.
  Trusting on default unit only is not best method.
  Or look at what they do with harvester and do the same.
• A reminder for you.
  GUI variables should be written "LikeThis", not "likeThis".
• The per second calculations can be done once onInit after the config.
  Then there is no need to re-calculate it each time onCast.
  Btw, something like "MS Cast" trigger would fit more instead of "MS Init".^^
• In cast trigger, "Set Player[index] = TriggeringPlayer" , instead of "OwnerOfUnit(Unit)". Slightly faster.

• Trigger - Turn off (This trigger)

  ->
  

  Trigger - Turn off MS Loop <gen>

  (This Trigger) is a function call. Always these brackets (), does mean a function is called.
• Is there a reason why you make instances for duration but not for time? (on init)
  Just curious.

The spell looks good.

 

[KILLCIDE]

The structure of the loop should look like this:
Pseude code:

If (DeIndexCondtion == False) then
----
---- Then
----
---- ---- Do Actions 1
---- ---- Do Actions 2
----
---- Else
----
---- ---- Deindex
Endif

The condition for deindexing is the first check that has to be done.
If it's time to deindex, then it has to be done immediatly,
and no further instance operations should be done or checked.

Thank you. I will work on adjusting it to this structure.

Use a KillTree system or adjust it correctly.
Trusting on default unit only is not best method.
Or look at what they do with harvester and do the same.

Working on it

A reminder for you.
GUI variables should be written "LikeThis", not "likeThis".

Already talked to you about it in chat however, I just wanted to clarify that the reason I write my variables like so is because I want to seperate my config variables from the variables used in the Init and Loop.

The per second calculations can be done once onInit after the config.
Then there is no need to re-calculate it each time onCast.
Btw, something like "MS Cast" trigger would fit more instead of "MS Init".^^

Will work on this! Thank you. Will changing it to MS Cast help me get a 5/5 rating? (;

In cast trigger, "Set Player[index] = TriggeringPlayer" , instead of "OwnerOfUnit(Unit)". Slightly faster.

Got it! I will have to do this for all my spells as well.

[*]

Trigger - Turn off (This trigger)

->

• Trigger - Turn off MS Loop <gen>

[/stable]
(This Trigger) is a function call. Always these brackets (), does mean a function is called.

I guess I can make this small change xD faster is better!

Is there a reason why you make instances for duration but not for time? (on init)
Just curious.

Im sorry I am a little confused with this question D: do you mind elaborating?

EDIT: Thank you for clarifying. Will add multi-level support.

The spell looks good.

Thanks I also thank you for taking the time to teach me about the slopes.


EDIT: Changes have been made.

 

[Kazeon]

- Only use 1 stunner dummy unit for the whole game. And I think it's better to stun when the meteor hits the ground instead of when it's destroyed, it just makes more sense.
- The angle is static, so store it in a real array variable for every instance. And eventually MS_moveRate is also static I think.
- Then to determine traveled distance, use distance=distance+movespeed on every tick, instead of getting the distance from loc a to b all the time. If distance>targetdistance then destroy (spell ends).
- Commonly 2 location variables are enough for a spell. To achieve this you need to use a location array variable for every instance which stores location where the spell is casted, let's name it CastPoint. Then the second one is a temporary location variable (current position of meteor): CastPoint[index] offset by CurrentDistance[index] towards Angle[index].

 

[KILLCIDE]

- Only use 1 stunner dummy unit for the whole game.

I like the idea of just making 1 stun dummy for an entire spell that would mean I only have to set the level right before the Unit Group function, correct?

I think it's better to stun when the meteor hits the ground instead of when it's destroyed, it just makes more sense.

I thought about this, but it seemed a bit too OP. That would basically give a guarantee for the damage and knockback. I considered giving the landing mechanic a huuge knockback, but that would benefit the enemy more than the player xD i like the idea of the meteor exploding at the end and stunning them more.

The angle is static, so store it in a real array variable for every instance. And eventually MS_moveRate is also static I think.

I actually attempted this, but the spell became super buggy after. fallRate would ALWAYS be the same, so i just determined its velocity on init. I indexed moveRate and angle on cast, however the spell did not work properly after one instance. I will attempt it again and maybe catch the error I had.

Then to determine traveled distance, use distance=distance+movespeed on every tick, instead of getting the distance from loc a to b all the time. If distance>targetdistance then destroy (spell ends)

Ahh that makes sense real comparisons are always faster. I will work on this, thank you.

Commonly 2 location variables are enough for a spell. To achieve this you need to use a location array variable for every instance which stores location where the spell is casted, let's name it CastPoint. Then the second one is a temporary location variable (current position of meteor): CastPoint[index] offset by CurrentDistance[index] towards Angle[index].

Hmm sorry Im a bit confused with this. I do index targetLoc and offset the distance with aimLoc. I use tempLoc and dummyLoc to move the meteor and just use the other two for an "aim." Do you mind elaborating a bit more?

 

[Bribe]

KILLCIDE, I made some changes to KB2D specifically for this spell. You can do all the movement of this system using it and avoid having to use PurgeAndFire's walkability resource as well.

 

[Kazeon]

Hmm sorry Im a bit confused with this. I do index targetLoc and offset the distance with aimLoc. I use tempLoc and dummyLoc to move the meteor and just use the other two for an "aim." Do you mind elaborating a bit more?

You only need to index cast point or start point: where the meteor is created initially. And you also have CurrentDistance and Angle variables. So to determine meteor's position on every tick you can use this for the temporary location variable:

set TempLoc = CastPoint[index] offset by CurrentDistance[index] towards Angle[index].

Note: variable "Angle" is angle from start point to target point.

 

[KILLCIDE]

KILLCIDE, I made some changes to KB2D specifically for this spell. You can do all the movement of this system using it and avoid having to use PurgeAndFire's walkability resource as well.

I saw it will be useful. However, I didn't want to heavily rely on systems to make my spells. I made this spell to practice on making an effect fall in a slope-like manner.

You only need to index cast point or start point: where the meteor is created initially. And you also have CurrentDistance and Angle variables. So to determine meteor's position on every tick you can use this for the temporary location variable:

Well I have "2 target" positions. The landing point & the explosion point.

Note: variable "Angle" is angle from start point to target point.

Will work on making angle an index. moveRate & fallRate can be calculated on init instead of on cast, so I will work on that as well. Thank you.

 

[Kazeon]

Well I have "2 target" positions. The landing point & the explosion point.

You only need one of them. Unless the meteor is able to turn. You only need the cast target point to determine the "Angle" and "Target Distance".

 

[KILLCIDE]

You only need one of them. Unless the meteor is able to turn. You only need the cast target point to determine the "Angle" and "Target Distance".

Ahh I understand now. Thank you! I have a lot of work to do xD


EDIT: Changes have been made.

 

[IcemanBo]

Same thing with deindex as it was before with your other spells.
Seems an update is missing, so I will have a more detailed look
after the next update.

I didn't want to heavily rely on systems to make my spells.

But systems are there to take usage of them
Outsourcing is something positive for spells, so you don't have to bother about any algorithms you need.

 

[KILLCIDE]

Same thing with deindex as it was before with your other spells.
Seems an update is missing, so I will have a more detailed look
after the next update.

Yah I figured you wouldn't accept this loop after discovering how to do them properly for my other spells. I will work on the loop again!

But systems are there to take usage of them
Outsourcing is something positive for spells, so you don't have to bother about any algorithms you need.

Oh I know xD I love the systems and I want to use them. However, like I said for Bribe, I made this spell to practice my own movement because I've never done it before. I just wanted to keep it this way for reference.


EDIT: Fixes for the loop have been made.

 

[IcemanBo]

So yeah it looks fixed.

Imo add a comment when configuration has ended.
It actually ends already after the timer config.

The boolean array array terrainHit does not to be an array,
and actually it can be removed completly. Just directly check the path before you deindex.

Concept is nothing new, but the spell looks good and is coded well.

Approved

 

[ILikeMacNCheeze]

Looks better than the original.

 

[3xKataratos]

Crash :S

i try to save map after i import the triggers but during the validating script phase world editor crases.. plz help

 

[KILLCIDE]

i try to save map after i import the triggers but during the validating script phase world editor crases.. plz help

Hmmm thats odd... I just ran some tests and never experienced a map crash. Are you sure it's my spell that is causing the crash?

 

[3xKataratos]

Yeap i am sure ...I can also tell u that the problem is on Resources folder. I may have import another knock back type ability but as the variables are different there should be no problem ,right ?

 

[KILLCIDE]

Yeap i am sure ...I can also tell u that the problem is on Resources folder. I may have import another knock back type ability but as the variables are different there should be no problem ,right ?

Wait are you getting a CRASH or just syntax errors? They are completely different things.

 

[KILLCIDE]

Thanks to jonbon for the bug report! Updated to v2.01:

• Added an optional Meteor Strike folder that is integrated with GUI Spell System
• Added Bribe's new knockback system update
• Fixed bug of meteor falling at a completely different location when casted directly on top of the caster
• Removed unnecesary NodeLast[] variable for linked list; last spell instance now stores into NodePrev[0]
• Removed If/Then/Else that would set NodeLast = NodePrev[Spell_ID] if NodeLast == Spell_ID

 

[jonbon29]

Much more good looking than the Invoker's Meteor Strike in Dota.

 

[bazzish]

what item do I use to get the knockback system right?

 

[KILLCIDE]

Awesome!! 5/5

Much more good looking than the Invoker's Meteor Strike in Dota.

Thank you both!

what item do I use to get the knockback system right?

Bribe's knockback system doesn't require any object editor data.

 

[bazzish]

Thank you both!


Bribe's knockback system doesn't require any object editor data.

okey how does It co-work with meteor stike, I don't get the knockback part to work. the rest works fine.

 

[KILLCIDE]

The knockback works fine in my map. Did you import all the resources into your map?

 

[bazzish]

The knockback works fine in my map. Did you import all the resources into your map?

Yeah of course!
Do I need to connect any variables?

 

[KILLCIDE]

No everything should be done for you when you import. Can you send me your map please so I can see?

 

[Jay-B]

you should change the collision size of the meteor dummy unit into 0 so it can pass through trees,structures.etc.. ^^

 

[KILLCIDE]

Yes I probably should ^^ I will be updating this spell along with the rest of my submissions when I have time.

 

[Jay-B]

Yes I probably should ^^ I will be updating this spell along with the rest of my submissions when I have time.

Well i made an ice version in this spell xD just for fun hahahahah

^^ check it out

Falling Effect

Rolling Effect

Stun Changed to Freeze effect

 

[Map Designer]

looks nice. lvl 6 blood mage?

I will use spell animation, i.e. like old mana siphon.

 

[Tal'Rarity]

Condition is missing but its better to use bribe's spell system.

 

[KaiZen7th]

Yummy! Good alternative for Living Meteor of Ragnaros Hero Concept.