Skip to main content

Amazon Review: Triple Town

Triple Town is the first released game on the Amazon Kindle. I was really excited to try this out, and I'm happy to be one of the first to write a review. Now, I know there are going to be a lot of nay sayers about the obviously lacking computing power of a device like the Kindle, which was designed to be lower power and function to read books, not run games. However, we should all be very familiar with the rules about limits in design: they can push us into greater heights. Is Triple Town the end all of gaming? Of course not. Is it a damn fine game that I'm happy to spend some time with? Absolutely.

Triple Town is what you get if you strip an RTS to its core and make into something of a puzzle game. Danc has a great write up on the design limits that needed to be worked around and where a game like this fits into a map of what works and what simply isn't fun, and finds a snug little place for itself.

Honestly, I'm loving the game. Not just as a neat novelty to have a game on my Kindle, but as a game that I am honestly hooked on as soon as I started playing! The game play is pretty simple and based on a casual match-three, but replacing the usual gems or abstract shapes with units in a town-building game. You plant grass and match them up to make flowers, which you match to make bushes, etc. You can defeat enemies by trapping them, turning them into tombstones, which you can match up to build churches, cathedrals, and more. You have to do a lot of planning to keep room on the board to work with, while also keeping blocked off areas for traps. I like to think I've figured out some strategies that are working pretty well.

I do have my complains. For example, the match-path you need to build a house, in a game about building a town, is grass, flower, bush, tree, logging, and finally the house. It takes more work to build than anything else I've found in the game, and that bothers me just from a perspective of presenting the theme of the game. I think the logging or the flowers could have been cut. I also would have liked to see the highscores online, so I know if I'm doing good or just suck.

Overall, if I was a game reviewer I'd be giving Triple Town a 4/5 and I certainly recommend anyone with a Kindle to grab a copy for only $2.99 at the Amazon store.

Comments

Popular posts from this blog

Why I Switched From Git to Microsoft OneDrive

I made the unexpected move with a string of recent projects to drop Git to sync between my different computers in favor of OneDrive, the file sync offering from Microsoft. Its like Dropbox, but "enterprise."

Feeling a little ashamed at what I previously would have scoffed at should I hear of it from another developer, I felt a little write up of the why and the experience could be a good idea. Now, I should emphasize that I'm not dropping Git for all my projects, just specific kinds of projects. I've been making this change in habit for projects that are just for me, not shared with anyone else. It has been especially helpful in projects I work on sporadically. More on why a little later.

So, what drove me away from Git, exactly?

On the smallest projects, like game jam hacks, I just wanted to code. I didn't want to think about revisions and commit messages. I didn't need branching or merges. I didn't even need to rollback to another version, ever. I just …

Respect and Code Reviews

Code Reviews in a development team only function best, or possible at all, when everyone approaches them with respect. That’s something I’ve usually taken for granted because I’ve had the opportunity to work with amazing developers who shine not just in their technical skills but in their interpersonal skills on a team. That isn’t always the case, so I’m going to put into words something that often exists just in assumptions.
You have to respect your code. This is first only because the nature and intent of code reviews are to safeguard the quality of your code, so even having code reviews demonstrates a baseline of respect for that code. But, maybe not everyone on the team has the same level of respect or entered a team with existing review traditions that they aren’t acquainted with.
There can be culture shock when you enter a team that’s really heavy on code reviews, but also if you enter a team or interact with a colleague who doesn’t share that level of respect for the process or…

CARDIAC: The Cardboard Computer

I am just so excited about this.


CARDIAC. The Cardboard Computer. How cool is that? This piece of history is amazing and better than that: it is extremely accessible. This fantastic design was built in 1969 by David Hagelbarger at Bell Labs to explain what computers were to those who would otherwise have no exposure to them. Miraculously, the CARDIAC (CARDboard Interactive Aid to Computation) was able to actually function as a slow and rudimentary computer. 
One of the most fascinating aspects of this gem is that at the time of its publication the scope it was able to demonstrate was actually useful in explaining what a computer was. Could you imagine trying to explain computers today with anything close to the CARDIAC?

It had 100 memory locations and only ten instructions. The memory held signed 3-digit numbers (-999 through 999) and instructions could be encoded such that the first digit was the instruction and the second two digits were the address of memory to operate on. The only re…