Ops, missed this thread.
Yes, magic crash was my first experience with analyzing crash dumps on windows.
Blizzard didn't check addresses of their functions they call carefully, that caused crash. I hope i fixed their check, at least it stopped crashing for me.
Yes, i plan to add that code to new loader. Maybe to make a console application you should run after war2 is started while new loader is not ready.
Let me know if you know some other points in gameplay causing crash, maybe it's quite easy to fix them too.
Would be nice if you could do that war1 conversion maybe add it as an option in the installer?
I thought about an option in the combat installer to switch between war2/war1 textures after the project is finished. Of course if easycompany will not protest. Or make it some other way.
3. The latest color fix
I hope to get finished version that never crash, works as fast as possible and on all the computers ans OS'es the same way, then to include into new combat.
Maybe i need to make some tests myself for that. That is in my plans also.
4. Command engine
What i see is pvpgn-side php-based command engine. Maybe that would be a good way to public API and request modules from people who want to help? Need to think about that.