Difference between revisions of "Socket Event Definitions"
From Another End
(→New - Need Handlers Implemented) |
(→New - Need Handlers Implemented) |
||
| Line 17: | Line 17: | ||
| N/A || | | N/A || | ||
Client Side, I need {listener: {listener obj}, nodeid: #} | Client Side, I need {listener: {listener obj}, nodeid: #} | ||
| − | || | + | || listenerCompleted |
|} | |} | ||
Latest revision as of 22:20, 21 January 2015
Contents
Client-Side
New - Need Handlers Implemented
| Event Name | Expected Input | Output Event |
|---|---|---|
| gameStateUpdate |
|
N/A |
| N/A |
Client Side, for now I just need the event type |
playerAction |
| N/A |
Client Side, I need {listener: {listener obj}, nodeid: #} |
listenerCompleted |
Done - Implemented
| Event Name | Expected Input | Output Event |
|---|---|---|
| gameStart |
|
N/A |
| terrainReturn |
|
N/A |
| objectReturn |
|
N/A |
Marked for Deletion
| Event Name | Expected Input | Output Event |
|---|---|---|
| newChunk | ?? | N/A |
| newObjects |
|
N/A |
Server-Side
New - Need Handlers Implemented
Done - Implemented
| Event Name | Expected Input | Output Event |
|---|---|---|
| playerPositionUpdate |
|
N/A |
| requestTerrain |
|
terrainReturn |
| requestObjects |
|
objectReturn |
| ExampleR3C1 | ExampleR3C2 | ExampleR3C3 |
Marked for Deletion
| Event Name | Expected Input | Output Event |
|---|---|---|
| requestChunk |
|
newChunk |
| objectsToSend |
|
newObjects |
