registerCommand("dev.spawn.ship", permission: "dev", args: ["template","--x","--y","--faction"], handler: (args, ctx) => if (!ctx.devmode) throw Error("Requires devmode"); let pos = clampCoordinates(args.x, args.y); let ship = spawnShipFromTemplate(args.template, pos, args.faction); return success:true, message:`Spawned $ship.name ($ship.id)`, data: ship.toJSON() ;
If the vastness of the "Unknown Space" becomes overwhelming, these commands can help you navigate or clear obstacles:
When using AddTech or SetFlag , you often need the internal ID for specific modules. Some common ones include: DEFAULT.ARMOR_1 / DEFAULT.ARMOR_2 DEFAULT.BATTERY_2 / DEFAULT.BATTERY_4 DEFAULT.BATTLESTATIONS DEFAULT.BEAMS_1 Tips for Better Console Usage
Critics might argue that console commands can be used to "cheat" and undermine the intended progression system. This is a valid concern regarding game design, but it is one that is easily mitigated by implementation choices. The existence of commands does not necessitate their constant use. Developers can disable achievement tracking when commands are used, ensuring that the integrity of the "leaderboard" or standard progression remains intact. Additionally, keeping the console hidden by default (requiring a specific key combination to access) ensures that casual players are not tempted to break their immersion, while power users have the tools they need readily available.
| Command | Effect | Better Use Case | | :--- | :--- | :--- | | unlock | Unlocks all warp gates. | Use if a gate refuses to activate after meeting requirements. | | additem [ID] [qty] | Adds specific quest items. | Add datapad 1 if an alien datapad despawns. | | resetquest [name] | Resets a specific quest stage. | Use resetquest scanner if the scanner tutorial fails to trigger. |