Unit Triggered Movement System/Projectile System

[Devalut]

Always excited for new projectile systems!

 

[Pyrogasm]

Relying on InitTrig functions (which will not work if the name of the trigger is changed) and not using simple scoping and encapsulation keywords like private/public (which would reduce your variable names significantly) are big no-nos in my book.

That this system doesn’t allow you to track a unit target instead of an xy target is a serious deficiency, as that is something one usually needs a projectile to do.

Why would I use this system over any others already in the database? What does it provide, optimize, improve upon, or execute in some novel way?

 

[NightKnight]

That this system doesn’t allow you to track a unit target instead of an xy target is a serious deficiency, as that is something one usually needs a projectile to do.?

As in the notes, I made this system for fixed points projectiles like skillshots, which can't change directions. Making it track a unit is easy to make, in fact it will be a small edit, but having both the tracking mechanic and the fixed point mechanic in 1 system can be confusing. The reason this system is fixed point one is because I actually made this one for my needs.

Why would I use this system over any others already in the database? What does it provide, optimize, improve upon, or execute in some novel way?

I didn't really check out any other projectile system, but I decided to share mine. I think mine is very fast to use, as only needs 1 line of code, and has many customizations and features like the ending explosion, and activated triggers, and the rest of the things in "Features" part of the post. I can also make versions with more customizations upon request, but the public version will stay as this, as 16 fields is already a big number.

Always excited for new projectile systems!

Cool . Hope this be helpful.

 

[MyPad]

I have edited the title of the system to not include the tags in them, as they are already indicated in the bundle.

Also, going by the trigger comments themselves, I suppose this caters more to the GUI users themselves than JASS/vJASS users. I suggest that there should be a simpler constructor for the JASS users, as having 16 arguments for a constructor call can significantly decrease readability in the script, and subsequently hinder attempts at debugging things related to projectile movement.

Spoiler: Review

Code:

Spoiler: Review

Relying on InitTrig functions (which will not work if the name of the trigger is changed) and not using simple scoping and encapsulation keywords like private/public

• The system can be encapsulated in a library named UnitMovingPoint. Then, you can make the constituent global variables private to that library.

​

• The function UnitMovingPointRun does not appear to stop when there are no instances provided to the system. This should be addressed by pausing the timer whenever it isn't in use (e.g. No instances -> UnitMovingPointInd == 0).

• Consequently, UnitMovingPointInit should restart the system when the timer is paused.

​

• The system will be better off as a struct which can support multiple constructors. Of course, the allocate and deallocate methods can be defined by extending the struct via extends array.

• 
  
  • The one-line constructor can be incorporated here as a static method to the struct.
• The system can be made to actually support special effects as projectiles, not just dummy units acting as special effects. (From Patch 1.29+)

this system doesn’t allow you to track a unit target instead of an xy target is a serious deficiency, as that is something one usually needs a projectile to do.

Given that there are a lot of issues/things that can be addressed/included, it would be best to move this to Awaiting Update

 

[NightKnight]

Sorry for the delayed response.

As for the vjass suggestions, I still haven't learned vJass except for the globals. So I would like if the system can be reviewed as it is currently, and I will update later when I find time to learn vjass.

For restarting the system when no instances are running, I will do that once I have time.

 

[Pyrogasm]

I still haven't learned vJass except for the globals.

JassHelper 0.A.0.0 It's really not complicated.

 

[NightKnight]

Sorry for the delay. However, I don't really intend to re-write this system in vJass currently.

 

[MyPad]

Fixed spoiler tags in system description.

Sorry for the delay. However, I don't really intend to re-write this system in vJass currently.

On matters concerning initialization, a library initializer will suffice for this system, since it doesn't require anything else. This would not even require one to rename their initializing function.

 

[NightKnight]

Updated

 

[kentzeus]

How do I get the projectile unit variable when using an ending trigger? I tried

• Custom script: set udg_unit = UnitMovingPointU[UnitMovingPointInd]

But it doesn't work, this assigns "no unit".

 

[NightKnight]

It's not UnitMovingPointInd, it's udg_UnitMovingPointActiveInd

I made an example using it in the test map.

 

[kentzeus]

It's not UnitMovingPointInd, it's udg_UnitMovingPointActiveInd

I made an example using it in the test map.

Oh, my bad

I'm still testing it but it seems nice so far. It would be cool if there was an option to arc the missile too, and that it could collide with buildings, trees etc aswell.

 

[NightKnight]

No problem . If you face issues, don't hesitate to ask.

 

[Zoson]

Why not use the new special effect natives for the projectile system?
Special Effects have the big advantage that they can be used kinda locally, meaning setting the effect path for all others to an empty string, and only to the desired effect for target player.
Also Units are much more performance taking than special effects. We have those natives now, use them.

 

[NightKnight]

I plan to add that in the future.

 

[Tal'Rarity]

Why not use the new special effect natives for the projectile system?
Special Effects have the big advantage that they can be used kinda locally, meaning setting the effect path for all others to an empty string, and only to the desired effect for target player.
Also Units are much more performance taking than special effects. We have those natives now, use them.

Sfxs have bad support for colliding against sfxs, units can also be used locally however way more limiting until we can create new object editor content in game. That's why you have to use dead dummy units aka corpses or locusted dummy units to reduce their performance costs. Just because something is new doesn't always mean better, the sfx natives do handle movement a little better at least.

 

[kentzeus]

I don't know if it would be too complicated but it would be cool if there was an option to arc the missile

 

[NightKnight]

I don't know if it would be too complicated but it would be cool if there was an option to arc the missile

Sure

 

[kentzeus]

Sure

That's awesome Thanks!

Edit: The ExplodeSFX is not working when arcing, though the explosion damage is still working as expected.

 

[zxxzyyz]

How can I make a spell like [Projectile running damage path] but deals damage only once to each unit?

 

[NightKnight]

How can I make a spell like [Projectile running damage path] but deals damage only once to each unit?

By having CheckRange value equals half the speed value.