• Check out the results of the Techtree Contest #19!
  • Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • Create a void inspired texture for Warcraft 3 and enter Hive's 34th Texturing Contest: Void! Click here to enter!
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!

Force Attack

I do not want to use this because:
- dynamic triggers (do i have to explain why?)
- inefficiency through KeyTimers. Plain timers work better for this.
- that AIDS textmacro looks like overkill to me (besides the horrible horrible name; it sounds as if your script was infected). For this application at least.
- What happens to the member overwritten before you abort because the attacker is already in a group?
 
That is the most feedback I've ever gotten, I've posted this on TheHelper, no comments on the coding.

1. No you don't. FIXED - Now using 1 trigger.
2. I might try at that. Done. Using Hashtables?
3. LOL. AIDS. The best system name ever :) Although the system called SEX is better :P
4. Shrugs. Roger that to fix. DONE.

UPDATED!
 
Last edited:
Needs fixing.

1. Dynamic timers are bad. Baaad.

2. Don't try to combine what should be done with multiple triggers and conditions into one big block. Less efficient, and more of a mess.

3. This shouldn't even compile: library ForceAttack initializer OnInit requires //, KT

4. The documentation is false.

5. Conditions are better than actions.
 
Back
Top