CINDER SDK • API REFERENCE
One API.
Many versions.
Cinder's stable creator API is deliberately smaller than the internal runtime. Interfaces are documented as they are implemented and verified, with Cinder Nexus handling supported version differences underneath.
SDK 1.0.0 • API 1 • ABI 1API AREAS
Build on the contract, not the implementation.
Runtime
Runtime identity, SDK version, capabilities, lifecycle, and verified environment information.
Player
The initial semantic player surface: identity, position, rotation, dimension, health, game mode, inventory, and availability.
Events
Core event primitives are available internally; the versioned creator event contract is being hardened before promotion.
Resources
Resource identifiers and core resource abstractions are being prepared for the stable creator surface.
Minecraft
World, Entity, Block, Item, Inventory, and Command APIs are planned and will be promoted only after verified Nexus mappings.
Networking
Networking APIs are planned for a later SDK milestone and are not yet presented as stable.
VERSION INDEPENDENCE
The implementation can move. Your API target should not.
Cinder's API contract hides Minecraft's internal changes behind semantic creator-facing interfaces.
Cinder Nexus provides the compatibility technology behind those interfaces. Native addresses, layouts, signatures, and other implementation details remain inside Runtime/Nexus.
When a mapping cannot be verified, the API fails closed instead of returning plausible but unverified state.
BUILD WITH US
Every new API must earn stability.
Follow the repository for implementation, verification, examples, and new semantic API promotions.
View Cinder on GitHub