Pixel Starships 2: Basic Crew AI Setup Guide (Levels 1-6)

To set up basic crew AI between Hull Levels 1 and 6 in Pixel Starships 2, create a two-line script that places an emergency repair trigger on Line 1 above a permanent stationing command on Line 2. This structure forces the game engine to check damage conditions first, ensuring crew members leave their stations to fix broken compartments and immediately return to man primary systems once repairs finish.

How Top-to-Bottom AI Evaluation Operates

The Pixel Starships 2 AI engine processes commands sequentially from the top down. During each combat tick, the engine scans your command list and executes only the first instruction whose condition evaluates to true. Any command situated beneath that active line is ignored for that tick. If a condition evaluates to false, the engine steps down to the next row.

Vertical ordering dictates priority completely. High-priority survival triggers must occupy the top slots, while routine duties and passive room-manning belong at the bottom as default fallbacks.

Configuring the Command Center and Grid Space

Accessing AI menus requires a Command Center, but the facility does not need to remain powered or even placed on your active deck once you finish programming:

1. Build the Command Center: Construct the room to open the crew and weapon scripting interfaces.
2. Program AI Routines: Enter your top-to-bottom command lines directly into each crew member's profile.
3. Store the Facility: Move the Command Center into ship inventory or cut its power. Your crew retains all programmed behaviors in combat, freeing power and deck tiles for reactors, shields, and weapons.
4. Research Python AI: Upgrade the room via the Academy or Lab as your hull advances to unlock advanced health thresholds and targeting options.

The Standard Two-Line Crew Script

Without scripting, crew members stand motionless during battle, leaving damaged systems broken and combat rooms unbuffed. The standard two-line foundation automates emergency repairs and station maintenance:

• Line 1: Friendly Room HP < 100% –> Target Friendly Room
• Line 2: None –> Target [Designated Duty Room]

At the start of combat, all rooms sit at 100% health. Line 1 evaluates to false, causing the engine to read Line 2. Because None functions as an unconditional pass, the crew member walks to their assigned combat post (such as the Shield Generator or Laser Room) to provide passive stat buffs. When an enemy attack damages a system, Line 1 becomes true, directing the crew member to repair the damage. Once the compartment returns to 100% health, Line 1 evaluates to false again, prompting the crew member to return to their Line 2 station.

Role-Specific AI Configurations

Assigning the same universal repair command to every crew member causes deck-wide bottlenecks and leaves essential combat systems unmanned. Tailor behaviors based on individual crew stats:

Common Early AI Errors and Fixes

If your crew behaves unexpectedly during combat, check your script order for these common logic faults:

• Permanent Lockout: Placing None –> Target Room on Line 1 prevents the engine from ever reaching Line 2. Because None is always satisfied, the crew member will never leave that room to fix broken systems elsewhere.
• Stranded Crew Members: Omitting Line 2 leaves pawns without instructions once repairs finish. A crew member who repairs a damaged compartment will freeze in place after the room hits full health instead of returning to their battle station.
• Elevator Congestion: Forcing all crew members to cross vertical elevator shafts at the same time creates movement delays. Assign repair duties primarily to dedicated runners stationed on central decks to keep transit lanes clear.