The client is an A-Frame component and the soul of the implementation. Here's a bit about it.
Note
This is work in progress and hasn't been tested properly yet.
Setup
To use simply add a script tag to the file.
Notice the socket being a separate tag. That's a requirement.
Usage
The idea is to keep the usage as minimal and simple as possible using it is simple. Use multi-frame tag on the object you want to sync and provide a unique mfId throughout the network. Example:
For server config:
We recommend using namespace as it is. And example server is available in connectors. The connector is not full fledged and has been designed to work for the demo. You can however write your own websocket server with a namespace given.
To start the multiplayer environment, simple call
This would start the environment based on the CONFIG set.
Reporting
Add any request, suggestion or bug in issues. I'll take it up.