Event Codes

From TACWiki
Jump to: navigation, search

Event codes are used by the game to identify events specific to certain criterion for actions the player performs in game. These criterion include information for many of the scientific experiments handled in game, as well as basic event identification for input handling.

The Event codes are grouped into two distinct groups. The first group identifies codes which are universal throughout the game. The second group is defined on a game by game basis, meaning that each internal mini game or the main game itself identify what these codes mean. The universal codes cannot be changed.

Due to the limitations of the parallel port that is used to print out this data in a lab setting, the codes can only range from 0-255, taking up only an 8 bit space.

Universal Codes

-2 - Debugging Test Code. Negative codes are assumed by the logger to be debug information only. This can be toggled within the logger whether these are recorded or not.

-1 - Debugging Enabled. This code signifies that debugging is enabled to the logger.

0 - The clear code. This is used by the parallel port to sense the data correctly, by monitoring high-to-low and low-to-high measurements. This cannot be changed.

254 - The start game code for Metoer Madness.

255 - End Current Game.

256 - ERROR.

Game Specific Codes

Game specific codes can be in the range from 1 to the last given start game code. This allows for having the largest number of codes per game as well as optimizing the code specification, as the codes are specified from the beginning of the enum to whatever the last valid enumeration is.