I downloaded the requirement .Net Framework 4.0 and tried to run it with State of Decay YOSE but it says “Same of higher version of .NET Framework 4 has already been installed on this computer.” And thus the installation doesn’t occur.
So I downloaded the SoD Tools anyway and it appears to work. It’s the 2.1.3 version as of now which is the latest version.
The problem is it says “Error: wrong command-line argument (C:\users\steamuser\AppData\Local\Temp\extractYOSE.txt)”
I tried to direct the program to the game folder but it’s blank and doesn’t show the .pak files.
You need to go into the apps settings, and uncheck YOSE settings if you are using it for non YOSE editions, and check YOSE settings if you are using it for YOSE editions
You know, quickbms has been released under GPL, so as you're using it as part of your executable (embedded resource), you should also provide the source code for your app. But for all interested on how to actually get the PAK files extracted without the SOD: 1. get the free open source quickbms from Luigi Auriemma: http://aluigi.altervista.org/quickbms.htm 2. get the script to extract the PAK files for quickbms from: https://forums.nexusmods.com/index.php?/topic/2809544-year-one-pak-files/#entry24838039 3. Run the quickbms as follows: quickbms.exe <location of the script from pt.2> <location of the pak file> <location where to extract the files>
Example (from the powershell in Windows 10): If I put the quickbms.exe in the same folder as the pak files, and save the script from point 2 above to sod.bms and place it in the same folder as the pak files, the command line will be:
.\quickbms.exe .\sod.bms .\gamedata.pak .\
This will extract all the data into the same folder where the pak file is located. It will also recreate the whole folder structure.
Thank you for the useful instructions for an alternative extraction tool.
I unpacked the "State of Decay YOSE\Engine\config.pak" file, modified some of the included .cfg files, and now want to use them.
Now how do I repack into a PAK file using my modified .cfg files? I've tried and failed using both SOD_Tools' "Reimport" feature and quickbms' "reimport.bat".
Or do I not need to repack into a PAK file? Can I place the modified loose .cfg files somewhere in the State of Decay YOSE folder and it will prioritize them over the original PAK file?
Edit: I believe I found the solution to my question at the link below. According to the link I can just delete the original PAK file that I extracted and copy in the unpacked (loose) files. Thank you internet. https://forums.nexusmods.com/index.php?/topic/6235681-how-to-make-modding-sod-yose-much-easier/
Because I use one open source file, I should release this as open source? Uhhhhh I'm not doing that, Have you not seen the influx of open source tools being repacked with viruses...
At this time editing pre-existing BMD files created by other mod authors is impossible. It's just far too time consuming to parse all the strings that are added to the xml file when its turned into a bmd. I've been working on an algorithm to attempt to make a cleaner way to extract the garbage text. itll be some time. It's easiest to ask the author for their XML source to edit then you can use my tool to compile to BMD
BUT To be honest i dont think ill release a bmd editor. it would enable people to decompile mod authors bmd files then repost as their own. In a sense, BMD files are a protection for mod authors
2017Nexus2017 The game uses XML files AND BMD files. And if you find a mod you'd like to edit, contact the creator and ask them to give you the source.
If it doesn't work, with the error: "Error: wrong command-line argument (C:\Users\[your Windows account's first name])",
try logging into a different Windows user that only has one single word as the name (and verify this is also true in the C:\Users\ folder) and then running this tool.
Sorry for necroposting. Im having problems with the extraction tool, it was working fine for a few days but now it refuses to export as BMD, tool claims it was done sucessfully but the BDM file is nowhere to be found.
I don't know if you were able to figure this out or not, and Sorry for the late reply on this, but I just started modding on SoD today. I had the same issue because I had my xml file I was trying to convert in "My Documents" folder. I read an earlier post a few pages back were somebody said that you needed to have your xml file in a folder in the C: drive. I created a folder in the C: drive and when I loaded the xml from that folder and "exported to bmd" it worked. I found the new bmd file in the same folder that the xml file was in. I hope this helps if you were still trying to figure this out!
A mí me pasa exactamente lo mismo... Intenté hacer lo que dijiste, pero todavía no puedo encontrar el nuevo archivo bmd... ¿cómo debería llamarse la carpeta en la unidad c?
For one, the XML file must have proper formatting in order for it to be built. Try saving an xml with just text in it and exporting to BMD. It just wont work as it lacks the proper formatting. Try the same on a properly formatted mod XML and it will export perfectly :) And two, I have fixed the issue with using directories with spaces in the path, This will now work as intended!
Hello I'm sorry to be a bother. I'm trying to modify files in Game\libs\class3\rts, but I just can't find it. The closest I can get is Game\levels\class3. Is something wrong?
99 comments
I downloaded the requirement .Net Framework 4.0 and tried to run it with State of Decay YOSE but it says “Same of higher version of .NET Framework 4 has already been installed on this computer.” And thus the installation doesn’t occur.
So I downloaded the SoD Tools anyway and it appears to work. It’s the 2.1.3 version as of now which is the latest version.
The problem is it says “Error: wrong command-line argument (C:\users\steamuser\AppData\Local\Temp\extractYOSE.txt)”
I tried to direct the program to the game folder but it’s blank and doesn’t show the .pak files.
Help please?
1. get the free open source quickbms from Luigi Auriemma: http://aluigi.altervista.org/quickbms.htm
2. get the script to extract the PAK files for quickbms from: https://forums.nexusmods.com/index.php?/topic/2809544-year-one-pak-files/#entry24838039
3. Run the quickbms as follows:
quickbms.exe <location of the script from pt.2> <location of the pak file> <location where to extract the files>
Example (from the powershell in Windows 10):
If I put the quickbms.exe in the same folder as the pak files, and save the script from point 2 above to sod.bms and place it in the same folder as the pak files, the command line will be:
.\quickbms.exe .\sod.bms .\gamedata.pak .\
This will extract all the data into the same folder where the pak file is located. It will also recreate the whole folder structure.
I unpacked the "State of Decay YOSE\Engine\config.pak" file, modified some of the included .cfg files, and now want to use them.
Now how do I repack into a PAK file using my modified .cfg files?
I've tried and failed using both SOD_Tools' "Reimport" feature and quickbms' "reimport.bat".
Or do I not need to repack into a PAK file? Can I place the modified loose .cfg files somewhere in the State of Decay YOSE folder and it will prioritize them over the original PAK file?
Edit: I believe I found the solution to my question at the link below. According to the link I can just delete the original PAK file that I extracted and copy in the unpacked (loose) files. Thank you internet.
https://forums.nexusmods.com/index.php?/topic/6235681-how-to-make-modding-sod-yose-much-easier/
Also is the mod jsut the bmp files? So the game doesnt use the XML files?
And if you find a mod you'd like to edit, contact the creator and ask them to give you the source.
If it doesn't work, with the error: "Error: wrong command-line argument (C:\Users\[your Windows account's first name])",
try logging into a different Windows user that only has one single word as the name (and verify this is also true in the C:\Users\ folder) and then running this tool.
And two, I have fixed the issue with using directories with spaces in the path, This will now work as intended!