Guidelines for Programming games - Revision history

Ygdrazil at 08:51, 1 September 2014

2014-09-01T08:51:59Z

Arnoldemu at 11:52, 16 March 2013

2013-03-16T11:52:12Z

Arnoldemu at 11:51, 16 March 2013

2013-03-16T11:51:03Z

Arnoldemu at 17:34, 15 March 2013

2013-03-15T17:34:29Z

TFM at 17:07, 15 March 2013

2013-03-15T17:07:29Z

TFM at 17:06, 15 March 2013

2013-03-15T17:06:41Z

TFM at 15:30, 15 March 2013

2013-03-15T15:30:46Z

Arnoldemu at 13:25, 15 March 2013

2013-03-15T13:25:12Z

Arnoldemu at 13:20, 15 March 2013

2013-03-15T13:20:24Z

Arnoldemu: Created page with "The following are guidelines that you should consider when programming games: * Games should be playable with joystick alone. All menus and such should be possible to select u..."

2013-03-15T13:18:58Z

Created page with "The following are guidelines that you should consider when programming games: * Games should be playable with joystick alone. All menus and such should be possible to select u..."

New page

The following are guidelines that you should consider when programming games:
* Games should be playable with joystick alone. All menus and such should be possible to select using joystick alone. This allows the game to be played on GX4000 for example and to play it without needing to press a key. It could be also selectable with number keys or arrows.

* 'P' key should be used for pause in joystick control mode. This makes it compatible with the GX4000. It's pause button is mapped to the 'P' key.

* Both digital joysticks should be selectable to use. The Amstrad plus has both connectors, the CPC can have a second joystick using a joystick splitter or using one of the official Amstrad Joysticks.

* Analogue joystick on Plus should be selectable if Plus machine is used. You can detect if a Plus machine exists programatically. Analogue joystick can be used as an alternative to a digital joystick (this avoids "Keyboard Clash" when used in 2 player games in conjunction with keyboard or another digital joystick).

* It should be possible to select "No Sound", "Music", "Sound Effects" or "Music and Sound Effects" (where possible).

* If you are using overscan, consider that the position of the screen may not be the same on all monitors, so a method to centralise it before the game starts, or in the options of the game.

* It should be possible to redefine the keys to the choice the user wants, or to be able to choose from a preset list. Good key "presets" are cursors and space (good for cpc6128 and Plus more awkward for 464 and 664), q for up, a for down, o for left, p for right and space for fire.

* Games should support the FIRE 2 button for gamepads/joysticks. Maybe the player character needs to be able to jump, and then UP is used for this. And that is ok. Just don't forget to include the FIRE 2 button for jumping as well.

← Older revision		Revision as of 08:51, 1 September 2014
Line 42:		Line 42:

	* If a game relies on a specific memory configuration (e.g. 128K), then the game or it's loader should check for this, report it to the user and stop them from continuing. This avoids the user not understanding why the game didn't work on their computer.		* If a game relies on a specific memory configuration (e.g. 128K), then the game or it's loader should check for this, report it to the user and stop them from continuing. This avoids the user not understanding why the game didn't work on their computer.
		+
		+	[[Category:Programming]]

@@ Line 26: / Line 26: @@
   Directions: Cursors
-  Fire: Space OR copy
+  Fire: Space OR copyGood presets:
   Directions: Q, A, O, P
@@ Line 39: / Line 40: @@
 * The availability of memory expansions should be investigated. And if additional memory is found the game shall use it in some way. Examples are to add additional features or to load all levels at one at the beginning.

@@ Line 1: / Line 1: @@
 The following are guidelines that you should consider when programming games:
-* 'P' key should be used for pause in joystick control mode. This makes it compatible with the GX4000. It's pause button is mapped to the 'P' key.
+* Games should be playable with joystick alone. All menus and such should be possible to select using joystick alone. This allows the game to be played on GX4000 for example and to play it without needing to press a key.
-* Both digital joysticks should be selectable to use. The Amstrad plus has both connectors, the CPC can have a second joystick using a joystick splitter or using one of the official Amstrad Joysticks.
+One suggestion is that the game allows the user to press fire on the gamepad/joystick or the corresponding fire button on the keyboard.
-* Analogue joystick on Plus should be selectable if Plus machine is used. You can detect if a Plus machine exists programatically. Analogue joystick can be used as an alternative to a digital joystick (this avoids "Keyboard Clash" when used in 2 player games in conjunction with keyboard or another digital joystick) or to their full analogue ability where it makes sense in the game.
+The game recognises which was pressed and uses this to determine which controller will be used in game.
 * It should be possible to select "No Sound", "Music", "Sound Effects" or "Music and Sound Effects" (where possible).
