MineRender V2 reference

Find API signatures, options, and the behavior shared across MineRender features. The reference complements the website's live examples with details about rendering, resource ownership, and platform support.

Find a feature

Start with the main API for the content you want to render. Related options and types appear beside it in the navigation.

Feature	Main APIs
Rendering and scenes	Renderer, RendererOptions, MineRenderScene
Player skins and capes	Skins, SkinObject, SkinObjectOptions
Blocks and item models	Models, BlockStates, ModelObject, BlockObject
Entities and animation	Entities, EntityObject, EntityAnimation
Worlds and file formats	MineRenderWorld, StructureParser, SchematicParser, AnvilParser
GUI layers and recipes	GuiObject, GuiLayer, GuiHelper
Assets and resource packs	AssetKey, AssetLoader, HostedAssetSource, ArchiveAssetSource
Images and model exports	Renderer, SceneExporter, SceneGLTFExportOptions

Shared behavior

Core concepts explains coordinate units, asynchronous initialization, redraws, and cleanup. Read it when a change does not appear on screen or when several objects share rendering resources.

Browser and Node.js explains package imports and which capabilities each environment provides. Node package support does not include a headless WebGL renderer.

Reading the API

Feature groups keep classes with their options and supporting types. Use search to find an exact symbol or method name.

Many scene objects extend three.js classes. MineRender adds asset loading, named parts, dirty notifications, and instance handling; direct changes to inherited three.js properties still follow the redraw rules.