Magical Daggers v1.1

[Rheiko]

Reserved ~

You might want to see this @IcemanBo

 

[Daffa]

You little...

Nice job!

 

[Rheiko]

Thanks

 

[IcemanBo]

Nice. I would maybe slightly decrease the moving speed as personal config, and decrease quite some start-offset (is 100, but not configurable atm). For some performance boost you maybe could create only 1 dummy caster, I think you even made one tutorial about it. ;p I like you seperated 1st and 2nd damage.

 

[Rheiko]

I actually created 1 dummy caster at first, I dunno why I changed it to that. I was half asleep while making this.
I never thought the start offset matter, I will add it to the configuration later.

;p I like you seperated 1st and 2nd damage.

Because I think it is kinda OP if I leave it with my default settings.

Thanks for the feedback, appreciate it!

Edit: Updated!
I forgot to put the version next to the spell's name the moment I uploaded this and since it's just a minor update, I think it's fine as v1.0 for now.
DummyCast is only created on init now.
Added StartOffset configuration.

Cheers ~

 

[Panda]

I feel like the missles should come back to the warden much sooner, they seem to come back after 5 seconds which seems too long to me but thats just me.

 

[KILLCIDE]

They're configurable, The Panda most of the time, the state of the spell you see when it is uploaded just has arbitrary values.

 

[Panda]

They're configurable, The Panda most of the time, the state of the spell you see when it is uploaded just has arbitrary values.

Ohh I see.

 

[Rogue Kessler]

This is really cool!

 

[Rheiko]

I'm pretty sure the delay only takes 3 seconds. But as Killcide said, it's configurable. Change it to your liking. ~

This is really cool!

Thanks!

 

[MyPad]

Just a small suggestion with the spell:

Why not play the spell animation for when the missiles return?

 

[Rheiko]

Because in my imagination, the daggers automatically return to the caster. It is magical, after all. So there is no need for a sign or anything to make them return. That's why I didn't make the caster play spell animation when they return.

I like the idea, though. I'll consider it.

 

[MyPad]

A late reply, but I would like to clarify what I had thought...

Upon the daggers reaching the Warden, the Warden optionally plays the spell animation.

 

[KILLCIDE]

Awesome spell concept!

Needs Fixed

• Nothing

Suggestions

• You should always add attachment point configurables for every special effect configurable. Some special effects won't always work for the same attachment point.
• Attack type and damage type should be configurable
• When you preload the dummy units, you're using their data from the Object Editor rather than the variables.
• I'd make the periodic timer into a variable. Since you use the value 0.03 in main code, the spooky math will break if the user decides to change just the periodic timer.
• That deallocation block looks DISGUSTING ! You should seriously consider Linked List

Status

Approved​

 

[Ofel]

Like the concept.

Hi there.

 

[ArneXis]

Cool spell, but the dummy units should be linked to variables from the start. It's annoying to search the unit in the unit editor for each reference.

 

[Elprede]

Please explain what you meant by "dummy untis should be linked to variables from the start."

 

[Ofel]

Please explain what you meant by "dummy untis should be linked to variables from the start."

Maybe he meant that the dummy unit type should be easily configurable for users.

 

[Daffa]

I checked the code and it's already available in the Init trigger.

 

[ArneXis]

What I was trying to point out this.



My map has over 500 custom units and even when you copy the dummy units into the map first they are not assigned to the trigger properly when its copied (random custom units are assigned, dunno why).
Its annoying to have go around and assign every reference again.

 

[Pyrogasm]

random custom units are assigned, dunno why

The unit in your map that has the rawcode that matches the unit in the source map is the one that gets 'put' in the trigger, because the editor thinks you already have that unit in your map (because the rawcodes match). It's not random.

 

[ArneXis]

The unit in your map that has the rawcode that matches the unit in the source map is the one that gets 'put' in the trigger, because the editor thinks you already have that unit in your map (because the rawcodes match). It's not random.

Yeah I suspected something along those lines.

 

[Ofel]

I guess there's no other way for that.
You must reconfigure it manually.

 

[Daffa]

Have it overrided with the variable at the config so there's no need for depth search.

 

[Deathkok]

Nice spell, thanks good job.

 

[HeLLsm]

I have a small problem. I used your spell, and when I cast it in-game, a huge dagger model appears at the place of the caster. What did I do wrong, why does it appear there?

 

[Rogue Kessler]

I have a small problem. I used your spell, and when I cast it in-game, a huge dagger model appears at the place of the caster. What did I do wrong, why does it appear there?
View attachment 330048

Looks like this model by Blood Raven. Moiety Dagger
Nevermind, that's the same model included in this resource. Ignore me.

 

[Daffa]

Does any config look out of place?

 

[HeLLsm]

Does any config look out of place?

No, I checked it so many times and I can't find what's wrong.
EDIT: Or at least I think so..

 

[HeLLsm]

I posted my problem here: Spell model problem. I also included my map with the issue in there, so if you want to help, answer there, please.

 

[SadOnix]

awesome spell!

 

[Rheiko]

I know it's been like 6 years but hey, why not.

Updated to v1.1:

• Attachment point for SFX[1] is now configurable
• Attack type and Damage type is now configurable
• Preloading dummy unit and abilities now use their proper data from variables instead of object data
• Periodic Timer is now a variable and added from MDG Init trigger

