51 replies to this topic

[DragonBlood87]

I've been having issues with this utility. I can get INT patches (like the rank name changes) to work without a problem, but INI changes seem to work inconsistently.

Whenever I check active file, I can see that it has all the changes present, but when I start a new game, most of the changes don't seem to have taken place, even after using the "Apply active file to the game" option and choosing to use the current EXE.

What's really puzzling is that some changes (such as enemy health) *do* seem to work, while others (like changing facility costs, or equipment stats) don't work... even though they show up in the active file and no errors are shown even in debug level 2.

I ended up downloading the ResourceHacker utility to double-check, and it was indeed not applying most of the changes that show up in the active file.

The only other mod I was using was ToolBoks, which I used a single time prior to using Custom Mod Builder; I have not used it since, and I have not done any backup restore.

[dubiousintent]

I've been having issues with this utility. I can get INT patches (like the rank name changes) to work without a problem, but INI changes seem to work inconsistently.
...
The only other mod I was using was ToolBoks, which I used a single time prior to using Custom Mod Builder; I have not used it since, and I have not done any backup restore.

1. Be sure to apply the Mod List changes to the Active file before you Apply the Active File (2 steps in the same menu), every time you change the Mod List.
2. ToolBoks makes changes to the UPK files, so it (and any other UPK patches) should be applied AFTER CMB because it runs XSHAPE to patch the EXE's SHA hash to what the Steam loader is expecting. CMB only makes INI & INT changes, but they are separate steps in the process.

-Dubious-

[FMod]

Whenever I check active file, I can see that it has all the changes present, but when I start a new game, most of the changes don't seem to have taken place, even after using the "Apply active file to the game" option and choosing to use the current EXE.

By checking the active file, you mean the internal check or opening it with an editor to view?
If it's the latter... Try posting mod builder.ini here, I'll see if there may be something wrong there.

What's really puzzling is that some changes (such as enemy health) *do* seem to work, while others (like changing facility costs, or equipment stats) don't work... even though they show up in the active file and no errors are shown even in debug level 2.

I ended up downloading the ResourceHacker utility to double-check, and it was indeed not applying most of the changes that show up in the active file.

That's a little strange. If it's in the Active File, it should apply either everything or nothing.
This is possible if you're being stuck with an older version of the exe where some of the changes have been applied.
Have you tried removing exe backups manually? It's not meant to be necessary anymore, but may be needed.

[Porkdish]

Why does the active file always set the USA funding to 500?

[FMod]

Must have been a mixup. I made a custom patch for a player that did exactly that and for some reason it got set as default.

Will fix ASAP.

[dubiousintent]

Woot!    With both CMB and ToolBoks updated, modlet patching is back in business for the rest of us!

 

-Dubious-

[Corrales85]

