"To The Death", a.k.a. WirHack v2.1

Ed Cogburn · Post by **Ed Cogburn** » Wed Oct 24, 2001 8:45 am

Get it here:

http://www.xtn.net/~ecogburn/wirhack.zip

Small updates to the scenario. A few new notes in readme.txt, but the real new features are 2 new hacks, one that prevents conversion of a Pz battalion to a Jpz battalion, and another that blocks Stug-IIIg tanks from being put in Pz battalions. They are by default OFF in whedit.

Those of you who take control of production and rebalance the production distribution of Tanks/Stugs/TDs will definitely want these hacks. If you play with the computer handling production do NOT use these hacks.

I ran a game to '45 twice and didn't see anything obviously wrong when checking every 6 months, but because these hacks are barely more than just educated guesses as to what to change in the code, you may want to be careful. I'm not ready yet to declare these new hacks as "correct". So anybody willing to run a game comp vs. comp, and look at things every 3-5 months to verify my results, I would really appreciate the extra help in testing.

IMPORTANT: Please note that Campaign '41 and other scenarios as well, do have a few divisions with Jpz battalions already having Stug-IIIg tanks when they arrive in the game. I've modified my scenario, TTD, to change these battalions to tank destroyers, so in my scenario you'll never see Stugs in a Pz or Jpz battalion. If you play the other scenarios, you will see this, so check the battalion in obwir using editwir before proclaiming it a bug.

Yogi Yohan · Post by **Yogi Yohan** » Wed Oct 24, 2001 9:52 pm

Again, thanks a bunch Ed!

This is just what I wanted and I got it QUICKLY!
Would you consider taking a position for Microsoft customer support...PLEASE? They could use you... <img src="biggrin.gif" border="0">

Mist · Post by **Mist** » Thu Oct 25, 2001 12:53 am

Originally posted by Yogi Yohan:
Again, thanks a bunch Ed!

This is just what I wanted and I got it QUICKLY!
Would you consider taking a position for Microsoft customer support...PLEASE? They could use you... <img src="biggrin.gif" border="0">

<img src="biggrin.gif" border="0"> Yes, Ed, you would made very good frontend for Windoze. I'd propose the following item to be included ASAP there: "Prevent Windows from crashing" yes by default in winhack.exe
Nice?

Ed Cogburn · Post by **Ed Cogburn** » Thu Oct 25, 2001 11:58 am

Originally posted by Yogi Yohan:
Again, thanks a bunch Ed!

This is just what I wanted and I got it QUICKLY!
Would you consider taking a position for Microsoft customer support...PLEASE? They could use you... <img src="biggrin.gif" border="0">

"MS's Customer Support". Hmmm, isn't that an oxymoron? <img src="biggrin.gif" border="0">

Ed Cogburn · Post by **Ed Cogburn** » Thu Oct 25, 2001 12:01 pm

Originally posted by Mist:
Yes, Ed, you would made very good frontend for Windoze. I'd propose the following item to be included ASAP there: "Prevent Windows from crashing" yes by default in winhack.exe
Nice?

<img src="biggrin.gif" border="0"> That's funny, but I'm absolutely convinced that if a take just a 15 minute look at MS code, I would go completely and totally insane.

Yogi Yohan · Post by **Yogi Yohan** » Mon Oct 29, 2001 3:52 pm

Ed,

I've discovered a problem with the block StuG hack feature. When it's activated, all vehicle replacements are blocked, even by special supply. Check out the 22nd and 23rd Panzer in OKW on the first turn of the -41 campaign.

Tom1939 · Post by **Tom1939** » Mon Oct 29, 2001 4:59 pm

Yogi, you mean all panzer replacement or just all stug replacement? As I have a game going this is important for me... I don't really care if it is only stug's, but all panzer's would hurt. Thanks for the answer.

Yogi Yohan · Post by **Yogi Yohan** » Mon Oct 29, 2001 7:02 pm

Originally posted by Tom1939:
Yogi, you mean all panzer replacement or just all stug replacement? As I have a game going this is important for me... I don't really care if it is only stug's, but all panzer's would hurt. Thanks for the answer.

