Starburst Stream GUI

[Daffa]

I suggest to use preload at Map Init

 

[Pyrogasm]

Daffa's correct; the preload only needs to be done once and it should happen at the start of the map. You already have an init trigger, just put it in that. You should put your triggers in between [trigger][/trigger] tags so people can easily read them.

 

[Daffa]

Change author to your name.

DO NOT HARDCODE. Put all dummy and ability information into variables.
Do not use Pause Unit. Do not manipulate vulnerability state.

 

[MyPad]

Changes have been made regarding the resource bundle, specifically the information.

 

[Asuna Tichondrius]

Thanks for review i will change it soon,..

 

[doomhammer99]

please provide few screenshots.

and put the preload and configuration in one trigger.
when preloading a dummy, don't add an expiration to it.
Instead of creating a dummy every time you cast, Create a dummy in the configuration spawning at the center of the map and just order it to do actions.
(e.g)
Preloading:

• -------- Below is the Dummy's raw/ Its variable is integer --------
• Custom scrpt: set udg_DummyRaw = 'o000'
• -------- Below is the Dummy's ability raw/ Its variable is integer --------
• Custom script: set udg_AbilRaw = 'A000'
• -------- Below is Creating a unit and assigning it instantly in one --------
• Custom script: set udg_Dummy = CreateUnit(Player(PLAYER_NEUTRAL_PASSIVE), udg_DummyRaw, 0, 0, 0)
• -------- Below is Adding an ability to Dummy --------
• Custom script: call UnitAddAbility(udg_Dummy, udg_AbilRaw)

 

[MyPad]

Spell Review:

Resource Description:

The spell lacks description as to what it does, requiring one to look for its' basis in the web. Insufficient information about the spell regarding damage dealt, number of slashes, stun duration, etc., has been noted. It is almost unnecessary to post the triggers, since the ability to preview them within the resource bundle is available.

Spell Mechanics:

Notes and Recommended Actions:

• In trigger Starburst Stream Loop, in the first conditional statement, under Then - actions, the line:
  
  
  • Sound - Stop StarburstSound[StarburstLoop] Immediately
  does not appear to have any bearing on the spell. It would be best to remove the line from the trigger.
  
  
• The triggers Preload and SA can be merged into a config/init trigger.
  
  
• In trigger Starburst Stream Loop, in the third conditional statement, under Then - actions,
  the function of the newly-created units seem to be for visual purposes only. It is recommended to use special effects instead.
  
  
• In the same trigger above, in the fourth (and final) conditional statement, under Then - actions, a dummy caster is dynamically created, and given a stun effect ability. The stun duration does not appear to adapt to the level of the caster's ability. It is recommended to use a global dummy unit instead for the spell, since the spell effect behavior is instant, and have the stun effect ability adapt to the level of the caster's ability.
  
  
• In the same trigger, a lot of (last created unit) function calls have been spotted. It would be better to save it into a temporary variable and reference that instead.

Suggestions/Recommendations:

• Why not base the ability off a channel ability? That way, one can, through the Object Editor, manipulate the delay between spell effect (channel) and triggered effects (channel finished). This can even give the players a clue as to when the triggered effects will occur.
  
  
• As a supplement to the above, do not grant invulnerability to the caster upon spell effect. This will add a risk factor when casting the spell, making it rewarding.

Spell Interactions:

The spell grants the caster invulnerability while channeling (triggered). This part can be quite cumbersome for opponents, since it cannot be interrupted, and they also lose control of the targeted unit, thereby making it a little bit unfair for them.

The caster strikes only in a single direction, without the possibility of variable location displacement, even if within the field of view of the target unit.

The repeated death animations of the target unit would not appear to make sense, as the target unit is (based on the Starburst Stream in SAO) expected to be struck and kept alive until the final slash.

The aesthetics of the spell feel more like a drawn-out fight sequence than a rewarding incantation, taking away much of the freedom of usage of that particular unit from the player. The feeling of blandness that arises from the spell affects the overall rating of the resource.

Rating given: 2.7/5.0

Status:

• Awaiting Update

 

[Asuna Tichondrius]

Edited !
- Add more info (damage dealt , slash count, slash delay).
- No longer Invulnerabe when casting.
- Replace Death animation to Hit animation.
- Replace dummy unit effect to special effect

 

[Daffa]

1. Stun does not interrupt the spell.
2. Spell pauses both target and self.
3. The spell can target self.

Some issues that I have discovered so far. Conceptually, it's pretty good ^^

 

[Asuna Tichondrius]

how to interrupt the spell when stunned i have no idea,

 

[Daffa]

One approach is to make the base ability channeling (this turns to make the spell requires to use SetUnitX/Y instead of SetUnitLocation), or detect the stunned debuff. Is getting damaged while doing the spell suppose to be intentional?

 

[KILLCIDE]

Needs Fixed

• Make the loop timer much shorter. 0.2 seconds imo is too slow and can cause bugs if there are multiple instances running.
• There are a few hard-configured aspects of your spell like special effects and their attachement points. I recommend going through them and making them configurable.

Suggestions

• I'd add a multi-configurable array for the other aspects of the spell because why not
• I'm not sure what the interactions are with Pause unit now, but I was never a big fan of it. If there are no problems with it now, I guess we can let it slide.
• You store the caster and target locations in onCast, but never used them
• Consider using Linked List instead of Dynamic Indexing >

Status

Awaiting Update[/COLOR​