How are events handled...
Summary
In NEET computers, some computer interactions cant / shouldn't be handled with API calls, in these situations (such as user inputs, peripheral interactions, external stimuli, or other triggers), information pertaining to the interaction are recorded as "events"
Events consist of a list of values, starting with a descriptor of the event and followed by event specific parameters containing information about the event, for example a key press event would look like ["keyPressed", <number representing the key>, <a letter representing the key, or nothing if not applicable>, <modifier key mapping>]
Event Access
(warn) doesn't currently work like this but it will soon
Events are categorized into special groups, including user, legacy, system, networking, and external; each of these groups represent a buffer, that fills with events that pertain to the category, these buffers can have their oldest entry pulled out of them (read and removed) using the events API.
If a event buffer overfills it limit of 35 events, the oldest event will be automaticly destroyed to make room. additional event buffers can be disabled in code, causing them to not receive new events (for performance reasons).