• 🏆 Texturing Contest #33 is OPEN! Contestants must re-texture a SD unit model found in-game (Warcraft 3 Classic), recreating the unit into a peaceful NPC version. 🔗Click here to enter!
  • 🏆 Hive's 6th HD Modeling Contest: Mechanical is now open! Design and model a mechanical creature, mechanized animal, a futuristic robotic being, or anything else your imagination can tinker with! 📅 Submissions close on June 30, 2024. Don't miss this opportunity to let your creativity shine! Enter now and show us your mechanical masterpiece! 🔗 Click here to enter!

Create a exe w3 with save game and debug

Status
Not open for further replies.
Level 5
Joined
Jan 26, 2015
Messages
94
Its possible make a exe to run the map w3 with a external program debug. So the external debug find a bug. The game map is save alone or multiplayer and you can continue the game loading the map saving alone or multiplayer
 

Dr Super Good

Spell Reviewer
Level 64
Joined
Jan 18, 2005
Messages
27,207
No it is not possible as the Warcraft III source code is not in the public domain (unfortunately).

You can attach assembly debuggers to the Warcraft III process at any time. However good luck finding a bug with one! If you are brave enough to try this my personal favorite is ollydbg. Start WC3 and attach it to the Warcraft III process when you want to debug. Do note that doing this violates the Warcraft III terms of use, will probably get you banned from BattleNet if done while connected to BattleNet and is technically illegal in most countries.

However do not get your hopes up, I tried doing this for "compatibility between software" reasons (so that I could create a blp library that accurately reads blp files as their public documentation is terrible) and had practically no luck after hours of trying.
 
Level 5
Joined
Jan 26, 2015
Messages
94
No it is not possible as the Warcraft III source code is not in the public domain (unfortunately).

You can attach assembly debuggers to the Warcraft III process at any time. However good luck finding a bug with one! If you are brave enough to try this my personal favorite is ollydbg. Start WC3 and attach it to the Warcraft III process when you want to debug. Do note that doing this violates the Warcraft III terms of use, will probably get you banned from BattleNet if done while connected to BattleNet and is technically illegal in most countries.

However do not get your hopes up, I tried doing this for "compatibility between software" reasons (so that I could create a blp library that accurately reads blp files as their public documentation is terrible) and had practically no luck after hours of trying.


But yo could by save the game before the map and game crash, so its a temporary use this method for play alone or multiplayer. Or its impossible?
 

Dr Super Good

Spell Reviewer
Level 64
Joined
Jan 18, 2005
Messages
27,207
But yo could by save the game before the map and game crash, so its a temporary use this method for play alone or multiplayer. Or its impossible?
The grammar of what you are asking makes no sense.

Save games are not an accurate state capture. As such after loading a crash may not occur that happened after it was originally saved. Many systems also break after load, such as periodic timers are set to "one-shot" and all data in any array index 8191 is lost.

It is far better to use a replay to reproduce a crash since that advances game state until the point of crash. Further more they can be dumped in parallel with game progression so even if the game crashes the replay will run until that point.

It is always possible to attach the debugger to the Warcraft III process however if it helps you is another question. Trying to understand part of ~1,000,000 lines of undocumented, compiler writted x86 assembly is not really humanly possible. Do note that if you attach it during a multiplayer game chances are you will lag out as every time you break it will stop all network communication for a period.
 
Level 5
Joined
Jan 26, 2015
Messages
94
The grammar of what you are asking makes no sense.

Save games are not an accurate state capture. As such after loading a crash may not occur that happened after it was originally saved. Many systems also break after load, such as periodic timers are set to "one-shot" and all data in any array index 8191 is lost.

It is far better to use a replay to reproduce a crash since that advances game state until the point of crash. Further more they can be dumped in parallel with game progression so even if the game crashes the replay will run until that point.

It is always possible to attach the debugger to the Warcraft III process however if it helps you is another question. Trying to understand part of ~1,000,000 lines of undocumented, compiler writted x86 assembly is not really humanly possible. Do note that if you attach it during a multiplayer game chances are you will lag out as every time you break it will stop all network communication for a period.


So dont exist a solution?. Its impossible fix temporary this problem?. You could fix debugging, but you dont know how the game and map crash. Any solution for no lost the progress in the map game?. And begin again?
 
Level 5
Joined
Jan 26, 2015
Messages
94
If the game crashes then all state is as good as lost. It is called a crash for a reason. This is why you usually save often in games. So sad WC3's save function is bugged so one cannot do this.

Sharpcraft cant do offer a solution for this?
 
Status
Not open for further replies.
Top