- Joined
- Dec 12, 2010
- Messages
- 2,069
I found issue with WC3's cast system.
apparently Blizzard's decided to optimize a bit and, instead of calling GetUnitCastpoint() everytime unit starts spell casting, they cache value somewhere inside spell's structure. Thats mean spell will keep this value until removed from hero.
Example: I created MyHero's dummy hero unit with all the same stats but backswing = 0.00. When player first time learns spell i want to remove backswing from, I do remove ability from unit, morph unit to dummy, add ability back, unmorph him back. Voila - now MyHero can use spell and wont suffer of backswing. Works for cast point as well.
Funny enough, its also affects unit's coloring if dummy has different settings there.
This thing will be tested, but i wonder, if someone already had experience with such abuses (morphing forth and back in order to derive some unit data into another)? Is there any side effect?
apparently Blizzard's decided to optimize a bit and, instead of calling GetUnitCastpoint() everytime unit starts spell casting, they cache value somewhere inside spell's structure. Thats mean spell will keep this value until removed from hero.
Example: I created MyHero's dummy hero unit with all the same stats but backswing = 0.00. When player first time learns spell i want to remove backswing from, I do remove ability from unit, morph unit to dummy, add ability back, unmorph him back. Voila - now MyHero can use spell and wont suffer of backswing. Works for cast point as well.
Funny enough, its also affects unit's coloring if dummy has different settings there.
This thing will be tested, but i wonder, if someone already had experience with such abuses (morphing forth and back in order to derive some unit data into another)? Is there any side effect?
