mirror of
https://github.com/italicsjenga/valence.git
synced 2025-01-10 23:01:31 +11:00
61f2279831
## Description Basic implementation of world border World border is not enabled by default. It can be enabled by inserting `WorldBorderBundle` bundle. Currently, this PR only implements world borders per instance, I'm considering expanding this per client. However, the same functionality can be achieved by Visibility Layers #362 <details> <summary>Playground:</summary> ```rust fn border_controls( mut events: EventReader<ChatMessageEvent>, mut instances: Query<(Entity, &WorldBorderDiameter, &mut WorldBorderCenter), With<Instance>>, mut event_writer: EventWriter<SetWorldBorderSizeEvent>, ) { for x in events.iter() { let parts: Vec<&str> = x.message.split(' ').collect(); match parts[0] { "add" => { let Ok(value) = parts[1].parse::<f64>() else { return; }; let Ok(speed) = parts[2].parse::<i64>() else { return; }; let Ok((entity, diameter, _)) = instances.get_single_mut() else { return; }; event_writer.send(SetWorldBorderSizeEvent { instance: entity, new_diameter: diameter.diameter() + value, speed, }) } "center" => { let Ok(x) = parts[1].parse::<f64>() else { return; }; let Ok(z) = parts[2].parse::<f64>() else { return; }; instances.single_mut().2 .0 = DVec2 { x, y: z }; } _ => (), } } } ``` </details> example: `cargo run --package valence --example world_border` tests: `cargo test --package valence --lib -- tests::world_border` **Related** part of #210 |
||
|---|---|---|
| .. | ||
| valence | ||
| valence_advancement | ||
| valence_anvil | ||
| valence_biome | ||
| valence_block | ||
| valence_build_utils | ||
| valence_client | ||
| valence_core | ||
| valence_core_macros | ||
| valence_dimension | ||
| valence_entity | ||
| valence_instance | ||
| valence_inventory | ||
| valence_nbt | ||
| valence_network | ||
| valence_player_list | ||
| valence_registry | ||
| valence_spatial_index | ||
| valence_world_border | ||
| README.md | ||
Crates
The standard crates used in Valence projects.
All crates here are exported by the main valence crate. valence is the intended interface for both end users and plugin authors.
Crates are versioned in lockstep with the exception of valence_nbt.
Ignoring transitive dependencies and valence_core, the dependency graph can be described like this:
graph TD
network --> client
client --> instance
biome --> registry
dimension --> registry
instance --> biome
instance --> dimension
instance --> entity
player_list --> client
inventory --> client
anvil --> instance
entity --> block
advancement --> client
world_border --> client