valence

The valence_generated crate contains the majority of Valence's generated Rust code used for handling Minecraft's protocol and entity data.

Note: This crate is currently intended to be an implementation detail of the valence_protocol and valence_entity crates. End-users should generally interact with those higher-level crates rather than using valence_generated directly.

The java_string crate provides an implementation of Java strings that is tolerant of invalid UTF-16 encoding. This is specifically designed to allow for round-trip serialization of all Java strings, including those containing invalid UTF-16, while still permitting standard string operations.

Key technical details:

• Encoding: Uses a modified UTF-8 encoding called "semi-UTF-8". This encoding allows surrogate code points (U+D800 to U+DFFF inclusive), enabling zero-cost conversion from Rust strings to Java strings.
• JavaCodePoint type: An analogue to Rust's char, but explicitly allows surrogate code points.
• API Parity: Most methods are designed to be entirely analogous to the Rust standard library (std) string methods. For detailed documentation on specific method behaviors, refer to the Rust std documentation.

The valence_network crate is the plugin responsible for accepting network connections and spawning clients. It manages the initial stages of the protocol, specifically:

• Handshaking
• Status
• Login

It handles everything that occurs before the main Play stage begins. It also includes built-in support for proxies such as Velocity and BungeeCord.

Note: valence_network is optional. You may choose to exclude it if you are using Valence for testing purposes or if you are integrating Valence as a server within a client.