It was totally a thing. Games are done! Well, more or less.

Entries

In no particular order

Name Author Language Description
Pork rightfold Befunge, C++ A herding simulator where you have to prevent some pigs from escaping
Sheep and Cabbage Abyx C++ A herding simulator where you have to fix a fence before the sheep escape and eat the cabbage
Fugam Ell Ruby Herd the shadows to let them escape
Herding Simulator 2014 Rapptz C++ A herding simulator
Bad Rats 2: Hyperactive Rats Cat and Robot C# A roguelike where you try to fix your broken zombie robot and escape a dungeon full of hyperactive rats.
Fishy DeadMG and melak47 C++ Run away from the sheep!
Prison Breakage Bartek and Cicada Lua Evade the herding guards!

Awards

Any vagueness in the description of the award criteria is probably intended.

Best game

Awarded to the entry that is the best when viewed as a whole.

  1. Gold: Sheep and Cabbage
  2. Silver: Fugam
  3. Bronze: Prison Breakage

Best content

Awarded to the entry that has the best content (visuals, story, whatever).

  1. Gold: Prison Breakage
  2. Silver: Fugam
  3. Bronze: Fishy

Best gameplay

Awarded to the entry that has the best game mechanics.

  1. Gold: Sheep and Cabbage
  2. Silver: Prison Breakage
  3. Bronze: Herding Simulator 2014

Best bug

Awarded to the entry with the best bug.

Worst code

Awarded to the worst code snippet.

Minor award nominees

Award Game
Extreme Finger Workout Award Bad Rats 2: Hyperactive Rats
No Idea What To Do Award Herding Simulator 2014
Best Invisible Character Fishy, for “invisible sheepdog”
Best Joke Bad Rats 2: Hyperactive Rats, for “stab avoidance device”
Took Minimum Number Of Hours To Get Working A Bit And Was Actually Sorta Runnable Award Fishy

Rules

Organisatorial

  1. The event takes place on 22 February 2014 between 18:00 and 23:00 UTC.
  2. Participants may be individuals or teams of two.
  3. A few minutes before the start of the event, three themes are picked randomly: Escape, Herding, and Repair what’s broken. Each participant has to incorporate two of those themes in their entry.
  4. Each participant must have their entry published on a publicly available source code repository when the event ends.
  5. Each entry must be accompanied by a ‘‘description’’ of its contents, including any build/run/play instructions that might be required.

Technical

  1. All programming languages are allowed.
  2. External libraries are allowed with the following conditions:
    1. The libraries used must be available under an open source license.
    2. The libraries used must be disclosed in the entry’s description.