Pight Level Editor — Full Guide

The Pight level editor ships with the full Steam release—not the free demo. It extends the game’s lifespan beyond the ninety-level campaign and lets you practice individual mechanics in isolation. Mindlabor advertises the editor on the store page alongside achievements and Steam Cloud; this guide explains how to use it productively without a text manual in-game.

If you have not purchased yet, read demo review and release and launch to confirm editor availability in your build.

Accessing the editor

After installing the retail app (2682270):

1. Launch Pight from Steam.
2. Open the main menu—editor entry sits alongside campaign and settings (exact label is icon-driven; look for create/edit affordance post-credits or from menu).
3. Ensure you are on the full game, not the demo app 2779090.

First-time access may appear after completing the campaign or from the start depending on patch version—if missing, verify game files and check updates hub for editor-related notes.

Editor philosophy

Pight’s campaign teaches through play; the editor assumes you learned. You place:

• Terrain — walls and void boundaries
• Standard and special blocks — pistons, stickies, hard blocks, dynamite, portals, power tiles
• The light block — always the win condition (light block goal)

No scripting language—logic emerges from geometry, like the main game.

Building a level step by step

1. Set board size and walls

Start small. Three-by-five grids teach one idea; sprawling boards hide broken logic. Draw walls first so pistons cannot push off unintended edges.

2. Place the win condition

Drop the light block and its power path before adding distractions. Ask: “What is the last tile that energizes the lamp?”—same backward planning as campaign levels.

3. Add pistons and movers

Orient pistons carefully. Test extend/retract cycles immediately. Mis-aimed pistons are the top cause of unsolvable player levels.

4. Introduce one special mechanic

Follow Mindlabor’s pacing: one new idea per level. A portal puzzle should not also introduce dynamite unless you are explicitly challenging friends.

Reference block types for interaction rules.

5. Playtest with undo mindset

Test as a player, not as a designer who knows the solution. Use the same unlimited undo philosophy as campaign play. If you brute-force during test, note which pushes were non-obvious—those are your puzzle.

6. Difficulty pass

Add red herring blocks sparingly. Pight’s charm is fairness, not trolling. Compare difficulty to mechanics tier list tiers when calibrating.

Testing win and fail states

Verify:

• Lamp can glow in at least one solution path
• Dynamite cannot accidentally hard-lock the lamp before players learn the rule
• Portal pairs are matched and reachable
• Hard blocks block only what you intend

Trigger fail intentionally once—destroy the lamp, confirm reset works.

Sharing custom levels

Mindlabor’s editor ecosystem may use Steam Workshop or file export depending on patch level—check in-game share button and Steam news at launch. Community practice:

• Post levels in Discord (official links)
• Name levels after the mechanic taught (portal-facing-test)
• Screenshot the solved glow for thumbnails

When sharing, credit that your puzzle uses Pight’s editor tools; respect Mindlabor’s IP for commercial reuse.

Learning from the campaign

Replay campaign levels mentally while editing:

• Levels 1–10: piston spacing
• Levels 20–30: stickies and hard blocks
• Levels 40–50: dynamite discipline
• Levels 50–60: portals
• Levels 70–90: electricity and redstone-style routing

Rebuild a simplified version of a tough official level to see how Mindlabor constrained tile count.

Editor as practice tool

Stuck on High Voltage or Nether-mind achievements? Recreate miniature versions in the editor. Strip a late-game level to one portal and one lamp until the facing click becomes muscle memory—then return to campaign. Link achievements guide for trophy names.

Pair editor sessions with the puzzle planning checklist so habits transfer both directions.

Limitations and expectations

• Editor is single-player—no shared build mode.
• Textless UI means experimentation over documentation.
• Updates may add tiles or QoL—watch demo update history style posts for retail patches.
• Custom levels do not unlock Steam achievements by themselves.

Related reading

• Puzzle planning checklist — design-time process
• Tier list hub — mechanic reference
• Mindlabor Puzzles compared — other titles without editors
• Official links — Discord for feedback on shared levels

The level editor turns Pight from a ninety-level story into a sandbox. Build small, test honestly, share generously—and keep the light block sacred.