toolbox/robust-toolbox-template
toolbox/robust-toolbox-template
Template
2
0
Fork 0
mirror of https://github.com/space-wizards/RobustToolboxTemplate.git synced 2026-10-24 06:12:50 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions

Add repo tests and fix build (#12)
Some checks failed
Build & Test / build (ubuntu-latest) (push) Has been cancelled
Details

Browse source
This commit is contained in:
metalgearsloth 2026-07-14 14:05:02 +10:00 • committed by GitHub
parent aee689e94c
commit 2aa315c03c
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
7 changed files with 177 additions and 15 deletions
Download patch file Download diff file Expand all files Collapse all files

2
README.md
View file

@ -7,7 +7,7 @@ This template additionally includes some helpful IDE settings if you're using Vi
An example file structure for Resources is also provided.
### Wait, why would I use RobustToolbox?
RobustToolbox is a fairly modern ECS game engine with strong multiplayer support. Out of the box, it's netcode is capable of handling hundreds of players (as demonstrated by the game it was originally written for, [Space Station 14](https://spacestation14.io/)) and is relatively easy to use with less risk of common mistakes like giving clients authority over game state compared to other engines.
RobustToolbox is a fairly modern ECS game engine with strong multiplayer support. Out of the box, its netcode is capable of handling hundreds of players (as demonstrated by the game it was originally written for, [Space Station 14](https://spacestation14.io/)) and is relatively easy to use with less risk of common mistakes like giving clients authority over game state compared to other engines.
It provides prediction-based server authoritative netcode by default, with options to both autogenerate simple state synchronization for components and to manually implement more complex state application algorithms as necessary. Additionally, basic RPC is provided through networked entity events (which can be sent both ways, and optionally targeted at specific entities) alongside direct access to the underlying transit layer for more direct control when necessary.