Hello good people, I have been trying to find the INI file and i did find a few "usersettings" INI file but no Edit seems to work. This tool also says "one or more config files are missing"
I am using the Juggernaut Edition and i got it from GamePass on Pc. I would really appricate some help and thank you in advance for ur time :D
Pre TL;DR version. This editor doesn't work with the Juggernaut / Steam Edition of State of Decay 2. Instead gotohttps://www.pcgamingwiki.com/wiki/State_of_Decay_2 ALL the ini changes are found there.
The info below will cover you for this game & future ini config changes.
Re Missing INI Files If there is no config file, simply create the ini file "missing" by using notepad or similar txt (text) file editor app. (Notepad+, Notepad++, notepad 2 etc).
To do this, create a new text (txt) file, Type or copy paste the changes, such as found at pc gaming wiki, save the text file under the title of the desired "missing" ini file, eg Engine.ini - Of course it will save as Engine.txt so don't forget to change .txt to .ini and when prompted with "If you change a filename extension, the file might become unusable. Are you sure you want to change it?" Click YES.
For future reference, you may want to set a newly created or edited ini config file to "Read Only" in the Properties box. It depends if the game makes it's own changes (reverting back to an original state). This is unlikely in your case as the game hasn't created the config.
This editor is incompatible with the STEAM version of State of Decay 2 ie the Juggernaut Edition. Your best course of action is to google PC Gaming Wiki State of Decay 2 and follow the changes you wish to make from there, the info I wrote above will aid you in this. Basically this tool gives a UI to change the EXACT same ini edits found at pc gaming wiki. I'd recommend you keep a note of any changes you've made/added in a separate text file - that way any changes you find causing issues with your gamelooks or play can be easily reverted.
Also it is good practice to duplicate an original ini file & back it up : An easy way to do this is to "zip" (compress) the copy as a "backup", zipping the file saves renaming it and guarentees the game will not accidentally read it as the config file instead of the one you edited.
To keep things tidy, create a folder named "00-Changes" or 00-MyMods" or "((Changes))", "00-" or "((-" just makes sure the folder is at the top of the folder tree list so you can find it easly nothing more :) . Place all the back up ini's & any other info in the folder, its fine to keep this folder in the same folder as the actual config ini files (or create a folder dedicated to game changes elsewhere).
If kept in the games ini folder either make sure the file is not named after something the game may try to "use" eg engine.ini rename to "OLD engine config file.txt" - it won't break your game, just the game will likely not use the changes you made or ignore both changes/and original ini, & at worse the game will simply recreate a new config file
So ZIP the back up folder you created (of course deleting the unzipped version left over), and that way you have a 100% sure fire way to prevent the game clashing with your new & old info.
***
That's several ways to keep a list of the changes you have made but the "pro" way is to use # in front of "notes" at the beginning of every ini files instructions to distinguish between what the game should do & should ignore for your reference only.
I'm no script/programmer so do your own research here but in short :- You can use "#" in front of information in the actual config file as it acts (for want of a better term) as an "ignore this line" indicator thus you'd have several lines of info all starting with# it'd look something like:-
#Some info. Date changes made 1st of today year. #More info for my reference only. #The info below changes the FOV. #You get the idea info.
Now here's the Info that changes the fov. False=0. True=1. 1920x1080=0. 1440x1080=1. Why did the The Doors Fan Chicken Cross the Road? 0,1,2 = -.stuffing, 1.paxo, 2.to break on through to the other side. 2
but I prefer backing everything up and saving both the changed and original ini files for future reverting or additional changes as I'm not 100% knolwegable regarding this method of using "#" etc.
Steam version vs UWP/Dayton version - steam version stores ini S in a separate location - only upon running this tool the dayone folder is created everything in related is exactly where is should be for a steam game (app data/local/state of decay) just as it's explained in pc gaming wiki.
Having zero clue about coding I can see there are multiple ini files in the steam version hence this tool searches for 1 when using the browse feature, as it cant load this all encompasing ini file and has no ability to read multiple instances it simply can not be used with the STEAM version.
TBH it takes less time to edit the ini files as explainined at pc gaming wiki than it does trying to (and failing) to find a fix to use this (handy) tool.
Side note : shame there's so little mods for SOD2 - must be a bugger to mod / unreal engine lockdown + MS being awkward making a poo pie for modders. Why? cos modders will add all the things Undead Labs have been drip feeding Us consumers "psarts" of what will eventually be the game it SHOULD be (and will continue along this path with minor game iterations to milk the most of a good game - consider the fail of No Mans Sky? if they had chopped it up into NMS1 , NMS2 & NMS3 without maiing such bold promises at the start they could have easily sold the game 3 times in it's vsrious forms.)
I digress but when SOD first came out it was a shadow of what we were led to believe it would be, SOD 2 was little different despite being enjoyable it could/should (1 day will be) the 3d deep zombie survival management game - half promised at the start. If they can't sell us DLC that appears ripped out of the main game then they'll simply sell us a 1/4 of a game and add a number at the end each time they replace" i mean "make a nw version" ie the bits planned from day 1.
apparently the path of the ini files for the game is "..\AppData\Local\Packages\Microsoft.Dayton.99d0e2bb9b_8wekyb3d8bbwe\LocalState\StateOfDecay2\Saved\Config\UWP\" and not as the program thinks in "..\AppData\Local\Packages\Microsoft.Dayton_8wekyb3d8bbwe\LocalState\StateOfDecay2\Saved\Config\UWP\" ... this location does exist, but seem like was created by your programs first run to store the backup files.
Fragball, I'll have to investigate. There has to be a reason why you have a different folder than normal. The folder path that I detect should be the one used by all computers.
For now, at least, in settings you can change the INI path to the one that's valid for your system.
Edit: Did you buy the game or are you using the Xbox Game pass?
might be the windows version i use (win10 prof. 64bit build 1803) or might be because i use customized steam installation with non-standart game libraries (yes, more then one ^^) ofc, it might have nothing to do with any of it - can't really say since idk why this microsoft package is installed where it is in the first place (nor what it really is ^^) as far as i know the path "..\AppData\Local\Packages\.." is for windows "app" installations since the days of win 8, and not for "external" programs or even optional windows components... but who knows what SOD2 had installed with it together. imo, all those ini files should have been put in the usual place(s) in the user sub-folders. and yes, i did changed the path to the one i have - might be of interest for those who also have problems finding the ini files, to check the other "packet" sub -folders too - might even be more different foldernames, since this one sounds rather randomized to me... but then again, everyone should have a different place where the files are...
same. I can only find one file that looks like a config file. And its encypted. Im thinking they changed how the game works cause I have NO ini files in any of the suggested folders yet the game works fine and Im clearly saving settings somwhere...... kinda sucks.
Is this the currently confirmed issue? I too just opened the ini editor to receive (without matching letter for letter) the same/similar error as above* despite having played for numerous hours with multiple open/close/save instances yet game ini editor reported *no ini file/i've beeen warned.
Is there a fix we can manually apply ourselves (for now?)
Any chance to make it work with Steam Juggernaut version? Tried but nothing. Even if i change browse folder to steam's appdata/local/stateofdecay2/blablabla, nothing works.
Read this, esp the part on scalability. https://framedsc.github.io/GeneralGuides/ue4guide.htm Due to the nature of the data-structure, there is no guarantee it works tho.
Alright I'm a tad bit confused. As I'm looking for something that can help me import assets into the game. As I'm trying to import a new model so those who want to have their characters wear and use helmets will and allowing one person to put a outfit and a character's facial model together instead of them being forced to settle with a Soldier with an Ugly face. Will this help me achieve this? If not could you or someone kindly point in the right direction with some steps on achieving this.
Give Feedback
44 comments
I have been trying to find the INI file and i did find a few "usersettings" INI file but no Edit seems to work.
This tool also says "one or more config files are missing"
I am using the Juggernaut Edition and i got it from GamePass on Pc. I would really appricate some help and thank you in advance for ur time :D
This editor doesn't work with the Juggernaut / Steam Edition of State of Decay 2.
Instead goto https://www.pcgamingwiki.com/wiki/State_of_Decay_2 ALL the ini changes are found there.
The info below will cover you for this game & future ini config changes.
Re Missing INI Files
If there is no config file, simply create the ini file "missing" by using notepad or similar txt (text) file editor app. (Notepad+, Notepad++, notepad 2 etc).
To do this, create a new text (txt) file, Type or copy paste the changes, such as found at pc gaming wiki, save the text file under the title of the desired "missing" ini file, eg Engine.ini - Of course it will save as Engine.txt so don't forget to change .txt to .ini and when prompted with "If you change a filename extension, the file might become unusable. Are you sure you want to change it?" Click YES.
For future reference, you may want to set a newly created or edited ini config file to "Read Only" in the Properties box. It depends if the game makes it's own changes (reverting back to an original state). This is unlikely in your case as the game hasn't created the config.
This editor is incompatible with the STEAM version of State of Decay 2 ie the Juggernaut Edition. Your best course of action is to google PC Gaming Wiki State of Decay 2 and follow the changes you wish to make from there, the info I wrote above will aid you in this.
Basically this tool gives a UI to change the EXACT same ini edits found at pc gaming wiki. I'd recommend you keep a note of any changes you've made/added in a separate text file - that way any changes you find causing issues with your gamelooks or play can be easily reverted.
Also it is good practice to duplicate an original ini file & back it up : An easy way to do this is to "zip" (compress) the copy as a "backup", zipping the file saves renaming it and guarentees the game will not accidentally read it as the config file instead of the one you edited.
To keep things tidy, create a folder named "00-Changes" or 00-MyMods" or "((Changes))",
"00-" or "((-" just makes sure the folder is at the top of the folder tree list so you can find it easly nothing more :) .
Place all the back up ini's & any other info in the folder, its fine to keep this folder in the same folder as the actual config ini files (or create a folder dedicated to game changes elsewhere).
If kept in the games ini folder either make sure the file is not named after something the game may try to "use" eg engine.ini rename to "OLD engine config file.txt" - it won't break your game, just the game will likely not use the changes you made or ignore both changes/and original ini, & at worse the game will simply recreate a new config file
So ZIP the back up folder you created (of course deleting the unzipped version left over), and that way you have a 100% sure fire way to prevent the game clashing with your new & old info.
***
That's several ways to keep a list of the changes you have made but the "pro" way is to use # in front of "notes" at the beginning of every ini files instructions to distinguish between what the game should do & should ignore for your reference only.
I'm no script/programmer so do your own research here but in short :-
You can use "#" in front of information in the actual config file as it acts (for want of a better term) as an "ignore this line" indicator
thus you'd have several lines of info all starting with# it'd look something like:-
#Some info. Date changes made 1st of today year.
#More info for my reference only.
#The info below changes the FOV.
#You get the idea info.
Now here's the Info that changes the fov.
False=0.
True=1.
1920x1080=0.
1440x1080=1.
Why did the The Doors Fan Chicken Cross the Road?
0,1,2 = -.stuffing, 1.paxo, 2.to break on through to the other side.
2
but I prefer backing everything up and saving both the changed and original ini files for future reverting or additional changes as I'm not 100% knolwegable regarding this method of using "#" etc.
Your choice.
Having zero clue about coding I can see there are multiple ini files in the steam version hence this tool searches for 1 when using the browse feature, as it cant load this all encompasing ini file and has no ability to read multiple instances it simply can not be used with the STEAM version.
TBH it takes less time to edit the ini files as explainined at pc gaming wiki than it does trying to (and failing) to find a fix to use this (handy) tool.
Side note : shame there's so little mods for SOD2 - must be a bugger to mod / unreal engine lockdown + MS being awkward making a poo pie for modders.
Why? cos modders will add all the things Undead Labs have been drip feeding Us consumers "psarts" of what will eventually be the game it SHOULD be (and will continue along this path with minor game iterations to milk the most of a good game - consider the fail of No Mans Sky? if they had chopped it up into NMS1 , NMS2 & NMS3 without maiing such bold promises at the start they could have easily sold the game 3 times in it's vsrious forms.)
I digress but when SOD first came out it was a shadow of what we were led to believe it would be, SOD 2 was little different despite being enjoyable it could/should (1 day will be) the 3d deep zombie survival management game - half promised at the start.
If they can't sell us DLC that appears ripped out of the main game then they'll simply sell us a 1/4 of a game and add a number at the end each time they replace" i mean "make a nw version" ie the bits planned from day 1.
"..\AppData\Local\Packages\Microsoft.Dayton.99d0e2bb9b_8wekyb3d8bbwe\LocalState\StateOfDecay2\Saved\Config\UWP\"
and not as the program thinks in
"..\AppData\Local\Packages\Microsoft.Dayton_8wekyb3d8bbwe\LocalState\StateOfDecay2\Saved\Config\UWP\"
... this location does exist, but seem like was created by your programs first run to store the backup files.
For now, at least, in settings you can change the INI path to the one that's valid for your system.
Edit: Did you buy the game or are you using the Xbox Game pass?
ofc, it might have nothing to do with any of it - can't really say since idk why this microsoft package is installed where it is in the first place (nor what it really is ^^)
as far as i know the path "..\AppData\Local\Packages\.." is for windows "app" installations since the days of win 8, and not for "external" programs or even optional windows components... but who knows what SOD2 had installed with it together. imo, all those ini files should have been put in the usual place(s) in the user sub-folders.
and yes, i did changed the path to the one i have - might be of interest for those who also have problems finding the ini files, to check the other "packet" sub -folders too - might even be more different foldernames, since this one sounds rather randomized to me... but then again, everyone should have a different place where the files are...
Edit: Oh, it's not compatible with Juggernaut Edition I think
I too just opened the ini editor to receive (without matching letter for letter) the same/similar error as above* despite having played for numerous hours with multiple open/close/save instances yet game ini editor reported *no ini file/i've beeen warned.
Is there a fix we can manually apply ourselves (for now?)
cheers for your hardwork.
Go to your main C Drive, Users, your pc profile name, AppData (if you dont see Appdata google how to make it appear)
Then Local, and look for StateofDecay2 it was all one word for me.
Then its Saved, Config, WindowsNoEditor folder, and then you find all the ini files that need to be edited.
Use
https://www.reddit.com/r/StateOfDecay/comments/8ke2w8/state_of_decay_2_ultimate_ini_tweak_guide_fov/
For Reference data on how to edit it manually. Finally just got rid of the horrid Noise effect
https://framedsc.github.io/GeneralGuides/ue4guide.htm
Due to the nature of the data-structure, there is no guarantee it works tho.