This module allows API instances to be associated with game objects without specifying how the association is implemented. This is useful when the same API could be implemented more than once or implemented in different ways. See also the package-info.java file.

• What we call an API is any object that can be offered or queried, possibly by different mods, to be used in an agreed-upon manner.
• This module allows flexible retrieving of such APIs, represented by the generic type A, from blocks in the world or from item stacks.
• It also provides building blocks for defining custom ways of retrieving APIs from other game objects.

See the javadoc of BlockApiLookup for a full usage example.

The primary way of querying API instances for blocks in the world. It exposes a find function to retrieve an API instance, and multiple register* functions to register APIs for blocks and block entities.

Instances can be obtained using the get function.

A BlockApiLookup bound to a position and a server world, allowing much faster repeated API queries.

See the javadoc of ItemApiLookup for a full usage example.

The way to query API instances from item stacks. It exposes a find function to retrieve an API instance, and multiple register* functions to register APIs for items.

See the javadoc of EntityApiLookup for a full usage example.

The way to query API instances from entities. Exposes a find function to retrieve an API instance, and multiple register* functions to register APIs for entity types.

The subpackage custom provides helper classes to accelerate implementations of ApiLookups for custom objects, similar to the existing BlockApiLookup, but with different query parameters.

A map meant to be used as the backing storage for custom ApiLookup instances, to implement a custom equivalent of BlockApiLookup#get.

A fast thread-safe copy-on-write map meant to be used as the backing storage for registered providers.