Basically almost everything @KILLCIDE suggested.
Also fixed the part where when I create dummy unit, I used the object data instead of variable as pointed out by @ArneXis. It's a complete oversight from me, I apologize. That's it, cheers!

 

[LightMidnight]

I know it's been like 6 years but hey, why not.

Updated to v1.1:

• Attachment point for SFX[1] is now configurable
• Attack type and Damage type is now configurable
• Preloading dummy unit and abilities now use their proper data from variables instead of object data
• Periodic Timer is now a variable and added from MDG Init trigger

Basically almost everything @KILLCIDE suggested.
Also fixed the part where when I create dummy unit, I used the object data instead of variable as pointed out by @ArneXis. It's a complete oversight from me, I apologize. That's it, cheers!

Not sure why but when i cast the spell it deals more damage than it should.
I changed the damage to 50/50 to test and units take between 100 and 200 damage per cast at random. I haven't changed anything outside of damage numbers and installed the spell as per instruction.
(I think the spell is supposed to deal damage only once per "direction" aka twice per cast)

Edit: Even in the test map damage dealt looks to be random.

 

[Rheiko]

Please re-read the description. It deals damage per dagger not per direction. When multiple daggers hit the enemy unit, the damage will add up. That's most likely the reason the spell deals more damage than you think it should.

 

[LightMidnight]

Please re-read the description. It deals damage per dagger not per direction. When multiple daggers hit the enemy unit, the damage will add up. That's most likely the reason the spell deals more damage than you think it should.

Alright, i must have misunderstood this.

Is there a quick way to make it deal damage once per direction?

 

[Pyrogasm]

The issue is mostly with the way Rheiko structured this. Instead of tracking instances of the dagger fan as a whole, it tracks each dagger individually. That means that there isn't one group that applies to all daggers in a cast, and you can't look at the full list of dagger instances to determine which ones should group together.

You can, however, just alter the groups it creates for the daggers so that each cast all collectively share one group under-the-hood. To do that, you'll need to identify which singular group should exist, assign it to a variable, and then make all the relevant indices of MDG_UndamagedGroup[] point to that variable instead of to their own empty groups. Then repeat this process for MDG_UndamagedGroup2[]. This will introduce one possible error: since all of the groups will be shared, when the first instance in the list ends it will destroy the groups, but the rest of the instances will still check things with that (now destroyed) group once before they too 'end'. Probably won't cause any issues, but it's possible some conflux of fate causes a problem on that exact iteration of the loop trigger. Anyway:

• Create 2 group variables: MDG_UG and MDG_UG2
• Look in the cast trigger for this comment above some custom script lines: Create a group to filter enemy units that have been damaged
• Leave the CS lines there, but put them inside the "then" block of an If/Then/Else, and add a couple more variable assignments. Should look like this:

• -------- Create a group to filter enemy units that have been damaged --------
• If (All conditions are true) then do (Then Actions) else do (Else Actions)
  • If - Conditions
    • MDG_TempInteger equal to 1
  • Then - Actions
    • // put all 6 of those CS lines here, followed by:
    • Set MDG_UG = MDG_UndamagedGroup[MDG_MaxIndex]
    • Set MDG_UG2 = MDG_UndamagedGroup2[MDG_MaxIndex]
  • Else - Actions
    • Set MDG_UndamagedGroup[MDG_MaxIndex] = MDG_UG
    • Set MDG_UndamagedGroup2[MDG_MaxIndex] = MDG_UG2

 

[LightMidnight]

The issue is mostly with the way Rheiko structured this. Instead of tracking instances of the dagger fan as a whole, it tracks each dagger individually. That means that there isn't one group that applies to all daggers in a cast, and you can't look at the full list of dagger instances to determine which ones should group together.

You can, however, just alter the groups it creates for the daggers so that each cast all collectively share one group under-the-hood. To do that, you'll need to identify which singular group should exist, assign it to a variable, and then make all the relevant indices of MDG_UndamagedGroup[] point to that variable instead of to their own empty groups. Then repeat this process for MDG_UndamagedGroup2[]. This will introduce one possible error: since all of the groups will be shared, when the first instance in the list ends it will destroy the groups, but the rest of the instances will still check things with that (now destroyed) group once before they too 'end'. Probably won't cause any issues, but it's possible some conflux of fate causes a problem on that exact iteration of the loop trigger. Anyway:

• Create 2 group variables: MDG_UG and MDG_UG2
• Look in the cast trigger for this comment above some custom script lines: Create a group to filter enemy units that have been damaged
• Leave the CS lines there, but put them inside the "then" block of an If/Then/Else, and add a couple more variable assignments. Should look like this:

• -------- Create a group to filter enemy units that have been damaged --------
• If (All conditions are true) then do (Then Actions) else do (Else Actions)
  • If - Conditions
    • MDG_TempInteger equal to 1
  • Then - Actions
    • // put all 6 of those CS lines here, followed by:
    • Set MDG_UG = MDG_UndamagedGroup[MDG_MaxIndex]
    • Set MDG_UG2 = MDG_UndamagedGroup2[MDG_MaxIndex]
  • Else - Actions
    • Set MDG_UndamagedGroup[MDG_MaxIndex] = MDG_UG
    • Set MDG_UndamagedGroup2[MDG_MaxIndex] = MDG_UG2

Thanks, i'm going to try this