More actions
| Scrum | |
|---|---|
 | |
| General | |
| Author | Jeffrey Pfau |
| Type | Puzzle |
| Version | 2015 |
| License | Mixed |
| Last Updated | 2015/01/04 |
| Links | |
| Download | |
| Website | |
| Source | |
Scrum is an entry for the GitHub Game Off 2012 competition. It's a puzzle game based on a simple premise: How to misrepresent programming as a game without making it some arbitrary minigame that may or may not involve Pipe Mania?
The game is primarily written in C, with a hint of ARM assembly, and compiled for the GBA. It also runs in your web browser.
User guide
Basics
When you start the game, you're dumped into a "development environment" as it clones the repository so you can begin your very long night of coding. The board is populated and then you can begin. The main gameplay consists of trying to complete lines of code in your program.
Each line contains blocks of four colors. You can place new blocks into the line of your choosing, and when you fill up the line all the way up to the delimited column, the portion of that line that matches the last color on the line is cleared.
You can clear an whole line by making the line entirely one color. Be careful, though! The more lines you clear, the harder the game gets. You only get a limited amount of time to decide which line a block should go on, and the more lines you have, the shorter that duration gets.
Debugging
If, however, you go over the line, you've made one bug for each column over you go. Furthermore, if you place a block of a mismatched color onto an existing line, you also get a bug. Watch your bug count! If it goes too high, you need to start debugging and will be automatically kicked into the debugger!
If your bug counter isn't greyed out, you can voluntarily enter debugging mode. You can manually exit the debugger when you've patched enough bugs, or if you meet your quota, you'll get kicked out of the debugger automatically. If you fail at debugging, however, it's game over.
Branch
But what's a good development environment without a good revision control system behind it? You can also create a local branch, each branch has its own score, line count and bug count, and you only get one local branch at a time, so use it wisely.
Once you have a local branch, you can switch between your local branch and the master branch, merge your changes back into master, or get rid of the local branch that you're not currently on.
Unfortuantely, it seems that the version of git you're using isn't very good at resolving merge conflicts of colored blocks, so any changes you've made on the other branch are lost when you merge.
Controls
A - Place new block, Fire (debugging mode)
B - Enter/Exit debugging mode
L - Create a local branch
R - Get rid of a local branch
Select - View high score when selecting a difficulty
Start - Pause
Screenshots
External links
- Official website - http://endrift.github.io/scrum/
- GitHub - https://github.com/endrift/scrum