| Command | Result | | :--- | :--- | | GiveResource Supplies X | Adds X supplies (e.g., GiveResource Supplies 500 ). | | GiveResource Intel X | Adds intel. | | GiveResource EleriumDust X | Adds elerium. | | GiveResource AlienAlloy X | Adds alloys. | | GiveEngineeringTech [tech name] | Instantly researches a tech. Names are case-sensitive. Try GiveEngineeringTech Hybrid_Materials | | MakeItemsAvailable | Unlocks all non-story items in engineering. Great for testing. | LWOTC’s 9+ classes are complex. These commands let you fix a mis-click or test a perk tree.
Long War of the Chosen (LWOTC) is a masterpiece of masochism. It takes the already punishing XCOM 2: War of the Chosen and stretches it into a 100+ hour campaign of strategic anxiety, where one missed 85% shot can unravel weeks of progress. But what if you want to peek under the hood? What if a bug strands your best soldier, or you simply want to skip the grind to test a late-game build? lwotc console commands
That’s where come in.
But when a Gatekeeper clips through the floor on a Haven Assault, or the Chosen Warlock refuses to spawn, the console transforms from a cheat into a lifeline. | Command | Result | | :--- |
The console does not ask for confirmation. RemovePerk LeadByExample will silently delete a cornerstone officer perk. GiveTech All will unlock plot techs and break the story progression. | | GiveResource AlienAlloy X | Adds alloys
So press that tilde key. Type carefully. And may your Long War be long—not broken. Have a specific LWOTC command you swear by? Check the XComGame log files in Documents\My Games\XCOM2 War of the Chosen\Binaries\Win64\Launch.log —every console action is recorded there for debugging.
Treat the console like a developer’s keycard: powerful, useful in emergencies, but capable of shutting down the whole facility if mishandled. LWOTC is an endurance test, not a sandbox. Console commands are best used to preserve your run from bugs or to understand how mechanics work—not to give yourself 10,000 supplies on Legendary.