valence/crates
Carson McManus 975014e76b
tag registry (#350)
- add Tags extractor
- add tags.json to extracted
- send `SynchronizeTagsS2c` packet on join
- fix encode

## Description

Adds a `TagsRegistry` resource that contains all the information needed
to build and send `SynchronizeTagsS2c` on join.

closes #349
2023-06-01 23:21:25 -07:00
..
valence Move packets out of valence_core. (#335) 2023-05-29 01:36:11 -07:00
valence_advancement Move packets out of valence_core. (#335) 2023-05-29 01:36:11 -07:00
valence_anvil Reorganize Project (#321) 2023-04-21 14:43:59 -07:00
valence_biome Reorganize Project (#321) 2023-04-21 14:43:59 -07:00
valence_block Move packets out of valence_core. (#335) 2023-05-29 01:36:11 -07:00
valence_build_utils Reorganize Project (#321) 2023-04-21 14:43:59 -07:00
valence_client tag registry (#350) 2023-06-01 23:21:25 -07:00
valence_core tag registry (#350) 2023-06-01 23:21:25 -07:00
valence_core_macros Move packets out of valence_core. (#335) 2023-05-29 01:36:11 -07:00
valence_dimension Reorganize Project (#321) 2023-04-21 14:43:59 -07:00
valence_entity Move packets out of valence_core. (#335) 2023-05-29 01:36:11 -07:00
valence_instance Move packets out of valence_core. (#335) 2023-05-29 01:36:11 -07:00
valence_inventory Move packets out of valence_core. (#335) 2023-05-29 01:36:11 -07:00
valence_nbt Reorganize Project (#321) 2023-04-21 14:43:59 -07:00
valence_network Move packets out of valence_core. (#335) 2023-05-29 01:36:11 -07:00
valence_player_list Move packets out of valence_core. (#335) 2023-05-29 01:36:11 -07:00
valence_registry tag registry (#350) 2023-06-01 23:21:25 -07:00
valence_spatial_index Reorganize Project (#321) 2023-04-21 14:43:59 -07:00
README.md Advancement api (#329) 2023-05-02 01:35:35 -07:00

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