• 🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
  • It's time for the first HD Modeling Contest of 2024. Join the theme discussion for Hive's HD Modeling Contest #6! Click here to post your idea!

Spell's Deadeye 1.3

This bundle is marked as useful / simple. Simplicity is bliss, low effort and/or may contain minor bugs.
I'm new to this community and wanted to say that I have many doubts about how it works, I'm not very good conosimientos on GUI or JASS but this pac spell ise a little simpler than enjoy.

-also want to give me tips to improve my knowledge.


Keywords:
Deadeye, purple, tree, pack, spells
Contents

Deadeye (spellPack) (Map)

Reviews
10:43, 31st May 2016 Tank-Commander: V1.3.2 - While you've fixed the leak issues, In reference to my last sentiment please fix the majority of issues before updating - set back to need fix 10:52, 30th May 2016 Tank-Commander: V1.3 - This...

Moderator

M

Moderator

10:43, 31st May 2016
Tank-Commander: V1.3.2 - While you've fixed the leak issues, In reference to my last sentiment please fix the majority of issues before updating - set back to need fix


10:52, 30th May 2016
Tank-Commander: V1.3 - This version has all the same problems as the previous - please fix the major or majority of issues before updating, I noticed that you changed your leak removal but it is still wrong, please view this tutorial to go over how to clean them properly

18:25, 29th May 2016
Tank-Commander: V1.2 - Thanks for the submission to the spell section - I went over the code quickly, given the multitude of issues found I'm setting it to needs fix, please see my post and I hope to see this fixed up
 
Level 22
Joined
Aug 27, 2013
Messages
3,973
Please post the triggers using the [trigger]YourTriggerHere[/trigger] tags.

  • You have a location leak - Position of DA_Target. //Damn Arrow
  • You have unit groups leak - CR_Group & CR_Group2. //Convenient Ritual
  • You have more location leaks - SsRg_Point1 & SsRg_Point2. //Skeletal Satanic Ritual Target
  • I'm afraid your Skeletal Satanic Ritual is not MUI and it also has many leaks.
 
Level 3
Joined
Apr 17, 2016
Messages
14
Please post the triggers using the [trigger]YourTriggerHere[/trigger] tags.

  • You have a location leak - Position of DA_Target. //Damn Arrow
  • You have unit groups leak - CR_Group & CR_Group2. //Convenient Ritual
  • You have more location leaks - SsRg_Point1 & SsRg_Point2. //Skeletal Satanic Ritual Target
  • I'm afraid your Skeletal Satanic Ritual is not MUI and it also has many leaks.

you updated
 
I went over it pretty quickly, here are some pointers:

Major:
- There's a lot of leaks (DA_PointLoop, DA_Group, etc.) they need to be cleaned before they're reused every time, not just at the end of the trigger
- Dummies should be made for a neutral player as to not interfere with scorescreens
- Constant configurables should be set in a separate trigger, not every time a unit starts the effect of the ability as these values will always be the same
- Only create unique variables for things like points and groups as are needed simultaneously (notably you have 6 location variables for "Damn arrow" when at most 2 are needed
- As said by Reiko Skeletal Satanic Ritual is not MUI and needs to be reworked

Minor:
- Store things such as last created unit into temporary variables if they're used more than twice to reference the same unit, this makes your program run faster
- Try to calculate numbers needed multiple times only once, restructure your codes to do this e.g. the line "Set DA_AoE_Total = (DA_AoE_Initial + (DA_Distance x (Real(DA_LvAbility))))" could be outside of its loop as this doesn't change
- Your group filtering is structured inefficiently - group in range into a group, then pick all the units, store the picked unit in a variable and then use an if-then-else structure to filter the units
- Don't use "Do nothing" functions
- Floating text should be optional (as there is a 100 floating texts per client limit)
- use a 0.03 timer speed instead of a 0.02 timer speed (you don't need 40 frames per second when humans can only see 30 - it adds needless processing)
- Your dummy unit type should be configurable as should all of your abilities used by both the spells and dummies
- I'd also suggest naming your folder the match the spell pack so that when people import it the folder is in an intuitive location (your import guide should also be in the same folder)

You also lack a proper description on the site - describe the spells that you've submitted
 
Level 3
Joined
Apr 17, 2016
Messages
14
I went over it pretty quickly, here are some pointers:

Major:
- There's a lot of leaks (DA_PointLoop, DA_Group, etc.) they need to be cleaned before they're reused every time, not just at the end of the trigger
- Dummies should be made for a neutral player as to not interfere with scorescreens
- Constant configurables should be set in a separate trigger, not every time a unit starts the effect of the ability as these values will always be the same
- Only create unique variables for things like points and groups as are needed simultaneously (notably you have 6 location variables for "Damn arrow" when at most 2 are needed
- As said by Reiko Skeletal Satanic Ritual is not MUI and needs to be reworked

Minor:
- Store things such as last created unit into temporary variables if they're used more than twice to reference the same unit, this makes your program run faster
- Try to calculate numbers needed multiple times only once, restructure your codes to do this e.g. the line "Set DA_AoE_Total = (DA_AoE_Initial + (DA_Distance x (Real(DA_LvAbility))))" could be outside of its loop as this doesn't change
- Your group filtering is structured inefficiently - group in range into a group, then pick all the units, store the picked unit in a variable and then use an if-then-else structure to filter the units
- Don't use "Do nothing" functions
- Floating text should be optional (as there is a 100 floating texts per client limit)
- use a 0.03 timer speed instead of a 0.02 timer speed (you don't need 40 frames per second when humans can only see 30 - it adds needless processing)
- Your dummy unit type should be configurable as should all of your abilities used by both the spells and dummies
- I'd also suggest naming your folder the match the spell pack so that when people import it the folder is in an intuitive location (your import guide should also be in the same folder)

You also lack a proper description on the site - describe the spells that you've submitted

thanks not know all that
 
Top