#Banished achievements with mods mod#
#Banished achievements with mods mods#

#Banished achievements with mods mods#

The original game in question, the dev has switched back and forth since that time of mods disabling achievements to where currently today, mods DO NOT disable achievements in his games.

#Banished achievements with mods mod#

I was a mod at AStats during that time, and said well you can't just target a single user for a rule, you have to apply it evenly across every game, so that'll be my fault for that lol. So that behavior was labeled as 'bypassing'. For example in Banished, you can mod give yourself everything save, turn of the mods reload the save, you keep everything, basically undetectable. then it got expanded to cover every single game where any behavior could be labeled as bypassing. It was originally about binding of Isaac i believe afterbirth because users were able to bypass the mod disabling by just pasting the mod in the base game folder instead of the mod folder, and it would work. It originally had nothing to do with mods /enable/disable/bypass Skyrim being a game that was caught in that crossfire. If I can make an assumption, they got caught on its impossible implementation at catching users, so they expanded it to all games, instead of originally the 1 game they initially applied it to. The history of the rule seemed to be intended just to trap a specific user. So far only a single user in that time has been banned from astats, and none from anywhere else to my knowledge. Obviously thats changed since our drop of technical support and their denial of the rules from 2 years ago to now.

We included it as a compromise to better adapt users to astats and other sites and I guess make it more likely for astats to adopt the unified rules. The rule was the last rule mytharox made at astats before disappearing. I can agree, I also disagree, but i think that there is time and language that needs to be adapted before that can come to fruition. It's unfortunate that there's games where this allows mods to straight-up unlock achievements for you, but if workshop mods are accepted as the developer explicitly allowing you to do something in-game, I don't see how that's any different to games like Redactem letting you press a button on the menu to do the same thing. If our position is 'using a workshop mod to get a map where grinding this achievement is super easy is okay, it doesn't matter that the dev didn't want you to do that', then surely 'using a workshop mod to enable achievements is okay, it doesn't matter that the dev didn't want you to do that' is just as applicable. I have always felt that it's a bit weird to allow workshop (or other officially-hosted) mods, but explicitly disallow specific mods that fit that category because they do something we don't want. Which is why I propose we treat it differently. I feel that this rule is fairly inconsistent, frequently ignored, and is generally unenforceable except for in cases where folks are ALSO breaking rules like OK-17.ДЇallout 4 and other games originally released with mod-blocking achievement code, but skyrim technically didn't. This means anyone buying the game currently must, effectively, play a game that has different rules than the original version.ДЄdditionally, 'Skyrim Script Extender' is allowed for official mods, but mods that ship in the ingame mod store for skyrim SE cannot be used by achievement hunters. My argument is that the rules allow modding the original version of Skyrim, which has been unlisted on the store in lieu of the remake. So, I'd like to argue for an exception to the 'No achievement enablers', specifically for Skyrim SE.