• 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.
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!
  • ✅ The POLL for Hive's Texturing Contest #34 is OPEN! Vote for the TOP 3 SKINS! 🔗Click here to cast your vote!
  • ✅ The POLL for Hive's Techtree Contest #20 is OPEN! Vote for the TOP 3 FACTIONS! 🔗Click here to cast your vote!

[JASS] Removing a unit... twice?

Status
Not open for further replies.
No it doesn't. GroupRemoveUnit removes the unit from the group, RemoveUnit removes the unit from the game. Your loop will bug because you never remove FirstOfGroup() from the group. So what happens is that since the unit is removed from the game, the handle is considered null and you exit the loop before looping through all units in the group.
 
Thats one good reason to not use RemoveUnit(). It causes Groups to fuck up and slow down by about 50 times (refer to Griffens tests over at wc3c for proofs). Just kill the units and hide them. Let WC3 do the recycling internally. Oh and FirstOfGroup() loops are inefficient. Why not use the boolexpr for that?
 
Status
Not open for further replies.
Back
Top