OBSIDREL / DOCS

Documentation

Guides, tutorials and technical references for the Obsidrel ecosystem.

DocumentationCustom entities: vanilla body and custom visual model

Custom entities: vanilla body and custom visual model

Obsidrel uses a Minecraft body for collision/AI and may render a separate resource-pack model. Definitions live in plugins/Obsidrel/resources/entities/. Validate a small body first, before rigs/animations.

Basic — vanilla body and attributes

A reduced configuration using the actual Obsidian Golem Showcase model (requires its bundled JSONs and PNGs). The Core requires model.path and model.texture; otherwise the definition is rejected:

yaml
simple_guard:
  name: '<aqua>Guardian</aqua>'
  body:
    type: WITHER_SKELETON
    visible: false
    ai: true
    persistent: true
  model:
    material: PAPER
    path: obsidrel:entity/showcase/obsidian_golem
    parent: obsidrel:entity/showcase/obsidian_golem_geometry
    texture: obsidrel:item/entity/showcase/obsidian_golem
  attributes:
    max-health: 40.0
    attack-damage: 5.0
    movement-speed: 0.22

This tests loading and attributes without authoring your own JSON, but depends on the actual Showcase visuals. For another model, update model.path, model.texture and the matching assets; do not omit model.

Advanced — official Obsidian Golem Showcase

The bundled showcase_obsidian_golem in resources/showcase/entities/entities.yml includes invisible WITHER_SKELETON body, custom attributes, model obsidrel:entity/showcase/obsidian_golem, texture obsidrel:item/entity/showcase/obsidian_golem, ground movement, skeletal rig, bones, display meshes, clips and loot.

This spans multiple assets; do not copy one isolated animation block. For a real complete project, keep the full Showcase YAML and matching JSONs/textures under pack/sources/showcase/ or its installed source. Rig bones and parts must use matching identifiers and animation clips target those bone IDs.

Customize safely

  1. Import an authored Blockbench project and keep JSON/PNG keys consistent.
  2. Change one dimension at a time: body.type, model.path, attributes, movement.
  3. Reload, build and deliver the pack when visuals change.
  4. Test spawn, collision, movement, animation, loot and server restart.
  5. Entity actions/conditions require supported event/engine integrations. Do not assume arbitrary Action YAML is accepted in every entity state.

Related: Models/animations, Movement, Actions/Conditions.

Was this article helpful?Loading ratings…

Help us improve Obsidrel documentation. One vote per account and article. Discord AI feedback can also contribute when the answer cites this article.