Good.

They removed failure risk completly.

They finally set it back to 0% minimum?

this mod is one of the must have mod in my list, for a logn time, though it wont needed for 2.1, still very appricate for make our game feel much better :)

It's still working,thx!

It should still work, it's a pretty simple mod. I don't play the game anymore, so I won't know if it stops working. Let me know if it does stop working though.

Any plan for 2.0?

@Nesano: The devs are aware of the bug regarding the screens not working like they should. The list includes anomalies, colonization, and resettlement so far that I'm aware of. The devs themselves have recommended the click&drag workaround.

Good luck guy,keep up the good work :D

I just tested it and it works. The anomaly information screen is blank until I drag the window, but it happens with or without my mod, so mine's not what's doing it.

Empty files?

It shouldn't need updating. Does it not work anymore?

Update please,thanks :D

We all were.

Holy shit, thank you, I was so triggered when I came back to Stellaris and I saw this shit.

That made no difference.

@Fire Fart
It is supported by the most recent version, so just ignore that.

That's not how mods work when creating and uploading. You don't make changes from the steamapps/workshop directory. I'm sure you could, but there is no good reason to do so, seeing as it adds an extra step that the launcher does automatically for you when you upload to workshop. The only situation I can see it being required is in a case of where the original creator's storage went bad, so they have to re-acquire their own content. And you would definitely never 'create' content from the workshop directory, as it needs to already have a workshop ID.

@Fire Fart
When you create a mod, you gotta have a folder and .modfile, and the directory is pretty much like

documents/paradox interactive/stellaris/mod/insertname
documents/paradox interactive/stellaris/mod/insertname.mod

And when you UPLOAD it, it creates a copy, moves the .mod file into the folder, changes the name of the .mod file, compresses the folder, and changes path to archive. Additionally, it adds a workshop ID to both the original .mod file and the packaged version that was uploaded.

NGameplay = { ANOMALY_RISK_MIN = 0 }

^ That's what it should be, Nesano.

A question, if you hover the mouse over this mod on the mods list of the launcher, does it say "this mod is version supported_version and not 1.8.2" or "this mod is version 1.8.0 and not 1.8.2"? Did you also modify descriptor.mod in the workshop file in steam\steamapps\workshop\28something? Did you use notepad++ (windows) or atom (iOS) to change the version and change the ANOMALY_RISK_MIN line? a normal txt editor will just mess up with the content, just like any unzipper to unzip the mod files in the workshop folder besides the windows explorer or the unarchiver for iOS

I named the file "00_anomaly_minimum_failure_risk_fix_defines.txt" and it won't recognize it.

The contents of the file is:

NGameplay = {
ANOMALY_RISK_MIN = 0 # Risk is never less than this
}

I don't see what else it would need.

Basically 000000_anomaly_risk_defines.txt would work

So, _defines.txt

anything before that name, knock yourself out, but the higher in the 0 to 9 A to Z sorting, the better.

The end of the filename has to be defines. Examples from two mods, hyperdriveonly and newshipclasses
AAAA_hyperdrivesonly_defines.txt
00_NSC_defines.txt

I changed it to 1.8.*. I don't much of anything about making mods, I only made this one because Paradox wants us to suffer and I say no more.

Yeah, overwriting the defines file with a file that only contains ANOMALY_RISK_MIN wouldn't be good.

It doesn't work though, does the unique name need to contain the string "defines" or something?

Also, did you make sure you actually changed the supported version in the .mod file?

I feel bad for asking that, but, hey, troubleshooting 101

Yeah, just make sure to rename the define, otherwise it won't work, and name it something unique.

I did that, but it didn't update the version number.

Come to think of it, that would make sense. All it needs is that constant. If I just have a txt file with that constant alone, it won't overwrite anything else. I'll update the mod using that method.

PS; I recommend renaming your defines file to something like 0000_anomaly_risk_defines or some other name like that, that way you don't overwrite the actual 00_defines file, and you still make the define change. New ship classes does this too.

I'm pretty sure there is also some kind of security to that, too, so you can't alter other people's mods, but, eh, who knows.

Use fetch info before you upload mod. It'll check if the mod is already on workshop (checks to see if the ID in the .mod file is the same as any workshop mods). If so, it updates the mod on workshop.

Welp, I've updated it with the new 00_defines file, but it still thinks it's on 1.8.0 for some reason. It'll work.

Is there a way to do that without creating an entirely new mod?

indeed the update has changed few lines and adde some, you need to reapply the changes you did in the first place to 00_defines and then upload it here on this workshop page.

I actually don't know if the 1.8.2 update touches the 00_defines file... in that case the anomaly minimum percentage must be reapplied and the mod updated to this page. As for bugs or issues i haven't experienced any as i haven't tried it yet :P doing it now.

Oh, I didn't realize it even needed updating. Would I just need to reupload it or something?

Thanks man, it was really needed! No more quicksaves. Anyway, can you update it to 1.8.2?