From e1f7043d87e2f9a947a4c29c95fa028b67407301 Mon Sep 17 00:00:00 2001 From: Micah Allen Date: Thu, 1 Nov 2018 08:47:02 -0400 Subject: [PATCH] Update README.md --- README.md | 10 ++++++---- 1 file changed, 6 insertions(+), 4 deletions(-) diff --git a/README.md b/README.md index 5658824..0d072e1 100644 --- a/README.md +++ b/README.md @@ -1,9 +1,11 @@ **rage-eventbus** simplifies two-way communication between the RAGE Multiplayer server, client, and browser instances. It can be used as a full-on replacement for RAGE's built-in `mp.event` API, providing consistency and clarity. -### Examples +--- -#### Server to Client +## Examples + +### Server to Client **Situation:** The server wants to ask a specific player if they are currently running. @@ -36,7 +38,7 @@ rbus.on('getIsRunning', () => mp.players.local.isRunning); --- -#### CEF to Server +### CEF to Server **Situation:** A CEF instance wants a list of all vehicle license plates directly from the server. @@ -66,4 +68,4 @@ rbus.on('getAllLicensePlates', () => { With `rage-eventbus`, CEF can directly communicate with the server and vice-versa. -###### In vanilla RAGE, you would have to set up multiple events for sending/receiving on the client-side, call them from CEF, then resend the data to the server and back. It's a hassle. \ No newline at end of file +###### In vanilla RAGE, you would have to set up multiple events for sending/receiving on the client-side, call them from CEF, then resend the data to the server and back. It's a hassle.