https://github.com/oguzeroglu/rhubarb

A WebSocket library optimized for multiplayer JS games, works on WebWorkers with binary data.
https://github.com/oguzeroglu/rhubarb

game-development game-server html5 javascript multiplayer webgl websocket websocket-library webworker

Last synced: about 1 month ago
JSON representation

A WebSocket library optimized for multiplayer JS games, works on WebWorkers with binary data.

• Host: GitHub
• URL: https://github.com/oguzeroglu/rhubarb
• Owner: oguzeroglu
• License: mit
• Created: 2019-12-28T23:33:59.000Z (almost 5 years ago)
• Default Branch: master
• Last Pushed: 2022-12-11T18:41:37.000Z (about 2 years ago)
• Last Synced: 2024-10-26T20:38:32.397Z (about 2 months ago)
• Topics: game-development, game-server, html5, javascript, multiplayer, webgl, websocket, websocket-library, webworker
• Language: JavaScript
• Homepage:
• Size: 876 KB
• Stars: 199
• Watchers: 10
• Forks: 8
• Open Issues: 21
• Metadata Files:
  • Readme: README.md
  • License: LICENSE

Awesome Lists containing this project

README

        
# Rhubarb

[See Wiki page](https://github.com/oguzeroglu/Rhubarb/wiki)

Rhubarb is a lightweight WebSocket library for multiplayer HTML5 games. It is originally designed to be used by the [ROYGBIV Engine](https://github.com/oguzeroglu/ROYGBIV). However it can be used outside of ROYGBIV as well.

Rhubarb is named after this [Aphex Twin track](https://www.youtube.com/watch?v=_AWIqXzvX-U).

Rhubarb works both on browsers and NodeJS.

![](/rhubarb.gif?raw=true)    

## Philosophy

Javascript is slow, therefore we want to have as much main-process-power as we can

in order to do game related calculations, graphics rendering and achieving 60 FPS.

For multiplayer games achieving 60 FPS gets even more complicated given that transferring data

over WebSockets is a slow operation. It also triggers GC activity by copying the transferred

data (if JSON is the preferred way), which eventually slows down the main thread as well.

Rhubarb is designed to overcome these problems by:

1. Using WebWorkers to handle networking out of main thread -> More time left for rendering in main thread

2. Using transferables between the main thread and the worker to prevent GC activity (zero copy)

3. Redefining/compressing and sending protocols using Float32Arrays -> Much less bandwidth consumption than *JSON.stringify*.

4. Allowing users to define their protocols in a high-level way and taking care of all the dirty bitwise operations internally.

5. Allowing sharing same protocol definitions between server/client.

6. Allocating objects only when being initialized. Reusing everything to prevent GC activity (That means *mutating* things, yeah get over it.)

## Installation

For clients: ` `

For servers: `npm install rhubarb-js`

## Usage

See [this tutorial](https://github.com/oguzeroglu/Rhubarb/wiki/Getting-started) to see how to use Rhubarb.

See [here](https://github.com/oguzeroglu/Rhubarb/wiki/API-reference) for the API reference.

## Demo

See [here](https://github.com/oguzeroglu/Rhubarb/wiki/Demos-and-how-to-start-them)

## Licence

Rhubarb uses MIT license.