@@ Line 12: / Line 18: @@
 * If you are using overscan, consider that the position of the screen may not be the same on all monitors, so a method to centralise it before the game starts, or in the options of the game.
-* It should be possible to redefine the keys to the choice the user wants, or to be able to choose from a preset list.
+* It is very important that keyboard controls should be redefineable. There is not one perfect control scheme for all, so this allows the controls to be chosen by the user.
-Good presets:
   Directions = Up, Down, Left, Right
@@ Line 27: / Line 35: @@
 * Consider supporting AMX Mouse (or compatibles such as Bryce's USB mouse hardware) and Symbiface 2 Mouse where it makes sense in the game. Movement could also be used for moving to the wanted menu item and clicking the mouse button to select.
-* The user should be able to choose the type of monitor. This will enable the game to adjust its colors to either a color monitor or a green / monochrome monitor.
+* The game should be playable on green screen or greyscale monitors in addition to colour monitors. This means things are easy to see and identify when used with all monitors. Ideally, the user should be able to choose the type of monitor, this will enable the game to adjust its colors to maximize the display for each monitor. Where games rely on colour, consider using visual differences in the tiles so they can be identified on monochrome monitors without needing to use colour but when used on colour displays they benefit from the extra colours.
-−
 * A game should provide a high score list (if it makes sense) and save it to disc.
 * The availability of memory expansions should be investigated. And if additional memory is found the game shall use it in some way. Examples are to add additional features or to load all levels at one at the beginning.

← Older revision		Revision as of 17:07, 15 March 2013
Line 18:		Line 18:
	* Consider supporting AMX Mouse (or compatibles such as Bryce's USB mouse hardware) and Symbiface 2 Mouse where it makes sense in the game. Movement could also be used for moving to the wanted menu item and clicking the mouse button to select.		* Consider supporting AMX Mouse (or compatibles such as Bryce's USB mouse hardware) and Symbiface 2 Mouse where it makes sense in the game. Movement could also be used for moving to the wanted menu item and clicking the mouse button to select.

−
	* The user should be able to choose the type of monitor. This will enable the game to adjust its colors to either a color monitor or a green / monochrome monitor.		* The user should be able to choose the type of monitor. This will enable the game to adjust its colors to either a color monitor or a green / monochrome monitor.

← Older revision		Revision as of 17:06, 15 March 2013
Line 17:		Line 17:

	* Consider supporting AMX Mouse (or compatibles such as Bryce's USB mouse hardware) and Symbiface 2 Mouse where it makes sense in the game. Movement could also be used for moving to the wanted menu item and clicking the mouse button to select.		* Consider supporting AMX Mouse (or compatibles such as Bryce's USB mouse hardware) and Symbiface 2 Mouse where it makes sense in the game. Movement could also be used for moving to the wanted menu item and clicking the mouse button to select.
		+
		+
		+	* The user should be able to choose the type of monitor. This will enable the game to adjust its colors to either a color monitor or a green / monochrome monitor.
		+
		+	* A game should provide a high score list (if it makes sense) and save it to disc.
		+
		+	* The availability of memory expansions should be investigated. And if additional memory is found the game shall use it in some way. Examples are to add additional features or to load all levels at one at the beginning.

@@ Line 12: / Line 12: @@
 * If you are using overscan, consider that the position of the screen may not be the same on all monitors, so a method to centralise it before the game starts, or in the options of the game.
-* It should be possible to redefine the keys to the choice the user wants, or to be able to choose from a preset list. Good key "presets" are cursors and space xor copy (good for CPC6128 and Plus more awkward for 464 and 664), q for up, a for down, o for left, p for right and space for fire.
+* It should be possible to redefine the keys to the choice the user wants, or to be able to choose from a preset list.
 * Games should support the FIRE 2 button for gamepads/joysticks. Maybe the player character  needs to be able to jump, and then UP is used for this. And that is ok. Just don't forget to include the FIRE 2 button for jumping as well.

← Older revision		Revision as of 13:25, 15 March 2013
Line 15:		Line 15:

	* Games should support the FIRE 2 button for gamepads/joysticks. Maybe the player character needs to be able to jump, and then UP is used for this. And that is ok. Just don't forget to include the FIRE 2 button for jumping as well.		* Games should support the FIRE 2 button for gamepads/joysticks. Maybe the player character needs to be able to jump, and then UP is used for this. And that is ok. Just don't forget to include the FIRE 2 button for jumping as well.
		+
		+	* Consider supporting AMX Mouse (or compatibles such as Bryce's USB mouse hardware) and Symbiface 2 Mouse where it makes sense in the game. Movement could also be used for moving to the wanted menu item and clicking the mouse button to select.