Also on AOL
- Autos
- Technology
- Lifestyle
- Gaming
- Finance
- Entertainment on AOL
- Lifestyle on AOL
- Sports on AOL
- Travel on AOL
- More on AOL
Featured Galleries
Joystiq
© 2013 AOL Inc. All rights Reserved. Privacy Policy | Terms of Use | Trademarks | AOL A-Z HELP | About Our Ads

Reader Comments (Page 1 of 1)
4-30-2011 @ 8:26PM
Mugutu said...
Incoming copypasta, plus a few edits, from a few weeks ago:
Ignite munching happens because of when crits actually happen in relation to each other. Take a combat log that looks like this (simplified)
[15:35:01] Fireball crits for 25000.
[15:35:02] Pyroblast! crits for 30000.
That would work fine, and both spells would properly proc Ignite. Now look at this:
[15:35:01] Fireball crits for 25000.
[15:35:01] Pyroblast! crits for 30000.
This situation is entirely possible if one casts a Pyroblast too soon after a Fireball - both spells hit at the same time, as far as the server is concerned. This is when Ignite munching happens. Both appear to be at the same time and the server can only handle one action, so it chooses the most recent one.
It can't really stack properly because of how it procs. Blood Shield can't proc twice at the same time, so it has no problem stacking.
Interchange "Pyroblast! crits for 30000" with something like "Living Bomb crits for 4500" and I think the problem is clear.