-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Easy Model Entities lets you use Blockbench models as Minecraft entities and block entities without writing a custom renderer, registry setup, or animation pipeline for every common case.
- Pack Usage: for resource pack and data pack authors who do not want to write Java code.
- Demo Commands: built-in demo entities and the demo block entity.
- Entities: for moving models with entity behavior.
- Block Entities: for fixed models at block positions.
- Blockbench Plugin: WIP notes for the planned exporter workflow.
- Developer Integration: for mods that use EME as a render and profile system.
- Profile Reference: fields, presets, animation modes, and file paths.
Use an entity when the model needs to stand as an entity, look at players, stroll on the ground, use pathfinding goals, or run other entity logic. Entities are flexible, but they cost more runtime because Minecraft tracks and ticks them like normal entities.
Use a block entity when the model stays at one block position. This is usually the better fit for decorations, mimics, shrines, machines, statues, displays, and other fixed models. Block entities are cheaper for those cases, but they do not walk through the world like mobs.
Pack authors put server profiles into the data pack and render profiles, Blockbench models, and textures into the resource pack. Most fields have preset defaults, so small profiles are enough for common cases. After that, profiles can be checked, entities can be summoned, and block entities can be placed with commands.
Mod developers can connect their own entities or block entities to EME by
implementing EasyModelRenderable and using the public render delegates. Simple
automatic animation modes such as automatic and random_idle are available,
and Java code can add or replace transforms per model part.