UNIX

3

I Know This

Global Game Jam entry by Gavin McCarthy, Adam Axbey and Matthew Simmonds takes its influence from a computer hacking scene from Jurassic Park:

Remember that one scene in Jurassic Park? The one where Lex hacks the computer system in order to lock a door and protect everyone from the raptors, and exclaims…

That was basically the whole premise for our game.

It starts with the same basic premise as the scene in the movie : you have to find a file. To make it more interesting than your average hidden object game, you need to hack specific Search Nodes (purple files) which, upon successful hacking, will help you narrow down which potential Golden Folder contains what you’re looking for. Don’t pick the wrong one though, all the other ones are full of viruses and bad stuff!


Fun fact : the filenames you’ll see in the game are lifted from your hard drive, and 8.3ified for formatting and retro-chic reasons!
 
Hacking involves mashing your keyboard until code appears, and hitting the return key where the line endings are, just like in real life. The hacking minigame was heavily inspired by hackertyper.net, a fantastic way to feel like you’re real good at making up C code on the fly. However, we gamified it (oh, the horror) by not letting you go further than line endings, and adding a timer.

You can download the game and find out more here

4

Screens of Jurassic Park posters

I’ve been wanting to do some JP fan art for a while. I got pretty excited after watching the trailer for Jurassic World, so I made these 4 fan posters to celebrate that. 

All of the posters are from things that appear on tv or computer screens in the first movie. 

I used a lovely free font called Lovelo for all of these. It’s awesome, here’s the website: http://fontfabric.com/lovelo-font/

2

The 1993 action game Doom? Yeah, it can manage *nix processes.

Initially started by a University of New Mexico student in 1999 and improved a year later, psDoom is a novelty source port that doubles as a process manager. Monsters tied to processes on the system are spawned in a secret area of E1M1 (or MAP01), with their process details printed on top of them. Wounding these “pid monsters” adjusts their priority, while killing them… kills the process. To make things a little less self-destructive, processes can’t damage each other with infighting.

From the author’s website:

I will not assume any liability for damage caused from running this code. Especially if you are running it as root. In fact, we both know that this will cause damage to the system, and that’s why you want to try it. You have been warned.

Thanks to suicunedude for reminding me of this!