A minecraft creative server built for redstone. Each 256x256 plot runs on its own thread, allowing for less lag, more concurrency, and many awesome extra features!
MCHPRS is very different from traditional servers. Because this server is tailored to the use of computation redstone, many things that are a part of Vanilla Minecraft servers simply don't exist here. That being said, MCHPRS comes with many of its own unique features.
If the Rust compiler is not already installed, you can find out how on their official website.
git clone https://github.com/StackDoubleFlow/MCHPRS.git
cd MCHPRS
cargo build --releaseOnce complete, the optimized executable will be located at ./target/release/mchprs or ./target/release/mchprs.exe depending on your operating system.
| Command | Alias | Description |
|---|---|---|
/rtps [rtps] |
None | Set the redstone ticks per second in the plot to [rtps]. (There are two redstone ticks in a game tick) |
/radvnace [ticks] |
/radv |
Advances the plot by [ticks] redstone ticks. |
/teleport [player] |
/tp |
Teleports you to [player]. |
/stop |
None | Stops the server. |
/plot info |
/p i |
Gets the owner of the plot you are in. |
/plot claim |
/p c |
Claims the plot you are in if it is not already claimed. |
//pos1 |
//1 |
Sets your worldedit first position. |
//pos2 |
//2 |
Sets your worldedit second position. |
//set [block] |
None | Sets all the blocks in your selection to [block] |
//replace [oldblock] [newblock] |
None | Replaces all of the [oldblock] in your selection with [newblock]. |
//copy |
//c |
Copies your selection into your clipboard. |
//paste |
//p |
Pastes your clipboard into the world. |
//count [block] |
None | Counts all [block] in your selection. |
//load |
None | Loads a schematic from the ./schems/ folder. Make sure the schematic in the Sponge format if there are any issues. |
- @AL1L for his contributions to worldedit and other various features.
- @DavidGarland for a faster and overall better implementation of
get_entryin the in-memory storage. This simple function runs 30% of the runtime for redstone.
Pull requests are welcome. For major changes, please open an issue first to discuss what you would like to change.
When the server starts up, the main thread, which will from now on be referred to as the server thread, loads the Config.toml file and starts the networking thread. Threads communicate using message passing.
The server thread handles the initialization process of the server and the login/ping procedure for connecting clients. If a client completes the login procedure, a Player struct will be loaded containing the client.
The networking thread handles all incoming clients. When there is a new client, a client thread is created. The client is then sent to the server thread through message passing.
The client thread manages the TCP connection between the Minecraft client and this server. The client thread sends incoming packets to the server thread or a plot thread depending on its state.
The plot thread handles most of the logic for the server. This is where the real magic happens. Player movment, player rotation, worldedit, command handling, world saving/loading, etc. is all handled by this thread. If this thread crashes somehow, the player will be sent back to the server thread to be moved to another plot*.