Difference between revisions of "enet.event"
m (→Description) |
(→Description) |
||
Line 2: | Line 2: | ||
An [[enet.event | event]] is a table generated by [[enet.host:service | host:service()]] or [[enet.peer:receive | peer:recieve()]] which will '''always''' contain a [[string]] named ''type'', a [[enet.peer]] named ''peer'', and a [[string]] or [[number]] named ''data'' depending on the kind of event. | An [[enet.event | event]] is a table generated by [[enet.host:service | host:service()]] or [[enet.peer:receive | peer:recieve()]] which will '''always''' contain a [[string]] named ''type'', a [[enet.peer]] named ''peer'', and a [[string]] or [[number]] named ''data'' depending on the kind of event. | ||
− | Though be weary that [[enet.host:service | host:service()]] and [[enet.peer:receive | peer:recieve()]] can return nil if no events are in the queue. | + | Though be weary that [[enet.host:service | host:service()]] and [[enet.peer:receive | peer:recieve()]] can return [[nil]] if no events are in the queue. |
== Structure == | == Structure == |
Revision as of 04:43, 10 October 2014
Description
An event is a table generated by host:service() or peer:recieve() which will always contain a string named type, a enet.peer named peer, and a string or number named data depending on the kind of event.
Though be weary that host:service() and peer:recieve() can return nil if no events are in the queue.
Structure
event.type | event.peer | event.data |
---|---|---|
"receive" | peer | string |
"disconnect" | peer | number |
"connect" | peer | number |