Fallout 2 Megamod Walkthrough

Fallout 2 Megamod Walkthrough

Fallout 2 Megamod Walkthrough ->>> https://urlgoal.com/2t79OA

The MIB88 megamod is currently version 2.34. This latest version contains some new content, but mostly corrects errors from previous versions of this mod. Also, the worldmap in this version is larger. See also the Megamod FAQ.

Haris wrote: What the mod is about: In this mod you are not the chosen or vault dweller, but a simple mercenary warrior that goes around the wasteland looking for missions/jobs. All missions/jobs are redo-able and are intended to be done multiple times. In this sequel of Wasteland Merc we have taken MMORPG elements to the max in the fallout 2 setting. You are forced to balance your skill points between crafting skills (outdoorsman, repair, science, doctor), thieving skills (sneak, lockpick) and combat skills or you can't make it that far.

So the latest versions of megamod tools use no auto update option the program has.They can almost all be solved by updating all the WeiDU.exe's to the most current version of the WeiDU.exe, which can always be found in here(the Windows Binary archive), you first do the auto update by running one of the setup-*modname*.exe's, and after it has succeeded to update most, you need do the manual update to know what files you need to update manually, and you do that by searching the folder by size, all the up to date setup-*modname*.exe's are about 655Kb's in size(that version was v22600), the outdated are smaller, so you delete the old setup-*modname*.exe, and then you copy the new WeiDU.exe from the archive to the game folder and then you re-copy it to the same folder so you have many of them, and then you rename one of the copies as the deleted one so you can run it.The WeiDU.exe is also moding tool that has it's interface if it's named as WeiDU.exe, and for Windows Vista and Windows 7 users, remember that you have to disable the UAC, read the answer #2, or use it as Administrator, whenever you try to use it cause it won't work without the proper user permissions and file allocations. Additionally, the WeiDU.exe renamed as setup-*modname*.exe has many times falsely detected as a virus by many anti-virus software programs. It's a false alarm and if you get that, you have to turn off the anti-virus program so you can install the mod. And usually it's recommended that you turn off the anti-virus program even before you start moding the game at all, as you can then turn it on again after you have finished the mod installations and scan your entire hard drive. *

2. The common Windows problems.The games require a few steps be taken so they work correctly, so they can be modified, and that the characters behave as they were originally intend to(patching).2.1. Don't use the default directory.Install the game to anywhere else than the default Program Files folder. "C:\Program Files\Black Isle\BGII - SoA\"This is, so far at least a problem on Windows XP SP3 with or without the 64-bit, Windows Vista and Windows 7.So don't install the game to the C: -drive's Program Files sub-folders(it's actual name changes according to your Operation System's language selection and the byte set, and between the different OS'es too), this is because the Operation Systems protect that folder from overwriting by mirroring the files, with is an extra security layer that actually puts the files into another directory, so your changes will not even take effect if you launch the game under a XP SP2 compatibility mode, under the Vista or Windows 7.In Windows 7, the changed files are actually written into your User Profile's Virtual Storage... from which they cannot be ran in XP SP2 compatibility mode.The Windows 7 x64 is said to be exception, as the "Program Files (x86)" is not mirrored... I have no personal knowledge on this. And I bet it has to do with the exact version of the program, as there's more than the basic today(Office, Professional, Ultimate). Update: Yep, my Ultimate versions folder is indeed mirrored. But anyway, in megamoding the Control Panel -> User Accounts and Family Safety -> User Accounts -> Turn User Account Control on or off -> Uncheck the box next to 'Use User Account Control (UAC) to help protect your computer', and push OK, and then restarting the computer, in annoyance...W7: Start -> Control Panel -> User Accounts and Family Safety -> User Accounts -> Change Your User Account Control settings... set to the bottom most option and done, and then restarting the computer, in annoyance...2.2.2 Disabling the Program Compatibility Assistant on Windows 7.To increase this annoyance, the clever idiots at the MacroHard have invented this assistant that always asks: 'Did this x program install successfully?' on 32bit system, and in 64bit system it can and will stop you from overwriting useful files, like the BGMain.exe when you upgrade the SoA to ToB. To remove it push the Start -> type to the console: gpedit.msc and start it, then User Configuration -> Administrative Templates -> Windows Components -> Application CompatibilityDouble click the option "Turn off Program Compatibility Assistant", and inside its configuration mark the "Enabled" -> Apply -> OK. Restart the computer.The gpedit.msc file can also be found usually manually from C:\Windows\System32 or C:\Windows\System64 -folder, in most machines, but as said in the link some versions of the Window 7's don't have that, meaning that you are stuck with the original setup... whatever that is, so you don't have to disable it.2.3 Install the official game patches.As the Bioware.com was updated a sometime ago, the old games don't have an official site to download the patches from, but there was a net archives that had the content, it seems for a while that the wayback machine was updated and thus the previous links were no longer in action, but these new should work:Baldur's Gate; use the v1.1.4315, without the DirectX 8+ patch, cause they were betas from long ago!Baldur's Gate: Tales of the Sword Coast; the v(1.3.)5512 without the DirectX 8+ patch, and even though the link says not to patch the Original Saga version, the Original Saga version can be patched to gain the most compatible version of the game, so it's recommended.Baldur's Gate II: Shadows of Amn; the 23037.Baldur's Gate II: Throne of Bhaal; the v(2.5.)26498... DO NOT use the 26499!Other good patch links to non-Bioware links with patches to Infinity Engine games:Planescape: Torment; the v1.1 ...Icewind Dale; v1.06Icewind Dale Heart of Winter; Trials of the Luremaster, also known as the v1.42 patch.Icewind Dale II; v2.012.4 Make a quick icon from the BGMain.exe to the desktop.This is made because you want to make sure you actually start the right game files, as the Baldur.exe uses the Windows Registry, which might not be the current game files in the same game folder you wish to modify the game in. (8.)2.5. Start the games.The game's installation is finalized when you start a new game, you only need to only be able to save the game, and no, you won't be using the character you create as the save at this point will not have any of the modified content, so you can delete it if you want to... the reason why you need to start a new game is that you can see if there's something wrong with the game at this point, that it actually starts, that there's no graphical errors etc.2.5.1 Get rid of the graphical errors before you modify the game.The

