Nomenclature

Script naming nomenclature:
 * Scripts names are left to the programmer's discretion. If one of the following nouns is used however, these are their definitions:
 * Script overseeing activity of a single entity: controller.
 * Script overseeing activity of multiple entities: manager.
 * One of the scripts composing an entity and overseen by a controller: component.

Coding nomenclature: Method naming nomenclature: EventType nomenclature: File example:
 * All data types use PascalCase.
 * All private fields use _camelCase.
 * All properties, private or public use PascalCase.
 * All public fields use PascalCase.
 * All constants use UPPER_CASE.
 * All parameters use camelCase.
 * Feel free to deviate from this nomenclature if there's reason to.
 * For callbacks invoked by events the method's names must be as such: ProcessEventTypeEvent.
 * For callbacks invoked by properties the method's names must be as such ProcessPropertyNameProperty.
 * Keep similar types of events close in the list. (ie: inputs all one after another, all damage events one after another, etc.)
 * For similar types of events put the more general descriptor first (ie: INPUT_LEFT_STICK, INPUT_ABUTTON and not LEFT_STICK_INPUT, ABUTTON_INPUT).