I mean all Panzer battallions in Panzerdivisions. I don't know about StuG battallions or independendent PzBn but those in PzDivisions do not seem to recieve any replacements.

[ October 29, 2001: Message edited by: Yogi Yohan ]</p>

Ed Cogburn · Post by **Ed Cogburn** » Tue Oct 30, 2001 11:44 am

Originally posted by Yogi Yohan:

I mean all Panzer battallions in Panzerdivisions.

Damn, it was too easy, I should have known better. This is why I wasn't sure it was "correct". Ok, lets try this again shall we? <img src="smile.gif" border="0">

WiRhack v2.11:
http://www.xtn.net/~ecogburn/wirhack.zip

I've left wirhack.exe out of the zip as its no longer necessary and makes the zip file so large. Just put whedit in the WiR directory, copy wir.exe (v3.101) to wirhack.exe, run whedit, select which hacks you want, hit the "Exit and Save" button, and run wirhack.exe.

Yogi Yohan · Post by **Yogi Yohan** » Tue Oct 30, 2001 2:20 pm

Originally posted by Ed Cogburn:

Damn, it was too easy, I should have known better. This is why I wasn't sure it was "correct". Ok, lets try this again shall we? <img src="smile.gif" border="0">

WiRhack v2.11:
http://www.xtn.net/~ecogburn/wirhack.zip

I've left wirhack.exe out of the zip as its no longer necessary and makes the zip file so large. Just put whedit in the WiR directory, copy wir.exe (v3.101) to wirhack.exe, run whedit, select which hacks you want, hit the "Exit and Save" button, and run wirhack.exe.

This apparently did the trick Ed, thanks!

Important for others using WHEdit , you must delete your old WiRHack file and make a fresh copy of WIR.exe named WIRHack.exe, since the StuG problem will remain in the old file even after having been edited with the new WHedit.

Yogi Yohan · Post by **Yogi Yohan** » Tue Nov 06, 2001 3:43 pm

Ed,

I just realized that the StuGs in PzBns is probably because the PzKpfw-IIIm has StuG-IIIg as upgrade. In this way, you can get any kind of equipment in any kind of subunit.

So all we needed to do to avoid this was to change the upgrade path for Pz-IIIm to 254 - none (or Pz-IVh or Panther or whatever we feel is appropiate - even Tigers, for those in that kind of mood <img src="biggrin.gif" border="0"> ).

Sorry I did not discover this before you went to all that work to block it in WIRHack. The blocked conversion of PzBn to JPzBn is still a great improvement though.

Ed Cogburn · Post by **Ed Cogburn** » Wed Nov 07, 2001 5:51 am

Originally posted by Yogi Yohan:
Ed,

I just realized that the StuGs in PzBns is probably because the PzKpfw-IIIm has StuG-IIIg as upgrade. In this way, you can get any kind of equipment in any kind of subunit.

So all we needed to do to avoid this was to change the upgrade path for Pz-IIIm to 254 - none (or Pz-IVh or Panther or whatever we feel is appropiate - even Tigers, for those in that kind of mood <img src="biggrin.gif" border="0"> ).

Sorry I did not discover this before you went to all that work to block it in WIRHack. The blocked conversion of PzBn to JPzBn is still a great improvement though.

You may be right, but I'm not sure. See, if the code I disabled was the code that did the normal conversion from one piece of equipment to the next one, all conversions would be blocked. Like other situations with WIR, the code I blocked was "special purpose" code for changing pz btns to stugs. The number for Stug-IIIg tanks (the slot number you see under Tank Types in editwir) was hardwired in this code. If the game were set up normally, using the slot in the scenario file for the tank upgrade info, there would be no reason for the code I blocked to even exist. So why is that special purpose code there, and being used, if the game is getting the tank upgrade info from the scenario file? Hmmm.....

BTW, the tank upgrade info is not in the first version of WiR, it was added later by Arnaud. In other words, in the first version, everything was hardwired in the code. Perhaps he just missed this special purpose code when converting from the upgrade info being hardwired in the code to getting the upgrade info from the scenario file? I'm ask him...