Pingus – Penguin Puzzle Adventure

v0.7.6 (December 24, 2011)

• Added 10 new Christmas-themed levels.
• Introduced new SVG icons for the game interface.
• Added the ability to sort levelsets by priority in the level selection menu.

v0.7.5 (October 25, 2011)

• Fixed a memory leak in the OpenGL renderer.
• Added support for Win32 cross-compilation using mingw32.
• Introduced game speed adjustments via Keypad +/– and single-stepping with “S”.
• Improved the application icon.
• Enabled access to all levelsets in developer mode (Ctrl+M).
• Added 10 new Halloween-themed levels.

Support

• Github
• Wiki
• Offical

General Level-Creation & Worldmap Tips:

• Pingus’s built-in level editor (press Ctrl+E in the main menu) lets you craft custom levels. Set the spawn-point, exit, and available actions. Test frequently with Ctrl+T to ensure logic flows.
• Levelsets can be sorted by priority (introduced in v0.7.6). If you create a fan levelset, assign a higher “priority” number so that it appears above base campaign sets.

Resource Management & Quota Efficiency:

• Each level displays your total allowed actions (e.g., 10 builders, 5 bashers) at the top of the screen. Always count required paths first never assume you’ll need all actions.
• Minimize “overbuild”: if a single-tile gap exists, use a basher instead of assigning a 3-step builder.
  In levels that require multiple tunnels, consider digging diagonally when possible to reduce lumps of earth that must be removed later.

Advanced Gameplay Mechanics:

• Armageddon Button (“A”): Instantly sacrifices all current Pingus to generate a fresh wave. Useful if you’ve trapped all existing Pingus in an inescapable area—but you lose your current survivors, so only use as a last resort.
  “Floaters” & “Bombers” (introduced in certain Halloween/Holiday levels):
  – Floater: Assign with F to let a Pingu fall safely from one higher platform to a lower platform by using an umbrella.
  – Bomber: Assign with O to have a Pingu explode, clearing blocks in a radius (kills the Pingu, but can clear mandatory paths).
• Using “Pause + Single-Step” (“P,” then S) to observe “next-tick” Pingu positions—vital for complex multi-tool timing.

Multiplayer & Cooperative Play:

• Pingus supports local hot-seat multiplayer (two players alternate assigning tools), but there is no built-in network play. For a “shared screen” mode, simply pass the keyboard back and forth once all Pingus in a level are on screen.
• Split-view custom maps: You can place two exits and spawn points in a single level, designing cooperative challenges (e.g., each player must save X Pingus to open the other’s path).

Performance & Compatibility Tips:

• On modern Linux distributions, install via Snap (sudo snap install pingus-game) or via the PPA to get automatic updates.
• For macOS Ventura or later, use the 64-bit .dmg. If you see “unidentified developer” errors, Control-Click → Open on the .dmg, then Allow in System Settings → Security & Privacy.
• If you experience lag on older hardware, disable OpenGL rendering by launching Pingus with --disable-opengl.

1. Tutorial & Early Levels (Levels 1–10)

Objective: Rescue the required quota of Pingus (often 3–5) using limited tools.

Actions Available:

• Blocker: Press Space (or click the blocker icon) to turn a walking Pingu into a blocker. Blocks redirect other Pingus.
• Builder: Press B to assign a Pingu to build a short 3-step bridge.
• Basher: Press R to have a Pingu dig horizontally through one tile.
• Digger: Press D to have a Pingu dig diagonally downward.
• Jumper: Press J to make a Pingu leap over one tile.
• Miner: Press M to mine diagonally downward through two tiles.
• Floaters, Bombers, Unknown: Some levels introduce these as you progress.

Strategy:

• Observe each level for pitfalls and traps before assigning actions.
• Use blockers at chokepoints to redirect groups into safe zones.
• Build minimal bridges—overbuilding wastes resources.
• Practice “one-step” digs early to visualize paths.

2. Mid-Game Levels (11–50)

New Mechanics Introduced:

• Multi-tool levels where you must juggle builders and bashers under tighter quotas.
• Timed “Armageddon” button (“A”) that sacrifices all Pingus to create a new thread of spawn Prompts (rarely optimal, but useful if many Pingus are irretrievably lost).
• “Levelsets” like “Desert,” “Factory Campaign,” and Halloween/Campaign levels that introduce complex traps (poison gas, falling rocks).

Common Pitfalls:

• Over-stacking bridges when a single span would suffice. Always count platform length.
• Mis-timed jumps—use “Pause” (P) liberally to survey landing zones.
• Wasting key actions early—if a level requires saving 5 Pingus but you only have 3 digger actions, plan chain digs in advance.

Tips:

• Assign one Pingu as a “scout” (just walk him straight) to check if a passage is safe before sending the main group.
• Hold action icons at exit ramps to queue the next action the moment a Pingu arrives.
• Use “One-Key” changes—e.g., press “B” or “R” repeatedly to queue actions as Pingus approach a doorway or pit.

3. Late-Game & Holiday Levels (51–77 + Christmas/Halloween Levels)

Level Characteristics:

• High-difficulty puzzle layers requiring precise timing (e.g., a mix of jumpers, basher, miners in rapid succession).
• Hidden secret areas—some levels contain underground shortcuts accessible only if you dig past the visible boundary.
• Winter/Halloween levels introduce moving platforms, poison gas, and multiple exits (only one counts towards the quota).

Advanced Tactics:

• Layered block-and-build tactics: Use blockers to funnel Pingus onto narrow conveyors before invoking a mass build.
• Simultaneous tool allocation: As Pingus flow through a choke point, rapidly switch between builder, basher, and miner to keep movement fluid.
• “Armageddon” failsafes: If you’ve lost too many Pingus, the “Armageddon” button can spawn fresh Pingus—but only use if you’re at least halfway through the level, or you might squander your final lives.
• Time/Quota trade-off: Some Halloween or Christmas levels require saving a large number of Pingus under a strict timer—if you delay a single action by 0.5 seconds, you can lose an entire run. Use Pause + Single-Step (“S”) to spot precise jump timings.