======================================== UPDATE 2: No dice. The program has ceased to work for some reason, and the side effects I mentioned before are back :/ ======================================== ======================================== UPDATED: So, I've been doodling around, and before trying to uninstall all my Steam games, the client and relocating the whole thing to a different folder than Program Files (x86), which I heard was giving some people trouble with Win7's data protection thingies (never been an issue for me, but I don't know) I decided to play around and install some previous versions. 0.99 is the winner! It's installed my 99 aim mod no problem, without any error messages. So you might want to have a look at it, since it may not be a local problem. =========================================== Hey there, new guy here I've been trying to tweak XCOM for some time now, but have been bashing my head against some hurdles. First I tried to mod the internal resources from the .INI by using Resource Hacker, which actually let me change the values I wanted, but also had some unpleasant side effects like random crashes (often upon starting a mission) and the game's process never actually shutting down after quitting, which prevented me from restarting the game without actually restarting the computer itself. So it isn't without some hope that I've tried to achieve my goal with CMB, but sadly to no avail. My problem goes as follows: - Installed XCOM. Latest version (changelist 356266) with both DLCs, clean install. Ran it twice, saved and loaded, etc. - Unpacked CMB 1.0 to my main XCOM Steam folder, launch it with the script, set directories properly. - FIRST SIGN OF TROUBLE: Even though I don't plan to use them, I try to enable INT patches from the options menu. The command console shuts down immediately, so decide to first dust off my MS-DOS, run a cmd and launch the tool from there. Upon attempting the same, the following message appears: =============================== "No se esperaba \Steam\steamapps\common\XCom-Enemy-Unknown\XComgame\localization\int\unicode en este momento." =============================== Now I'm running a Spanish-language version of Windows, so that would translate (not sure if it's to the letter) to: =============================== "\Steam\steamapps\common\XCom-Enemy-Unknown\XComgame\localization\int\unicode was not expected at this moment." =============================== But well, since I don't plan on using INT patches, I don't mind it much right now. Next, I enable "auto-apply on quick install" (which I suppose is good for testing individual small tweaks) and "use EXE file backups". - So, (for testing purposes strictly ) I want to make the default aim score for rookie soldiers 99. So I head to "create mods", create a new working file called "Base aim 99" and edit it. I find the "ROOKIE_AIM=65" line and change the value to 99, and save and close the working file (everything right so far, save for my dirty cheating, right? ). - Then option 3, "clean the working file to yadda yadda". I just hit enter since I want it to bear the same name. Option 5 shows me the following .txt: =============================== ;patch,Description goes here ROOKIE_AIM=99 =============================== - So I return to the main menu and choose "Quick install mods", taking into account that I've already changed the option to apply them upon a quick install. Since "Base aim 99" already appears above as the active mod, I just select "Install active mod". - SECOND SIGN OF TROUBLE: =============================== Active file size 98310, patch size 44 compiling... Patch has 1 lines, starts with "ROOKIE_AIM=99" Compiling patch, line 001/001... patching... [total hits/matching patterns/non-matching patterns] [001/1/0] Active\Custom.txt 1 files checked, 1 changed. Report on file Active\Custom.txt Last updated: 08/05/2013 23:35, total size: 98310 bytes Contains 735 lines, of them 694 significant, 41 comments Lines different from master Masters\Default.txt: 1 lines, of them significant - 1 lines "builder.patcher.exe" no se reconoce como un comando interno o externo, programa o archivo por lotes ejecutable. Completed (if there were no error messages) If the game does not work, use Manage Backups to revert. Operation complete. Press any key to continue. =============================== "If" there were no error messages? But there is! =============================== "builder.patcher.exe" no se reconoce como un comando interno o externo, programa o archivo por lotes ejecutable. =============================== That one I can easily translate off the top o' my head, it's this one: =============================== "builder.patcher.exe" is not recognized as an internal or external command, operable program or batch file. =============================== - So I press enter anyway, and launch the game with Steam in offline mode. New game, normal mode, no tutorial, in South America. And sure enough, the aim scores are 65 as usual. - At the very least I can quit and the process stops running So, is an angry god punishing me for being a cheating bastard? That doesn't hold up, as I've also tried lowering the aim value, and also giving the soldiers reduced sight radiuses (radia, radii?). None of it works. My guess is that the second point of trouble is the key here, but I'd also like to know what's up with the INT patching option. I mean, Unicode? What can be wrong with that? :s I'd really appreciate it if anyone could help me, as: 1. I feel really dumb asking for what would essentially amount to a step-by-step instruction list 2. I really like the tool itself and I can't help thinking I'm to blame because I'm dumb and ugly 3. I love tweaking numbers and playing around with game rules :3 Thank you, everyone

Edited by Corrales85, 09 May 2013 - 08:30 AM.

[FMod]

0.99 is the winner! It's installed my 99 aim mod no problem, without any error messages.

It's a bit strange. I'll take a look into the differences.
My guess is it's not a problem, but that 0.99 had taken some shortcuts where 1.0 fixed them.

Upon attempting the same, the following message appears:==============================="No se esperaba \Steam\steamapps\common\XCom-Enemy-Unknown\XComgame\localization\int\unicode en este momento."===============================Now I'm running a Spanish-language version of Windows...

Here is a likely cause of the problem.
Is your XCOM version the International English one? If no, it doesn't have .int files, so they can't be modded.

It's possible that the path wasn't stored correctly due to localization. What's your full path to the Steam folder?

I want to make the default aim score for rookie soldiers 99. ....
;patch,Description goes here
ROOKIE_AIM=99

That is correct, just how it should look.

Contains 735 lines, of them 694 significant, 41 comments Lines different from master Masters\Default.txt: 1 lines, of them significant - 1 lines

"builder.patcher.exe" no se reconoce como un comando interno o externo,programa o archivo por lotes ejecutable. Completed (if there were no error messages)

The new file to patch was created correctly, all how it should be.

But this is the error message (no translation needed, they are easy to recognize).
It couldn't find builder.patcher.exe - a file that is supplied and automatically copied to the game's folder. This means the path to the XCOM game wasn't set correctly. It's auto-detected in the standard English version of Windows, but I think the auto detection glitched with yours.

To fix this, you would need to go to Options and set path to the game manually.

My guess is that the second point of trouble is the key here, but I'd also like to know what's up with the INT patching option. I mean, Unicode? What can be wrong with that?

The INT patching option is for making changes to the text in the international game version, which is what INT stays for. It has some complications with UTF8-UTF16 conversion in order to store changes in plaintext.

[redrat9595]

Hey there. I'm getting the same issue as Corrales85, and I'm on the English version as well. How do I get the international version? I didn't pirate the game or anything (in fact, I got the special edition hard copy). I tried changing the language through Steam to German and back, but no dice. I have an English copy of Win 7 (x64) as well as an English copy of the game. Full path is as follows.

C:\Program Files (x86)\Steam\steamapps\common\XCom-Enemy-Unknown

In "C:\Program Files (x86)\Steam\steamapps\common\XCom-Enemy-Unknown\XComGame\Localization\INT", I have a plethora of .int files. Is there anything I can do?

-Redrat

[FMod]

Unfortunately I couldn't reproduce INT related problems on my system, so wasn't able to find the issue.

 

Anyway, an Enemy Within compatible version is early in the works. I just got EW and with the holidays and all it anything usable is likely to have to wait till next year, but it's close enough.