Difference between revisions of "Equipment/The Beast"

From London Hackspace Wiki
Jump to navigation Jump to search
(Created page with "== Keymappings == === Player 1 === * Directions: Left Arrow, Right Arrow, Up Arrow, Down Arrow * Buttons: Z, X, C === Player 2 === * Directions: J (left), K (down), I (up), L (r...")
 
Line 1: Line 1:
 +
This is the big arcade machine that lurks in the space.
 +
 +
It has indies games on it, and emulators.
 +
 
== Keymappings ==
 
== Keymappings ==
 +
 +
Don't change these, as it'll break all the indie games that rely on them.
 +
 
=== Player 1 ===
 
=== Player 1 ===
 
* Directions: Left Arrow, Right Arrow, Up Arrow, Down Arrow
 
* Directions: Left Arrow, Right Arrow, Up Arrow, Down Arrow
Line 40: Line 47:
 
Alternatively, you could load a splash video. This needs to be in ogg format, and goes in the "splashScreenPath" variable. You also need to set the variable "splashIsVideo" to true.
 
Alternatively, you could load a splash video. This needs to be in ogg format, and goes in the "splashScreenPath" variable. You also need to set the variable "splashIsVideo" to true.
  
I've just been dumping all the games into the <tt>arcade_games</tt> folder, accessible via the public share.
+
I've just been dumping all the games into the arcade_games folder, accessible via the public share.

Revision as of 22:43, 16 September 2011

This is the big arcade machine that lurks in the space.

It has indies games on it, and emulators.

Keymappings

Don't change these, as it'll break all the indie games that rely on them.

Player 1

  • Directions: Left Arrow, Right Arrow, Up Arrow, Down Arrow
  • Buttons: Z, X, C

Player 2

  • Directions: J (left), K (down), I (up), L (right)
  • Buttons: N, M, B


Launcher software

This lives at http://github.com/v21/Boinger. Any improvements gratefully welcomed, although you will need a Pro version of Unity3D to compile it. I know, sorry. One improvement would be rewriting it to not require this.

Adding games to the launcher

All games should run fullscreen at 1024 * 768 resolution. They should also survive being exited abruptly, as the launcher software isn't particularly gentle when it quits things.

The launcher reads the games avaliable from a json file called local.json, which sits in the arcade_games folder linked on the desktop. If The Beast is plugged into the network, it should appear as a Windows fileshare on machine //INDIEBOX/

The format looks like this:

{"games" :

[
	{
		"name" : "game2", 
		"author" : "me" , 
		"filePath" : "C:/Users/Public/arcade games/SumoBOSSRace.exe",
		"splashScreenPath" : "file://C:/Users/v21/Documents/My Dropbox/Launcher/Assets/tex2.png"
	}
]
}


The splash screen is the screen that's displayed on the arcade machine when cycling through the games. This works best if it's a 1024 * 768 png. Ideally it'll be exciting and eyecatching, tell people what the game is and who made it, maybe tell them what keys to press and maybe exhort them to push start. But it's up to you.

Alternatively, you could load a splash video. This needs to be in ogg format, and goes in the "splashScreenPath" variable. You also need to set the variable "splashIsVideo" to true.

I've just been dumping all the games into the arcade_games folder, accessible via the public share.