Uses of Package
org.bukkit

Packages that use org.bukkit
Package
Description
 
Deprecated block API, replaced by SoundGroup and RayTraceResult.
Deprecated Brigadier integration, replaced by Commands.
Entity pathfinding, ranged attack and targeting API.
 
 
Events relating to the Brigadier command tree, such as the commands and suggestions sent to clients.
 
Inventory events.
 
 
Root package for the Paper API.
API for advancements.
 
API for fluids and their data.
Classes relevant to pot blocks.
Brigadier connection API.
Arguments.
This package contains events related to player connections, such as joining and leaving the server.
 
Item data components, representing its runtime counterpart as a version-specific data-focused type.
 
This package contains classes and interfaces related to the dialog system in Paper.
 
Point of interest (POI) API.
 
 
 
 
Events relating to the server.
Events relating to worlds.
 
Package containing maths-related API, including position API.
Persistent data container API.
 
Ray tracing API.
 
Collection of registry entry types that may be created or modified via the RegistryEvent.
This package contains events related to the Paper registry system.
 
 
This package contains the API for registry sets in Paper.
Registry tag API.
 
 
Feature flag API.
The root package of the Bukkit API, contains generalized API classes.
Classes relevant to advancements.
Classes relevant to attributes.
Classes relevant to bans.
Classes used to manipulate the voxels in a world, including special states.
Classes relevant to banner blocks.
Generalized BlockData classes.
Specific BlockData classes relevant to only a given block or set of blocks.
Classes concerning the creation of boss bars that appear at the top of the player's screen.
Classes relating to handling specialized non-chat player input.
Classes dedicated to handling a plugin's runtime configuration.
Classes dedicated to facilitate direct player-to-plugin communication.
Classes concerning damage types and sources applicable to living entities.
Classes relating to the specialized enhancements to item stacks, as part of the meta data.
Interfaces for non-voxel objects that can exist in a world, including all players, monsters, projectiles, etc.
Interfaces for various Boat types.
Classes concerning an entity's persistent memory.
Interfaces for various Minecart types.
Events relating to when a block is changed or interacts with the world.
Events relating to entities, excluding some directly referencing some more specific entity types.
Events relating to inventory manipulation.
Events relating to players.
Events related to raids.
Events relating to programmatic state changes on the server.
Events relating to weather.
Events triggered by various world states or changes.
Classes to facilitate world generation implementation.
Classes to facilitate world Structure generation.
Classes involved in manipulating player inventories and item interactions.
The interfaces used when manipulating extra data can can be stored inside item stacks.
Isolated components which may form part of item meta.
Classes that allow attaching custom data to items.
Armor trim meta types.
A Package that contains builders for building InventoryViews.
Classes relevant to loot table manipulation and generation.
Classes to facilitate plugin handling of map displays.
Classes that represents various voxel types and states.
Classes that allow attaching persistent data to various objects.
Classes specifically relating to loading software modules at runtime.
Classes for handling plugins written in java.
Classes to represent various potion properties and manipulation.
Interfaces used to manage the client side score display system.
Classes related to creating or using structures without creating Structure blocks in the world.
Vanilla tags for registries that are not covered by Tag itself.
Multi and single purpose classes to facilitate various programmatic concepts.
Classes dedicated to facilitating deterministic noise.
Spigot-specific player events.