#client-server #shared #definition #game-server #voxel #voxel-game #perovskite

perovskite_core

Multiplayer voxel game written in Rust - Implementation details shared between client and server

4 releases

0.0.4 Jun 23, 2024
0.0.3 Feb 24, 2024
0.0.2 Dec 31, 2023
0.0.1 Sep 3, 2023

#1213 in Game dev

Download history 17/week @ 2024-07-29 25/week @ 2024-09-16 20/week @ 2024-09-23 7/week @ 2024-09-30

245 downloads per month
Used in 3 crates

Apache-2.0

51KB
1K SLoC

This crate contains core definitions shared between Perovskite clients and servers. It doesn't make sense to use on its own, unless you're writing some kind of middleware, loadbalancer, custom client, protocol translator, etc.

The constants and definitions will generally offer a somewhat stable API; the network protocol may evolve quickly, with protocol version mismatches mediated by logic in the client and server crates.

However, its definitions are useful in conjunction with the APIs in either perovskite_game_api (if you want to write game content) or perovskite_server (if you need lower level engine access).

Please see the perovskite_game_api and perovskite_client crates to run a game server and join a game, respectively.

Dependencies

~10–16MB
~220K SLoC