She copied her save file to a new folder. “First rule of console commands: never experiment on your main run.”
Maya stared at her screen, frustrated. She was deep into a Corruption of Champions 2 playthrough as a calm, pure-hearted fox-mage, but a nasty bug had locked her out of a key quest item—the Sunstone Amulet . No matter what she did, the game wouldn’t register that she’d picked it up. corruption of champions 2 console commands
Later, she saw a player in the game’s Discord asking: “Help! I used ‘stat:add HP 9999’ and now my character won’t take damage at all, and a main story boss won’t trigger!” She copied her save file to a new folder
She had wanted to earn the pure ending. If she just set corruption = 0 instead of resisting temptations in-game, it would feel hollow. And if she accidentally toggled debug_mode = true , she might break events permanently. No matter what she did, the game wouldn’t
But the post had a warning: “With great power comes great corruption… of your save file.”
That’s when she remembered the second rule from the forum: “Don’t solve roleplaying problems with console commands. Solve technical problems with them.”
She remembered an old forum post about “console commands.” A quick search later, she found the list: cofc2-console-commands.txt .