About Team Mods Releases Docs API gaps FAQ

GitHub Download

Search the docs/

Overview

What Sunrise is, what it can do and who makes it.

What is Sunrise?
What Sunrise can do
How Sunrise is built

FAQ
Contribute

Not an official Minecraft product. Not approved by or associated with Mojang or Microsoft.

Who makes it

Sunrise is made by its team: Umut, Xmilon, Juan Luci, Ari, levzzz, Isloka, Qwerner88880, 5oscow, and Sylviromi, with everyone who contributes. It builds on Horizon (opens in a new tab), founded by Ludovic Marie, and the horizon-rust contributors. This site is made by Umut (opens in a new tab) and Xmilon (opens in a new tab), hosted by Umut (opens in a new tab), and grew out of the Horizon site by Anthony S (opens in a new tab). Reach us on GitHub (opens in a new tab). Sunrise contains no Minecraft code, assets or data, and this site offers no game files: you need your own legally obtained copy of Minecraft: Java Edition. Minecraft is a trademark of Mojang Synergies AB.

Licences

Sunrise's code is under the MIT licence (opens in a new tab), as Horizon's. The fonts are Geist, Geist Mono and Sora, with Bricolage Grotesque on share cards, under the SIL Open Font License (opens in a new tab). Every asset on this site is listed in LEGAL.md.

Privacy

This site sets no cookies for visitors and has no analytics or trackers. Opening a release stores a keyed hash of your IP address, and sharing a performance capture stores the file you upload; downloads come from GitHub, under GitHub's privacy statement (opens in a new tab). The launcher sends nothing unless you allow it: what it can send, and how to delete it (opens in a new tab).

FAQ API gaps Modding team

Made in the open, in Rust.

Español sunrise-org/horizon

About Team Mods Releases Docs API gaps FAQ

GitHub Download

About Team Mods Releases Docs API gaps FAQ

GitHub Download

Search the docs/

Modding

Make a mod: one folder, one .hmod file.

Make a mod: quickstart
How a mod works

Build your first block
Add code to your mod

Modding recipes
Recipes: blocks
Recipes: block entities
Recipes: items
Recipes: mobs and entities
Recipes: crafting and smelting
Recipes: loot tables
Recipes: tags
Recipes: world generation
Recipes: events and hooks
Recipes: commands
Recipes: menus, screens and the HUD
Recipes: sounds and particles
Recipes: networking
Recipes: saved data

Making a content mod
Native mods
Injections
Mixins
Biomes
Building a mod to mod.wasm
Cache reload-stable recipe definitions
Check biome tags
Controlling spawns
Declaring a machine's menu data
Drawing resolved models
Drawing with your own render pipeline
Emitting game events with context
Maths and network NBT
Playing entity keyframe animations
Publishing your mod
Query attachment holders
Read biome data
Reading tags in custom loot evaluation
Register game rule categories
Slowing or boosting entities on a block
Temporary client sound effects

Test a mod
Publish a mod

The manifest and the .hmod file
Blocks, items and data files

What changed in modding
Legacy native mods (.hnmod)
The legacy bundle (.hnmod)
Legacy hook points and helpers

Reference book

Ari’s complete mod API book, copied from arismoko/horizon.

Modding Horizon
Your first native mod
Installing and using mods

Wire types
Trait mods, Parts and attachments
Where the mod API is going
Design: server read tier for handles
Design: vehicle health layout
Design: per-type batched block entity ticks
Design: Source-validated guest point artifact
Design: typed cauldron interactions
Villager professions and trades
Villager profession resources and clients
Design: decide, fire, apply
Design: decide, fire, apply: route inventory
Block entity neighbour changes
Block experience and explosions
Client action pipeline design
Create and Mekanism capabilities
Death sources and weapons at the loot hook
Design: a mod's biomes inside the Overworld and Nether
Design: Attachment query joins
Design: baked models and ModelData
Design: chunk attachment disk hooks
Design: client extensions
Design: custom recipe-book settings
Design: effect added
Design: entity render state
Design: general entity types
Design: inside-block contact shapes
Design: level extracted state
Design: main target configuration
Design: mesh visibility
Design: mod datapack registries
Design: mods extending the mod API
Design: moving structures
Design: multi-block placement
Design: offline players and selection
Design: Part instance state
Design: pending children
Design: per-biome client effects and mod biome registry sync
Design: Read-only typed loot context
Design: resource-backed special item renderers
Design: section geometry
Design: section meshing
Design: snapshot participants
Design: stale handle errors
Design: transactional block-entity removal
Design: travel and move hooks
Design: typed payloads
Design: unified fluid declaration
Design: worldgen features and placers
Farmer's Delight's calls against existing hooks
Generated block class tags
Item abilities
Mod render colour
Observing refused damage attempts
Permission nodes and handlers: proposed design
Saved-world mod mismatches
Structs a mod builds and structs a mod receives
Villager secondary work blocks

NeoForge data files
NeoForge extension methods and Horizon
Mod files
The registry index and .hpack
The mod API (rustdoc)

Where each doc lives
Scoped whole-stack rollback for internals mods

For agents

Docs/Modding/How to do it

The build's warnings

From the modding book of arismoko/horizonbfbda6a

Before it builds, the launcher validates injection declarations and reports their compiled slots in native/build.log. Invalid or stale declarations stop the build; see Injections.

←PreviousClient effect interpolation →NextA mod's own ingredient kinds, matching at craft time

Edit this page on GitHub · Spotted something wrong? Open an issue .