Corruption Of Champions 2 Console Commands Apr 2026

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!”

Maya hesitated. She didn’t want to cheat. She just wanted to fix the bug. So she decided to be a .

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.

She copied her save file to a new folder. “First rule of console commands: never experiment on your main run.” corruption of champions 2 console commands

Relieved, she closed the console.

She found the wiki. The command she needed wasn’t for giving herself infinite stats—it was flag:set "Sunstone_Obtained" 1 .

Maya smiled and typed her response: “You can’t reverse that easily. But here’s how to use the console safely to reset your max HP to the normal level: stat:set baseHP (your level*15 + 50) — and next time, back up your save first.” Later, she saw a player in the game’s

So she made a third rule:

That’s when she remembered the second rule from the forum: “Don’t solve roleplaying problems with console commands. Solve technical problems with them.”

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. She just wanted to fix the bug

She remembered an old forum post about “console commands.” A quick search later, she found the list: cofc2-console-commands.txt .

But then, curiosity crept in. What if she gave herself 5000 gems? Or changed her corruption level? She pulled up the command list again.

She opened the console (Ctrl + Shift + C), typed carefully, and pressed Enter. A quiet Flag updated. appeared. She checked her inventory. The amulet was there. The quest updated. The bug was fixed.