Steev/JS-Server-Framework
Archived
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Update readme.md

Browse Source
This commit is contained in:
steevLP 2019-09-27 15:16:20 +02:00 committed by GitHub
parent aca9e3f199
commit 34b3e45ff8
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 6 additions and 6 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
readme.md
View File

@ -23,18 +23,18 @@ and this can go on for ever but, this should show the point of a packet
## Events ## Events
Something need to happen with your packet and the Event Handler is handling it Something needs to happen with your packet! The Event Handler is handling it.
The Handler is taking in a **Event Name** and a **Function** for it The Handler is taking in a **Event Name** and a **Function** for it.
so it should look like this: So it should look like this:
``` ```
{name:'logout', function() {eventFunction(possible,arguments)}}, {name:'logout', function() {eventFunction(possible,arguments)}},
``` ```
but somewhere your event need to be defined But somewhere your event need to be defined!
as default they are stored in *bin/classes/events* As Default they are stored in *bin/classes/events*
and a normal event is build like this and a normal Event is build like this:
```js ```js
event_funcition(){ event_funcition(){
Console.log('Your code here please'); Console.log('Your code here please');