Routing bug

[alexti]

Chazar said:
Although I wonder why it sometimes notices that the client is of the wrong Version (2.08 vs 2.12) and sometimes not (2.12 vs 2.14)?

It depends if the algorithm passes through the branch with altered RNG calls or not. For example, if commander had burning pearl, he would have 100% fire resistance and when he was hit by the fire damage spell or weapon, RNG wouldn't be called. After the patch his resistance went down to 50% and RNG had to be called in that case to determine amount of damage. After that all subsequent RNG calls get shifted by one, which will produce different results.

Example:
RNG sequence:
1
6
6
5
1

Actions:
Mage A casts fire flies and it hits enemy commander,
Mage B casts soul slay on enemy's Air Queen with 25MR.

Server:
- commander has 50% fire resistance, the fire damage rolls uses first RNG number, 1 and deals appropriate damage.
- mage B rolls his number for MR check: 6. Roll again: 6. Roll again: 5. Ok, 11+17=28 total. AQ rolls its MR check: 1. 25+1=26. AQ is dead.

Client:
- commander has 100% fire resistance, so no fire damage roll is needed.
- mage B rolls his number for MR check: 1. Ok, 11+1=12 total. AQ rolls its MR check: 17. 25+17=42. No problem for AQ.