zay-es-debug

Diagnose Zay-ES EntitySet update failures and memory leaks in JMonkeyEngine projects.

25|5|Updated Apr 22, 2017
One-click install
npx skills add https://github.com/assofohdz/subspace-infinity --skill zay-es-debug
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: zay-es-debug
Source: https://github.com/assofohdz/subspace-infinity/tree/main/.claude/skills/zay-es-debug
Command: npx skills add https://github.com/assofohdz/subspace-infinity --skill zay-es-debug

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill addresses common pain points for Java developers using the Zay-ES Entity-Component-System library in JMonkeyEngine projects, including EntitySets that fail to update, memory leaks from unreleased entity resources, component query mismatches, and concurrent modification crashes during entity processing.

Core Features & Use Cases

  • EntitySet Troubleshooting: Step-by-step checks to resolve issues where added entities do not appear in EntitySet results, including verifying applyChanges() calls and correct component queries.
  • Memory Leak Prevention: Identifies unreleased EntitySets as the root cause of growing memory usage and out-of-memory errors in long-running ECS applications.
  • Official Pattern Guidance: Provides vetted Zay-ES best practices including the visualization pattern for syncing entities to visual objects, the decay pattern for time-based entity removal, and correct component mutation workflows to avoid conflicting writes.
  • Use Case: If you are developing a Subspace Infinity server or JMonkeyEngine game and your ship entities are not rendering, or your server crashes with ConcurrentModificationException when processing entity updates, this Skill walks you through the root cause and verified fix.

Quick Start

Use the zay-es-debug skill to diagnose why your Zay-ES EntitySet is not reflecting newly added entities and get the correct fix for your ECS workflow.

Frequently Asked Questions about zay-es-debug

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

FAQPage Schema
Why is my Zay-ES EntitySet not showing newly added entities?

EntitySet update failures in Zay-ES usually stem from missing applyChanges() calls or incorrect component query definitions. This Skill provides step-by-step checks to verify your query parameters and ensure your ECS workflow properly syncs added entities into the active EntitySet results.

How do I fix memory leaks in a JMonkeyEngine game using Zay-ES?

Memory leaks in Zay-ES are typically caused by unreleased EntitySets that accumulate resources over time. This Skill identifies unreleased entity sets as the root cause of growing memory usage and provides the correct release patterns to prevent out-of-memory errors in long-running game applications.

What causes ConcurrentModificationException during Zay-ES entity processing?

ConcurrentModificationException crashes during Zay-ES entity processing are caused by incorrect component mutation patterns and conflicting writes. This Skill walks you through the correct entity mutation workflows and change-entity patterns to avoid thread safety issues in your Java game server.

How does the Zay-ES visualization pattern work for syncing game entities?

The Zay-ES visualization pattern syncs ECS entities to visual objects by mapping component state changes to scene graph updates. This Skill provides vetted best practice guidance for implementing this pattern correctly in JMonkeyEngine projects to ensure ship entities render properly.

Can I use this Skill to debug a Subspace Infinity server with Zay-ES?

Yes, this Skill applies directly to Subspace Infinity server development and other JMonkeyEngine-based Java projects using Zay-ES. It addresses the specific ECS operational bugs encountered in server workflows, including entity rendering failures and concurrent modification crashes during entity updates.

When should I use the decay pattern in Zay-ES entity management?

The decay pattern in Zay-ES is used for time-based entity removal, allowing entities to expire automatically after a defined duration. This Skill provides official best practice guidance for implementing decay and correct component mutation workflows to manage entity lifecycles without conflicting writes.