mirror of
https://github.com/italicsjenga/valence.git
synced 2025-01-26 13:36:35 +11:00
Change 'Flexible' bullet in README.md
With the introduction of `valence_protocol` and some future plans, I've decided it's unrealistic to try and hide all the protocol code. There are situations where direct access is necessary.
This commit is contained in:
parent
420f2d1b7c
commit
b8e41cbb9a
1 changed files with 2 additions and 2 deletions
|
@ -15,9 +15,9 @@ like a minigame server without need for vanilla game mechanics, you can depend o
|
|||
Valence aims to be the following:
|
||||
|
||||
* **Complete**. Abstractions for the full breadth of the Minecraft protocol.
|
||||
* **Flexible**. Your use case should be achievable without manually sending and receiving packets or other hacks.
|
||||
* **Flexible**. Valence provides direct access to Minecraft's protocol when necessary.
|
||||
* **Minimal**. The API surface is small with only the necessities exposed. Opinionated features such as a
|
||||
standalone executable, plugin system, and reimplementation of vanilla mechanics should be built in a separate crate on
|
||||
standalone executable, plugin system, and reimplementation of vanilla mechanics should be built in a separate project on
|
||||
top of the foundation that Valence provides.
|
||||
* **Intuitive**. An API that is easy to use and difficult to misuse. Extensive documentation is important.
|
||||
* **Efficient**. Optimal use of system resources with multiple CPU cores in mind.
|
||||
|
|
Loading…
Add table
Reference in a new issue