← Creator SDK

CINDER SDK • GETTING STARTED

Your first
Cinder mod.

A future-proof creator workflow starts with one target: the Cinder API. Cinder Nexus and the runtime handle the Minecraft-specific details underneath.

SDK 1.0.0 • WINDOWS X64

THE WORKFLOW

Four steps from idea to mod.

01

Install Cinder

Install a Cinder runtime build and the Cinder Creator SDK when the public package is available.

02

Create a project

Start from a Cinder mod template and target the versioned Creator SDK contract.

03

Build against Cinder

Use cinder/cinder.hpp and semantic APIs instead of binding directly to changing Minecraft internals.

04

Test across versions

Use Cinder Nexus and the verification suite to validate behavior across supported Minecraft environments.

THE CONTRACT

Your mod targets Cinder. Nexus targets Minecraft.

Cinder SDK 1.0.0 establishes API version 1 and ABI version 1. Creator code should include the public Cinder headers rather than depending on Runtime implementation headers.

Cinder Nexus provides the compatibility technology between the stable Cinder API and supported Minecraft implementations. Unverified runtime state is unavailable rather than guessed.

The mod manifest schema is documented in the repository and is part of the launch contract.

NEXT

Explore the verified API surface.

The API reference grows alongside Runtime and Nexus. An API is promoted to stable documentation only after its underlying implementation is tested and verified.

View API Reference