hytale-ecs

Define ECS architecture for Hytale plugins with stores, components, and systems.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/Reign-software/hyforged --skill hytale-ecs-reign-software
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hytale-ecs
Source: https://github.com/Reign-software/hyforged/tree/main/.github/skills/hytale-ecs
Command: npx skills add https://github.com/Reign-software/hyforged --skill hytale-ecs-reign-software

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

The Hytale ECS skill provides a comprehensive reference for building data-driven game logic with Stores, EntityStores, and ChunkStores, enabling consistent component and system design across plugins.

Core Features & Use Cases

  • Core architecture: Store, EntityStore, ChunkStore, Holder, Ref, and pure data Components.
  • Systems and scheduling: EntityTickingSystem, TickingSystem, DelayedEntitySystem, RefChangeSystem, and SystemGroups for deterministic execution.
  • Components and registration: guidelines for creating Entity and Block components, including serialization and registration patterns.
  • Use cases: building per-entity logic, block ticking, and plugin-wide ECS integration.

Quick Start

Create a minimal plugin that defines a new component, registers it with EntityStore, and implements a simple tick-based system to observe changes.

Frequently Asked Questions about hytale-ecs

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is ECS architecture and how does it work for Hytale plugin development?

ECS architecture for Hytale plugin development separates game logic into pure data Components and processing Systems. It structures data using EntityStores and ChunkStores to enable scalable, data-driven behavior across entities and blocks.

How do I structure components and systems in a Hytale plugin?

Structure Hytale plugin components as pure data attached to entities or blocks, then implement logic using EntityTickingSystem or TickingSystem. Register components with EntityStore and schedule systems via SystemGroups for deterministic execution.

When should I use ChunkStore versus EntityStore in Hytale ECS?

Use EntityStore for managing per-entity components and ChunkStore for block-based data and ticking logic. ChunkStore handles spatial block data, while EntityStore tracks individual entity state within your Hytale plugin architecture.

Can I implement delayed execution and deterministic scheduling in Hytale ECS?

Yes, Hytale ECS supports deterministic scheduling through SystemGroups and DelayedEntitySystem. You can orchestrate system execution order and defer entity modifications using command buffers to ensure safe, sequential processing.

What is the best way to register block components for ticking in Hytale?

Register block components by defining pure data structures and attaching them to ChunkStores. Implement a TickingSystem to process these block components, enabling consistent spatial logic and block state updates across chunks.

How do I create a minimal Hytale plugin with a custom ECS component?

Define a new pure data component, register it with an EntityStore, and implement a simple tick-based system. This minimal setup observes component changes and validates your ECS architecture integration within the Hytale plugin.