Reverse Engineering: Dagda and Wolf’s Lair bugs fixed after 21 years - Independence War II - Edge of Chaos - Community

Off-Canvas Toggle

Off-Canvas Toggle

Search<br>Search Search

Advanced Search<br>Last Downloaded

Raider FighterDescription<br>Replaces the Command section and Storm Petrel with a Raider Fighter

Chaos Trilogy 3 - Chaos Description<br>This mission takes place after Chaos Legacy (Chaos Gate,part 2) The fleet has brough the artifact to a secret research station in the orbit of Jupiter's moon Ganymede. The commonwealth is preparing to take advantage of the artifact...

New Forum Posts

Issue with Drop-Down Menus and a small thought on ...

I-War 1

Login<br>Username<br>Password

Remember Me

Sign in with a passkey<br>Log in

Forgot your password?

Forgot your username?

Create an account

Reverse Engineering: Dagda and Wolf’s Lair bugs fixed after 21 years

I am so excited to share today's news with you: We’ve been able to patch the two most glaring bugs this game had since its release over 21 years ago.<br>Thanks to our community member ZeroPipeline the proprietary .pkg files (which contain the mission logic) have been disassembled into useable source code. Fixes to this code have been made by other members of our community and then put into a community patch mod. Read on for further details.<br>Independence War 2: Edge of Chaos has plagued numerous players with two major bugs since its release in 2001, probably resulting in quite a few broken joysticks and keyboards over all these years:<br>1. The "Wolf's Lair" Mission bug<br>This is mission 22 in Act 2 of the game. There is a high chance that the mission will never progress, because a freighter that is supposed to move isn't doing anything. Thus, the mission cannot be finished.<br>Back in 2010, Stephen Robertson (of Particle Systems) commented on this issue at the GOG forum:<br>It's an old problem which I don't think there's a reliable solution for apart from 'keep trying it until it works', I'm afraid.<br>Going back to the base, then restarting the mission might do it.

In our own forum, people have been angry about this bug almost 15 years ago:<br>I have the exact same problem.<br>Did you solved yours?

Yes, Cyro, we have. Maybe give this game another chance, even if it's been 10 years.<br>2. The "Dagda crash"<br>Every time you visited the Dagda system in Act 2 the game would crash after a while, making it unplayable.<br>This was reported at the GOG forums in 2011:<br>I'm in Act 2 tootling around and everytime I go to Dagda and the NPC 'The Kiwi' speaks to me the game crashes stating that Loader.exe has caused a problem.

People tried various methods to fix this bug, with varying success. Solutions ranged from disabling the sound to setting the game to Windows 98 compatibility mode.<br>Sometimes this worked, a lot of times it didn't, resulting in a lot of frustration.<br>Hey guys. It's NOT solved. I've tried all the tips given here, and nothing has worked. Zip, zilch, nada.

DDM_Reaper_20, I know it's been a long time, but now it should be fixed.<br>But how was it actually done?<br>It all started on the 8th of September 2022 when a discussion between Brandon0sh and ZeroPipeline emerged on the #mods-discussion channel of our Discord:<br>theres 110 original game pkg's, and then there's modded pkg's, but the one im pretty sure we really really want decompiled right away is iacttwo.pkg<br>decompiling the rest would be really cool for making huge mods to the game but starting with iacttwo.pkg will allow us to hopefully fix the Dagda bug

to which ZeroPipeline replied:<br>I am already using the SDK to compile test scripts so I can see what the output looks like. I have a pretty good idea of how it all works. just working to identify the different op codes

From this point onwards, it all just started to go crazy. Over the course of the next few weeks ZeroPipeline and the whole modding team worked together and actually managed to crack the .pkg files wide open. ZeroPipeline wrote a decompiler for the files, which can be accessed right here on Github.<br>This was admittedly the biggest step for fixing long outstanding bugs of the game and an absolutely crazy undertaking. Thanks to ZeroPipeline for doing this!<br>With the source code of the .pkg files now available to all of us, any member of our community can edit the mission scripts, make their own fixes and enhancements and put them back into the game. Thus, a new community patch project was born.<br>Credit for the mission fixes goes to multiple members of our community:<br>@ZeroPipeline wrote a real fix for the Wolf’s Lair mission bug (Act 2 Mission 22):<br>https://github.com/i-war2-community/i-war2-patch/pull/4/commits/8d2b2ca9576cfe6b23dea13e3c162975c6286f02<br>@Kalpa2 fixed the Dagda crash bug which has plagued the game for ages.<br>https://github.com/i-war2-community/i-war2-patch/pull/11<br>Since I’m just a humble casual gamer, I asked @Kalpa2 what was actually the cause for the Dagda crash bug:<br>The short of it is, in the part of Dagda script that handles recreating a new Maas interceptor...