• Check out the results of the Techtree Contest #19!
  • Listen to a special audio message from Bill Roper to the Hive Workshop community (Bill is a former Vice President of Blizzard Entertainment, Producer, Designer, Musician, Voice Actor) 🔗Click here to hear his message!
  • Read Evilhog's interview with Gregory Alper, the original composer of the music for WarCraft: Orcs & Humans 🔗Click here to read the full interview.
  • Create a void inspired texture for Warcraft 3 and enter Hive's 34th Texturing Contest: Void! Click here to enter!
  • The Hive's 22nd Icon Contest: Creep Abilities is now concluded, time to vote for your favourite set of icons! Click here to vote!

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
 
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.
 
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?
 
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.
 
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?
 
Status
Not open for further replies.
Back
Top