Unified Achievement Hunting Rules
Detailed Rules & Regulations Guidebook for Achievement Hunting
Mission Statement & Philosophy
Users are required to earn their achievements fairly and legitimately.
In general, a player must unlock achievements:
inside of a game by in-game actions;
by their own control;
without outside-modifying game files or game code;
without using another player’s save file, and;
without using outside cheat programs.
These rules are designed to keep players honest in their gameplay and honest towards each other in competition. It is important to understand that “achievement hunting rules” are not the rules for how to have fun playing a game or how to play a game as it was intended. Achievement Hunting is a community very much like speedrunning or high-score attack where we are playing our games in a non-standard, meta-competitive way. Some rules may seem contradictory because there are certain methods that are not considered “cheating” here even though they are unorthodox in normal play - those rules will be explained below, but it is because they still meet the “physical, mechanical, or digital” conditions needed to trigger those achievements in-game. These rules have been voted on, heavily discussed, and adjusted over the years by experienced achievement hunters since achievements were first released on Steam in 2007 🏆.
These Rules Officially Followed By:
Table of Contents
- ❌ Not Allowed - General Rules ❌
- ✅ Allowed - General Rules ✅
- 🎮 Game-By-Game Rules / Edge Cases 🎮
- 😓 Penalties for Cheating 😓
- 👮 How to Clean & Appeal Cheating 👮
- 📋 Feedback 📋
- ✏️ Changelog ✏️
❌ Not Allowed - General Rules Index ❌
- NA-1: Do not EVER use programs that circumvent game code to instantly unlock/relock achievements, such as Steam Achievement Manager (SAM).
- NA-2: Do not use save files that are not your own.
- NA-3: Do not modify game code.
- NA-4: Do not edit registry values for games.
- NA-5: Do not use outside game programs known as “trainers” or the Cheat Engine program.
- NA-6: Do not use unofficial mods that alter gameplay.
- NA-7: Do not use “workaround achievement-enabling” mods or “Achievement Unlocker” mods.
- NA-8: Do not use TAS (tool-assisted speedrunning), Bots, or Complex Scripting to gain achievements.
- NA-9: Do not alter the system clock in order to unlock achievements that require a passage of time.
- NA-10: Do not use console commands or debug menu options which allow you to speed up the passage of time.
- NA-11: Do not use any “depot method” to access “easier” versions of games.
- NA-12: Do not use console commands which directly and instantly unlock achievements.
- NA-13: Do not allow other users to access your account and earn achievements for you.
- NA-14: Do not be abusive to developers.
- NA-15: Do not create or share cheating methods.
✅ Allowed - General Rules Index ✅
- OK-1: Console commands that do not directly/instantly unlock achievements are allowed.
- OK-2: In-game cheat codes/modes and in-game debug tools are allowed.
- OK-3: Making use of in-game glitches, in-game exploits, and “cheesy” tactics are allowed.
- OK-4: “Save-scumming” and copying/transferring your own save files are allowed.
- OK-5: Using online guides/walkthroughs is allowed.
- OK-6: “Clickers / Autoclickers / Macros” are allowed.
- OK-7: Getting “carried” or “twinked” in coop games is allowed.
- OK-8: “Farming” and “boosting” achievements is allowed.
- OK-9: Changing your OS system clock to get Date-Specific achievements is allowed.
- OK-10: Deleting Registry Values is allowed.
- OK-11: Use of in-game buttons and button combinations that developers add into the game to unlock achievements is allowed.
- OK-12: Using in-game/in-app DLC and microtransactions (“p2w” / “Pay-to-Win”) is allowed.
- OK-13: Creating or using custom maps for games that support custom maps is allowed.
- OK-14: Simplistic Scripting is allowed to facilitate gameplay but not fully replace/emulate gameplay.
- OK-15: The “Depot Method” is allowed for games that broke themselves with an update.
- OK-16: Most Steam Workshop Mods and Official Mods/Official Patches are allowed.
- OK-17: Fully Cosmetic Mods are allowed.
- OK-18: Modifying certain standard settings via .ini files is allowed.
- OK-19: Reading game files and game code is allowed.
❌ Not Allowed - General Rules ❌
Do not EVER use programs that circumvent game code to instantly unlock/relock achievements, such as Steam Achievement Manager (SAM).
Even if you “should have” unlocked the achievement. Even if the game is bugged. Even if the achievement is removed or broken entirely. This is extremely easy to detect because of the way it interacts with game stats in the API pull and is harshly punished. There is NO situation where using SAM-type programs to unlock/relock an achievement is allowed, except for appeals with moderator direction.
Examples: Using SAM to unlock the broken achievement in Hate Plus; using SAM to unlock DLC achievement in a game you previously 100%ed before DLC was added; using SAM to modify a game stat to be 499/500 and then getting the last one yourself; using an achievement locker/unlocker to relock achievements you do not want; etc.
Do not use save files that are not your own.
Even if your save got lost/corrupted or you need a save from earlier in the game because you missed something.
Examples: Downloading a clicker game save online; begging a friend to send you his save file because your house burned down and you lost all your PC files; etc.
Do not modify game code.
Do not use other people’s unofficial edits of game code, even if it seems to “fix” a game. If an achievement is broken, please notify the developers of the game and wait for an update patch. Simply assuming developer intent and altering game code to unlock achievements misleads developers with false statistics, and the trade of potentially malicious compiled objects such as .dll and .exe files is a large security risk. Please see Allowed Rule 18 and any relevant Game-by-Game Edge Cases for the only exceptions to this rule.
Examples: Opening up specific game files with a text/hex editor and changing values to what you want; editing properties such as “read-only” for game files; editing TF2 files and pointing it towards a YouTube video you do not own for the YouTube views achievements; swapping certain .dll files or other game files between similar games to attempt to “fix” broken games; editing the images of puzzle pieces in puzzle games to have a number so you see exactly where to put them; modifying an .ini file for a Unity game to change enemy health; etc.
Do not edit registry values for games.
Examples: Going into the registry folder for a game and updating a registry file that keeps track of how many kills you have to get closer to a “Kill 1000 enemies” type of achievement; etc.
Do not use outside game programs known as “trainers” or the Cheat Engine program which can boost your powers in games, unlock debug modes, speed the game up, modify game code, etc.
Examples: Using Cheat Engine for anything; downloading a Devil May Cry trainer to enable invincibility/infinite Devil Trigger; downloading and using cheat toolsets or trainers for GTA V; using unofficial mods that act as trainers or debug/cheat toolsets; Game Genie / Action Replay and other such similar cheat tools; etc.
Do not use unofficial mods that alter gameplay.
All Steam Workshop mods are allowed except for mods that instantly/directly unlock achievements or circumvent games that block achievements when they detect any mod use (Not Allowed Rule 7).
Examples: Installing unofficial debug-style mods similar to a trainer; Installing unofficial and gameplay-altering mods from sites such Nexus Mods or GameBanana or ModDB or random forums; installing a mod from NexusMods that increases your carry capacity or increases your XP gain or enables fast travel and other such gameplay-altering mods; etc.
Do not use “workaround achievement-enabling” mods for games that disable achievements when any mod or in-game cheat or in-game debug menu is being used.
Do not use “Achievement Unlocker” type mods that grant options such as a teleport power you can use to go to an achievement room with buttons you simply press for achievements or items you can use that unlock achievements directly/instantly, etc.
Examples: Fallout 4 and Cities: Skylines disable achievements when they detect any mod being used and it is not allowed to circumvent this with mods; installing Steam Workshop cheat mods for Skyrim, such as the “Achievement Unlocker” mod; do not use any mods that allow you to instantly/directly unlock achievements via command/button/power; etc.
Do not use TAS (tool-assisted speedrunning), Bots, or Complex Scripting to gain achievements.
These are all advanced scripting of a game far beyond simple tasks (sometimes even synced to clockspeed) to allow complex, unique, and/or non-monotonous/non-repetitive sections of a game to be played without human interaction. (See Allowed Rule 14 below for allowed simple scripts).
Examples: Using a bot for an MMO game to gather resources/level up for you; using a TAS to complete a difficult speedrun or no-death achievement; using a complex script with advanced functionality (such as PixelSearch/ImageSearch, OCR, AI/ML, etc.) and/or decision-making ability; using complex scripts that complete entire games or large portions of games with no human input but requiring many unique actions such as completing Portal 1’s gold challenge rooms; etc.
Do not alter the system clock in order to unlock achievements that require a passage of time.
See Allowed Rule 9 below for allowed date-change rules.
Examples: The Stanley Parable’s achievement to not play for five years; Garry’s Mod/Universe Sandbox achievements to play for one year; Tabletop Simulator’s 1000 hours achievement; Chivalry: Medieval Warfare’s 80 hours achievement; etc.
Do not use console commands or debug menu options which allow you to speed up the passage of time in order to more quickly achieve passage of time-based achievements such as “play for x hours”.
Examples: aoc_slomo in Chivalry: Medieval Warfare; “survive 100 days” achievement in The Forest; “1001 Nights” achievement in Cities: Skylines; etc.
Do not use any “depot method” to access “easier” versions of games.
Depot methods are only to be used as described in Allowed Rule 15 below.
Examples: If a developer updates their game and changes the “difficulty” or design of a game then you are not allowed to depot back to an easier time in the game’s design history; etc.
Do not use console commands which directly and instantly unlock achievements.
Examples: “caqs” in Skyrim and Fallout 4; “unlock ach” in Into The Breach; anything similar to a “unlock_achievement x” type of command; etc.
Do not allow other users to access your account and earn achievements for you (including your “little brother” or your “cousin”).
You must earn your achievements yourself. Letting people earn achievements on your account is not allowed in general and if anyone cheats or breaks the rules on your account, you will still be held accountable.
Examples: Having a friend who is more skilled at a game complete a difficult section for you in a single-player game; letting someone log into your Steam account to beat a difficult part of a game for you on your account; letting your little brother work on a grindy achievement for you; etc.
Do not be abusive to developers via their Steam forums, social media, email, doxxing, etc.
You’re allowed to complain, ask for changes, leave negative reviews/comments and other such respectful criticisms, but you give all of us in the achievement hunting community a really bad name when you harass/attack developers because of what they did to their game’s achievements. Do not abuse Steam’s refund policy by purchasing a game, quickly 100%ing (hundoing) it, and then refunding it (“refundo”).
Examples: Issuing death threats or flagrant insults to devs because they added achievements to their game that you do not like; using extreme/excessive rudeness while demanding a developer remove or change achievements; etc.
Do not create or share cheating methods.
Examples: Teaching someone how to use SAM; sharing a non-allowed complex script; posting on the Steam forums to promote an egregious game file edit method; sending someone a link to Cheat Engine or a trainer; teaching someone how to hide cheating; creating a non-allowed complex script and sharing it around even if you never use it yourself; etc.
✅ Allowed - General Rules ✅
Console commands that do not directly/instantly unlock achievements are allowed.
Examples: “sv_cheats 1, x, sv_cheats 0”; god; tgm; spawn enemy; npc_kill; noclip; godmode; fly; most Steam console commands; etc.
In-game cheat codes/modes and in-game debug tools are allowed.
Examples: iddqd cheat code style commands typed into older FPS games or cheat options unlocked in certain games such as Duke Nukem 3D; speedup options in Steam’s Final Fantasy re-releases; etc.
Making use of in-game glitches, in-game exploits, and “cheesy” tactics are allowed.
Examples: breaking out out of normal bounds to avoid enemies; doing something strange inside of a game to “bug a game out” so you become invincible; accessing powerful items earlier than intended; standing somewhere enemies can’t hit you; etc.
“Save-scumming” and copying/transferring your own save files are allowed.
Please realize that transferring save files between platforms may cause identical unlock timestamps for the achievements that were imported. Having proof of your original progress is strongly recommended.
Examples: quicksaving/quickloading often; manually backing up a copy of your own save file and moving it back into your save folder after a game had deleted it; manually backing up a copy of your own save file and moving it back into your save folder in order to replay sections of a game before an important story junction; using your own Steam Cloud on multiple PCs to play the same game; transfering your own save file to a new PC; importing your mobile save file for Time Clickers, Final Fantasy Mobius, Realm Grinder, etc. (See: https://goo.gl/imGkqk for a list of mobile games with Steam transfer capabilities); transferring GTA V save between console and Steam; etc.
Using online guides/walkthroughs is allowed.
Examples: Steam guides; youtube video guides; GameFAQs; puzzle solutions; collectible lists; etc.
“Clickers / Autoclickers / Macros” are allowed.
A clicker is defined as hardware or software that manually or digitally mimics button presses. Clickers/autoclickers typically press one key rapidly or at a specific pace whereas macros might press 3 or more different keys in a specific order again and again. These tools are only allowed if they are for monotonous simple tasks and if they meet the “mechanical” conditions of achievement. This could be a weight on a key, a rubber band on a thumbstick, a turbo controller, an autoclicker program (AutoClicker, NIAutoClicker, FastClicker, etc.), a macro program (Joy2Key, Macro Recorder, etc.), and many mouse drivers come with macro programs installed by default as well.
Examples: Turning on an autoclicker in a clicker game to rapidly click the enemy; making a simple macro that forces your character to jump over and over to earn a “jump x times” achievement; using an autoclicker to rapidly fire your gun in a space shooter style game; letting an auto-clicker rapidly left-click through an entire kinetic novel; etc.
Getting “carried” or “twinked” in multiplayer games is allowed.
Examples: a skilled friend playing some Payday heists or Killing Floor games with you at a higher level than you could handle alone; a friend inviting you into their Terraria world and helping you kill some bosses; high-level friends donating gear to you; etc.
“Farming” and “boosting” achievements is allowed.
Note that although this is allowed in general for achievement hunting, many various online game communities are very against this sort of organized farming and will ban you for it.
Examples: trading kills back and forth in a shooter game; camping some location for a special item again and again; having one friend join and leave your game so you auto-win over and over; running a program such as Sandboxie in order to have multiple instances of a game open and farm yourself; etc.
Changing your OS system clock to get Date-Specific achievements is allowed.
Date-changing is allowed only for date-specific achievements that specify a certain single date. Date changing is not allowed to produce a passage of a specific amount of time (See Not Allowed Rule 9). Changing your OS system clock to complete more “daily challenge” type achievements without waiting is allowed also. Date-changing for date-specific achievements is allowed because of many games having many issues relating to time zones or natural de-sync with PCs, but these issues should not be present for longer-term “passage of time” achievements.
Examples: changing your PC’s date to the twelve dates needed for Calendar Man’s “Storyteller” achievement in Batman Arkham City; changing date to April 29th for “Happy Birthday Pixel!” in Cave Story+; completing multiple LYNE daily puzzles within a single day by changing OS date; etc.
Deleting Registry Values is allowed.
Sometimes games will break or add achievements and require a full reset to unlock further achievements - this is common with idle/spam games where achievements are triggered through registry values. You are allowed to delete those registry entries and reinstall the game to re-idle the time and try again to get it to trigger properly. You are not allowed to “edit” registry values (See Not Allowed Rule 4) to any specific number or value.
Examples: Many various spam/idle type games require either a registry wipe or playing on a new PC to “reset” the game and thereby re-idle the needed time (often for newly-added achievements or patches to these types of games); etc.
Use of in-game buttons and button combinations that developers add into the game to unlock achievements is allowed.
Note that using one of these may get your game auto-invalidated on AStats since the rules/enforcement on this have been extremely varied on AStats over the years. We will not penalize users for these actions here because this type of action is done fully in-game and we cannot really control what devs add to their games.
Examples: Incredipede; Redactem; Sweatshop; Daily Run; Plandzz; Rogue Legacy; etc.
Using in-game/in-app DLC and microtransactions (“p2w” / “Pay-to-Win”) is allowed.
Examples: Purchasing gems in Crush Crush with real world money; purchasing items/in-game currency with real world money to get a boost in many clicker games and f2p (Free-to-Play) games; purchasing powerful items with real world money in Warframe or TF2; etc.
Creating or using custom maps for games that support custom maps is allowed.
They still need to follow the other rules in terms of not auto-unlocking achievements, etc.
Examples: Creating or using custom maps in: Counter-Strike Source, CS:GO, Day of Defeat: Source, Pirates vs. Vikings II, Booster Trooper, ORION: Prelude; etc.
Simplistic Scripting is allowed to facilitate gameplay but not fully replace/emulate gameplay.
“Simple Scripting” is a macro or sequence of commands that helps facilitate “monotonous/repetitive” gameplay but does not entirely replace gameplay. Complex Scripting such as TAS-type scripts or Bots (typically used for MMOs) are not allowed (See Not Allowed Rule 8 above). Many of these simple scripts are written in AutoHotKey (AHK).
Examples: Writing a script to have your second PC and alt steam account auto-join your lobby and ready up so you can farm kills/wins against it; creating a .bat file to open and close a game rapidly for “open game x number of times” achievements as found in Garry’s Mod; simple AHK scripts to click multiple places on the screen at different intervals in clicker games; simple AHK scripts to start/end a game for “play as x character y times” type achievements such as in Metal Slug; etc.
The “Depot Method” is allowed only for games that broke themselves with an update.
This is a valid method of obtaining older or unique versions of games directly from Steam. This method is allowed because we can accurately determine where these files were sourced from (Valve) and obtaining them through Steam directly instead of a third party warez/torrent site does not break any copyright law, TOS, GNU/GPL, or SSA. This method is only allowed to obtain a working version of a game if the current present date version of the game is broken, or an achievement is broken due to a patch/update. This is not allowed to be used to access “easier” versions of a game (See Not Allowed Rule 11).
Examples: Ubinota - A March 28th, 2015 patch to the game seemingly broke the functionality for the achievement “Challenge n°1”, preventing the trigger from working properly. You can depot back to the March 4th, 2015 version of the game where the achievement functionality works; etc.
Most Steam Workshop Mods and Official Mods/Official Patches are allowed.
Steam Workshop mods are considered official and generally allowed (even Steam Workshop mods that alter gameplay) except in cases of “workaround achievement-enabling” mods or “Achievement Unlocker” mods (See Not Allowed Rule 7).
Examples: Installing and using most Steam Workshop mods, as long as they do not circumvent a game blocking achievements when it detects mods or grant you ways to instantly/directly unlock achievements (Not Allowed Rule 7); installing official, dev-provided H-patches (Hentai / Adult Content patches) which were downloaded outside of Steam in games where this is required for an achievement (many VN hentai games); downloading and using dev-provided accessory tools/patches to games; etc.
Fully Cosmetic Mods are allowed.
100% cosmetic-only mods are allowed, as long as they completely do not alter gameplay - this includes: texture packs, accessibility mods, mesh/lighting mods, nude mods, character portrait mods, mods that change how your player character looks, widescreen/aspect ratio mods, FoV mods, UI mods, HUD mods, and graphics overhaul mods. Unofficial mods that enable see-through walls/doors, wallhacking, outline/glow of enemies/items/etc. are not considered “cosmetic” and not allowed. Note that using any mods at all for online games might get you banned or VACed.
Examples: Installing high-resolution texture pack mods or lighting fixes for The Witcher 3 is allowed; changing the character portrait artwork for the villagers in Stardew Valley is allowed; reskinning your Skyrim character into a beautiful naked magical hentai pony is allowed; etc.
Modifying certain standard settings via .ini files is allowed.
Certain games contain an Initialization file (.ini file) which may be the only way to configure standard in-game options such as: resolution, aspect ratio, v-sync, windowed/fullscreen mode, directx version, standard keybindings, etc. Some games (namely Source games) use .ini files which can mimic “Launch Options” under a Steam game’s properties view or can auto-launch standard console commands upon running the game - these are allowed. Modifying any .ini file value outside of these typical (in-game visual/audio settings / console commands / launch options / standard keybinds) type of situations is not allowed and will be considered as game file editing, unless a specific game-by-game rule exists below.
Examples: Changing an .ini file to the exact 4:3 resolution your older monitor needs because the in-game settings only allow for widescreen; enabling v-sync for a game via .ini file because it lacks an in-game setting; hard-forcing directx9 for a game via .ini file; etc.
Reading game files and game code is allowed.
As long as you are not modifying any actual game file or game code, you are allowed to open game files/registry entries and simply read them. Unzipping/decompiling/decrypting a game file in order to read it is allowed as long as it does not violate either the game’s or Steam’s Terms of Service.
Examples: Opening up a ren.py Visual Novel game’s text file to see when a certain achievement unlocks; etc.
🎮 Game-By-Game Rules / Edge Cases 🎮
aMaze Achievements : Darkness
✅ AStats allowed the copy and pasting of an identical “sister” file “Assembly-CSharp.dll” from aMaze Achievements: Forest to “fix” aMaze Achievements: darkness by replacing the “Assembly-CSharp.dll” file in Darkness without penalty. AStats allowed this due to previous rulings on other games that involved copying files you own from one game to another version of the same game, specifically Red Orchestra 2 Single Player into Multiplayer. We will not penalize users for doing this because this is a long-established, unique AStats ruling.
Company of Heroes 2
❌ Use of the Steam Workshop Mod “Achievement M.10 - Zero-Risk Market Unlocker” is not allowed as it exhibits SAM-like behavior in auto-unlocking an achievement upon loading a map.
Dungeons of Dredmor
✅ The workshop mod to fix the Deadshot achievement by adding the skill back into the game was allowed on AStats.
❌ The workshop mod to fix the wand achievement has not been ruled on (not known how it operates at the moment) so it is not currently allowed.
❌ The mod for “Sewer Brew” was not allowed on AStats as it just triggers the achievement on load (SAM-like) and does not actually meet the criteria of the achievement (drink a beer with a developer).
✅ What Have You Done Achievement. It requires you to edit a mock, fake .txt file with any text and save it to then trigger the achievement the next time you start the game. We allow this as it is required for the Achievement and does not interact with any other configurations for the game. The fake empty .txt file was put there specifically by the developer to use for this achievement.
✅ On Christmas Eve, 2015 a large amount of achievement hunters were tricked by a “fake Garry” in a public server who was actually a hacker troll granting people the “Yes, I am the real Garry!” achievement. Typically this would be against the rules for achieving something via hacking instead of fulfilling the real requirements, but since so many achievement hunters were affected that day, it was deemed to be allowed for this one case.
✅ The “Brick your game (intentionally)” achievement requires you to open a game save file and type some gibberish and then open your game, which will result in crashing the game and earning the achievement - this is normally disallowed game file editing (Not Allowed Rule 3) but is allowed in this case. (Steam Guide)
✅ Use of Visual HUD mods/UI Improvement mods are allowed (HoxHUD/WolfHUD). While Payday 2 does not use Steam Workshop, a good amount of these mods have been “approved” by the developers.
❌ This does not allow other lua scripting/mods that alter the game in other ways outside of HUD/UI and do things such as: auto grant XP, increase XP gain, despawn enemies, grant achievements directly, allow more players in a game, allow players to carry more bags, increase loot, grant infinite ammo, grant invulnerability, etc.
❌ Playing with hackers or people obviously using these types of game-altering mods mentioned in point 2 above is not allowed. Please leave the game as soon as possible after noticing a hacker and realize that playing with a hacker may render your entire game invalidated as it will make your achievement and/or in-game stats appear as cheated.
Pixel Puzzles Ultimate
✅ Deleting a local copy of a file used to store Christmas event “advent calendar” data allowed users to gain near-infinite amounts of in-game currencies such as hints and golden puzzle pieces. While file deletion was “okayed” by AStats mods, users went further by changing file properties (specifically, making the file read-only), to speed up the process of deleting the save file again and again. This breaks the standard “do not edit game files” rule but is allowed in this one case.
Red Orchestra 2
✅ The Developers, Tripwire removed the Singleplayer mode from the Base Game of Red Orchestra 2, now renamed Red Orchestra 2 Multiplayer, and moved it to Red Orchestra 2 Singleplayer. The achievements still exist in the base game achievements list. AStats allowed users to copy the SinglePlayer folder entirely over to the root folder of the Multiplayer Game to allow for play and earning of Singleplayer Achievements. We also allow it and will not penalize users for this.
✅ Downloading the non-Steam Workshop “Skyrim Script Extender” for use with various official mods, including SkyUI, is allowed.
Ted By Dawn
✅ Ted by Dawn’s exe is actually a .zip compressed file not a traditional exe. Within that .zip folder is a steamapi.dll. This dll is outdated and does not properly trigger achievements. AStats allowed users to open that exe/zip and replace the dll with a working dll from any steam game available, usually the steamapi.dll from “Super Blue Boy Planet” a free to play game and dll downloaded directly from steam. Create new text file with name “steam_appid.txt” and insert value to file “381090”, then save.
✅ BFF Achievement. AStats allowed you to use a console command to unlock this achievement. We do not allow use of console commands to directly unlock achievements, but we will not penalize users for this specific achievement as this AStats rule has been established too long for us to effectively disallow it. We do discourage users from doing it. All other console commands that directly unlock achievements in a “get.achievement()” fashion are disallowed (See Not Allowed Rule 12).
😓 Penalties for Cheating 😓
Breaking Not Allowed Rule 1, Not Allowed Rule 3, or Not Allowed Rule 5 are each considered critical offenses and can result in you being immediately fully banned from the achievement trackers in addition to losing “verified” status on the 100Pals Discord until you complete cleaning and appeal via 100Pals staff member. Other forms of cheating and “not allowed” actions as described above can result in the point value of those individual games being invalidated and marked as cheated on your tracker profiles. If a user has a substantial amount of invalidated games or purposefully hides their cheating, that also may result in a de-verification on the 100Pals Discord and potential tracker-ban until a cleaning and appeal is completed. Violations of Not Allowed Rules 14 & 15 regarding harassing devs and sharing cheat methods can result in losing verification or being banned from the 100Pals Discord.
If a user refuses to appeal, abandons their appeal, or is dishonest during their appeal, they will be banned from the 100Pals Community and recommended for ban on the achievement trackers and partner communities. Note that certain trackers give cheaters one single chance to appeal, and perma-ban for all ban-worthy infractions following that.
👮 How to Clean & Appeal Cheating 👮
Various automatic-detection systems and inspector suite toolsets exist for moderation/inspector staff to police cheating across the achievement trackers. Players are also manually deep-dived at random and during initial verification by 100Pals Staff.
Upon ban-worthy cheating being detected, a 100Pals staff member will be in contact with you to let you know that cheating was detected. You will be instructed by the staff member and required to wipe the achievements of those cheated games either by in-game console commands or a relocker tool that the staff member will provide you with (please do not ever use SAM or relocker tools to lock achievements before speaking with a mod). A log of this will be created, archived, and provided to the achievement tracker moderation teams. Please see our Appeal Forum and Appeal FAQ.
If you wish to come forward and admit cheating, please PM a moderator on the 100Pals Discord or create an appeal on our Appeal Forum, this will be greatly appreciated and taken into consideration during your appeal.
Written with love by: ❤️ The 100Pals Staff Team ❤️
With generous assistance from: Several moderators and developers of: AStats, Completionist.me, Exophase, MetaGamerScore, and Steam Hunters.
And with valuable suggestions and input from dozens of tracker users and community members.
📋 Feedback 📋
If you have any comments or suggestions regarding the above rules you can leave anonymous feedback here: https://goo.gl/UJ7W9g or you can chat with us on the Discord. Additionally, proposed rule changes can be made by making a Gitlab pull request.
These rules will be amended from time to time and game-by-game rules will be created to clarify edge cases as needed.
✏️ Changelog ✏️
2019 Aug 2 - Minor changes to formatting and conversion to new site, and edited a few examples for accuracy/clarity
2019 JUL 15 - Added example to Allowed Rule 4.
- Clarified Penalties for Cheating section.
- Added exception links to Not Allowed Rule 3.
2019 JUN 29 - Added more in-doc reference links to rules.
2019 JUN 28 - Added clarifying text to Not Allowed Rule 3: Do not modify game code.
- Added thanks to community members for their continued input.
- Fixed typo.
2019 JUN 26 - Added feedback section & merged need help section.
2019 JUN 15 - Fixed typo in Allowed Rule 19. - Thanks, Sellyme!
2019 JUN 10 - Added Exophase to Penalties for Cheating partnership list.
2019 MAY 28 - Added in-doc reference links to several rules for easier navigation.
2019 MAY 26 - Added adoptive partners and fixing gramatical errors.
2019 JAN 17 - Rewrote Not Allowed Rule 7 to include in-game cheat/debug menus.
2019 JAN 04 - Added links to How to Appeal section.
2018 DEC 23 - Indexed Rules now all link to their respective descriptions. Added links to go back to Table of Contents.
2018 DEC 13 - Rewrote Not Allowed Rule 1 for clarity.
2018 NOV 12 - Added pencil emoji to Changelog header.
2018 OCT 07 - Added Allowed Rule 19: “Reading game files and game code is allowed.”
2018 SEP 26 - First upload of rules.