mirror of
https://github.com/italicsjenga/valence.git
synced 2024-12-23 14:31:30 +11:00
41bcd1eb2c
## Description Did an api for advancements. Issue: https://github.com/valence-rs/valence/issues/325 Each advancement is an entity, it's children is either criteria, either advancement. Root advancement has no parent. Also did an event AdvancementTabChange (listens if client changes advancement's tab) ## Test Plan Use an example "advancements" |
||
|---|---|---|
| .. | ||
| 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 | ||
| 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