Extract that directly into your game folder; overwrite if and when asked to, and then Edit the "change-log.bat" with Notepad, change the "########.###" and perhaps the "*********.***" and remove the "::" in the last line in case you need to make change-log's from multiple files. There is a folder in the archive, it is important that you do extract it too, so the logs and files have a free space to be saved to.Then you just run the change-log.bat, it will use the WeiDU.exe that's included inside the archive... the process is fast and should only take a few seconds... or thousands of seconds if you make thousands change-log*.txt's, but then you are insane, just like the Imp is. The process will print the files into the folder the archive had inside it(by default it's called the "change-log" -folder), well, you can actually change that too, but then you have to rename it if you want to use it. Unfortunately this cannot extract the vanilla backups from the .bif files, so you'll be missing the .00000. file if the file is from the vanilla game, or if it's biffed by with the old style that deletes the backups. You also won't get a notice if the file is overwritten by you, edited by one of the Infinity Engine Tools besides WeiDU.exe or if it's overwritten some by some .bat file, or you manually do the same, as those leave no marks in the WeiDU.log . Which is a good reason to learn to have a clean install directory before installing any mods on it.The "BiG World Installpack v9.9.7z" includes a little better file than these, but not much, so you can use them too, and you start by editing the "change-log.bat" file, alike above.Or, if you have installed the BWP after the v7 but not v9.9, then you have the old version of the change-log.bat available, you can use it by editing the file with Notepad, insert the file name on the ####.### and save, when it's run, it will make you the change-log.txt which is a text file that opens again with Notepad... but it prints the files all over the place, so I suggest using either of the newer versions.These all also works with Vista and Windows 7, but you have to disable the User Account Control like always.6.1. What's the use of the --change-log after it's made ?It first of all prints out the change-log.txt, and it also extracts all the backup files it can into the "change-log" folder as .*****. where the * are the numbers of the backup files it is from, so you can take a look at them, or you can put the folder into an archive(.zip, .rar or .7z file) and post it in a forum, you usually have to be a member, for others to look at it, and you should post it on the forum the question was made, so the megamod maintainers and the people responsible for the mods maintainers can take a peek and make the right connections on why a bug happened. And generally, it's a mark of good behavior, that you attach the whole folder after you archive it, to the forum you were asked to make the --change-log, so they don't have to ask you a thousand times... 6.2. The expected result...It can look like this: 2b1af7f3a8