Pip and Waddleton

Pip and Waddleton

  • Steinzer
  • 11 months ago
  • 44th

Description

Lead Prof. Waddleton and his trusty assistant Pip out of this building without getting seen. Both of them must reach the end of the level without getting persecuted by evil robots.


Characters

stuff Waddleton (left) can shoot darts that destroy enemies. Pip (right) can go stealth.


Controls

  • WASD - movement
  • E - use skill
  • RMB - switch characters
  • Shift (Hold) - move the camera/view [move the mouse to define what you wanna see]

Items

  • Darts - restores 1 dart use
  • Milk - restores 1 stealth use

Known Bugs

  • Pip has collision problems.
  • Finishing Level 3 brings you to an empty room. That's the end of the game!
  • Going fullscreen affects Help text display.
    • You can avoid this by playing in Windowed mode instead.
  • Fatal error with obj_spotted.
    • If possible, don't shoot enemies when they're chasing you.
    • If you encountered this, I'm afraid you're gonna have to restart the game. :(

Feedback
8

You must be logged in to leave feedback
Register an account or log in to start writing.

Post-mortem

What went wrong

1. Effort spread out too thin; quantity over quality

I focused too much on making the game stand out from the common genre during dev time that I completely missed making the game stand out on its own without comparison from others. Too much planned features to make, too little polish on what's actually already there.

2. Unorganized planning/project management

Unlike my previous gm48 entry, I didn't plan this out too much. The design, features and even the style was decided on the fly. This caused me to keep on doing stuff that may have been better as possible updates in the future rather than chocking them in the 48 hours of dev time for a stealth game.

3. It feels "hollow".

Aside from the lack of sound, by my standards, the graphics are underwhelming and disappointing. To think that the enemies have "better" animations compared to the main characters is just... annoying. Not to mention the lack of a premise that actually ties the whole thing together.

What went right

1. Somewhat pulling off a stealth game

Never could have thought of making a game of this genre. Despite its failures, I'm proud of what I managed to put out after 48 hours. In my history of jamming alone, I actually managed to make a playable game.

2. PATHS

Somehow, using Path Editor and mp_* functions to make paths actually worked. I dreaded them once, I still do, but they did their thing, which is nice.

Lessons

  1. Plan. Dev. Polish. In that order. Not skipping one.
  2. Should dedicate polish time instead of more content.
  3. Cliche but good > unique but poorly executed. It backfires. Like, A LOT.
  4. Have fun. Seriously.
Result 44th
Loading...