All Packages
Package Summary
Package
Description
Root of the Fidorial API: the
Server and its entry points.Annotations documenting the API itself.
Attribute modifiers carried by items.
Chat types: how messages sent to players are decorated.
Damage sources and the combat service.
Brigadier commands: registration, sources and senders.
Argument types for Brigadier commands.
Custom argument types built on top of native ones.
Arguments resolved against the source running the command, such as selectors and relative or local positions.
Dialogs: modal windows shown to players, and the values they send back.
Entities and players, online or offline.
Goals and pathfinding driving mobs.
Status effects running on living entities.
Bending the built-in mobs, and writing new ones.
The event bus: subscribing to, posting and cancelling events.
Events fired when blocks are placed or broken.
Events fired about entities.
Events fired by farming: soil being tilled, getting wet, drying out or trampled, plants growing,
fertilizer being used, and harvests dropping.
Events fired about a single player.
Events fired by redstone: a signal spreading through dust, components switching, blocks reacting
to being powered, pistons moving, and the block updates carrying it all from one block to the next.
Events fired about the server as a whole.
Game rules, server-wide and per world.
Containers and the inventories of players.
Item stacks and the item registry.
Values of the data components items carry.
Data components: the typed data attached to item stacks.
Enchantments, vanilla or added by plugins, synchronised with clients like the other data-driven
registries.
Maps: the 128×128 pictures drawn on
filled_map items.Bans and the whitelist.
Permission nodes, their defaults and how they are resolved.
Plugin entry point, context and metadata.
Crafting recipes: the vanilla ones the server ships with, and the ones plugins add.
Registries, and the keys addressing their entries and tags.
Running tasks on the region threads, and their performance.
Services: the pieces of server behaviour plugins can replace.
Sound events played by the server.
The status shown in the multiplayer server list.
Persistence backends for player data, inventories and enderchests.
Scenario tests run against a real server.
Annotations marking scenario tests.
Worlds, chunks and positions.
Biome definitions and the biome registry.
Block types, block states and their behaviour.
Traits of block states, one per common property.
Block states of specific blocks, combining several traits.
Environment attributes of dimensions and biomes.
Farming: soil, the plants growing on it, and the engine making them grow.
Fluids and their simulation.
World generators and the chunks they fill.
Redstone: the signals blocks emit and read, and the engine that carries them.
Datapack structures and templates.
The day/night cycle of worlds.
The weather of worlds.