Probably two reasons. You only have "two months away from the launch", so no time to re-architecture the existing working save mechanism. Why change it when you

Probably two reasons. You only have "two months away from the launch", so no time to re-architecture the existing working save mechanism. Why change it when you have an infinite amount of other works to be done? It's just a straightforward prioritization problem. Also, it's fairly tricky to make the deterministic replay works. SC definitely do that for network play, but the risk is arguably higher for saving. StarCraft there were lots of synchronization issues even at very last minutes of its beta due to unexpected non-determinism which is probably because the game engine was not designed with that in mind. IIRC, the game would simply shutdown the session in a such case. But if it's from the save file, you don't have a way to detect that so the save file is going to be in a corrupted state with no hope of recovering. In the case of WC3, the engine has been written with lessons learned in the hard way so it should be capable of handling this problem more elegantly.