1004 // Some weapons, deagle in particular, wouldn't play so nice in infinite attack mode if hogs were still moving.  Most likely scenario

  1004 //if isInMultiShoot and not AllInactive and (Hedgehog^.CurAmmoType in [amShotgun, amDEagle, amSniperRifle]) then HHGear^.Message:= HHGear^.Message and not gmAttack;

  1005 // is trying to shoot them twice while rolling.  This is mostly about not wasting ammo, but shouldn't apply to gears not using AmmoShove (portal

  1005 if isInMultiShoot and (Hedgehog^.CurAmmoType in [amShotgun, amDEagle, amSniperRifle]) then

  1006 // Should we rethink AmmoShove? Presumably we'd need a way of knowing if current gear had already attacked a gear

  1006     begin

  1007 if isInMultiShoot and not AllInactive and (Hedgehog^.CurAmmoType in [amShotgun, amDEagle, amSniperRifle]) then HHGear^.Message:= HHGear^.Message and not gmAttack;

  1007     AllInactive:= true;

  1008 (*

  1008     HHGear^.Message:= 0

  1009 if isInMultiShoot then

  1009     end

  1010     HHGear^.Message:= 0;

  1010 else AllInactive:= false;

  1011 *)

  1012 

  1013 (*if ((Ammoz[CurrentHedgehog^.CurAmmoType].Ammo.Propz and ammoprop_Utility) <> 0) and isInMultiShoot then 

  1014     AllInactive:= true

  1015 else if not isInMultiShoot then

  1016    AllInactive:= false;*)

  1017  AllInactive:= false;

  1134     if Hedgehog^.Gear <> nil then

  1127     if not(isInMultiShoot and (Hedgehog^.CurAmmoType in [amShotgun, amDEagle, amSniperRifle])) and (Hedgehog^.Gear <> nil) then