boss-spawning

Diagnose and fix Boss spawn rule blockers in Spigot/Paper server setups.

Updated Feb 15, 2026
One-click install
npx skills add https://github.com/kangarko/ai-support --skill boss-spawning
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: boss-spawning
Source: https://github.com/kangarko/ai-support/tree/main/projects/boss/skills/spawning
Command: npx skills add https://github.com/kangarko/ai-support --skill boss-spawning

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps identify and resolve why Bosses fail to spawn according to configured rules in the Boss plugin, reducing downtime and manual debugging.

Core Features & Use Cases

  • Diagnostic Flow: steps to enable debugging and validate common blockers (distance, timing, conditions).
  • Configuration Guidance: checks related to settings.yml and platform notes to avoid ignored spawns.
  • Use Case: A server administrator uses this Skill to troubleshoot a Boss not spawning despite correct conditions, then applies a fix and observes spawns resume.

Quick Start

Follow the diagnostic flow to verify spawn conditions and apply fixes.

Frequently Asked Questions about boss-spawning

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

FAQPage Schema
Why is my Minecraft Boss not spawning despite correct conditions in settings.yml?

Bosses fail to spawn when distance checks, timing windows, or condition matches block the spawn rules in settings.yml. This Skill identifies those exact blockers on Spigot/Paper servers to help you apply fixes and resume spawning.

How do I troubleshoot Boss spawn rules on a Paper server?

Troubleshoot Boss spawn rules by running a diagnostic flow that validates distance checks, timing windows, and condition matches against your settings.yml. This enforces proper interpretation of spawn rules on your Spigot/Paper server to resolve configuration issues.

What are common blockers preventing custom Bosses from spawning in Minecraft?

Common blockers preventing Bosses from spawning include failed distance checks, narrow timing windows, unmet condition matches, and incorrect settings.yml references. Identifying these spawn rule constraints resolves ignored spawn attempts on your server.

Does this Boss spawn diagnostic process work for both Spigot and Paper platforms?

Yes, the diagnostic process applies to server setups using Spigot or Paper with custom settings. It addresses platform-specific notes and enforces correct settings.yml references to ensure reliable Boss spawning behavior across both server platforms.

How do I fix ignored Boss spawn attempts in my plugin configuration?

Fix ignored Boss spawn attempts by verifying spawn conditions, correcting settings.yml references, and applying platform-specific notes for your Spigot/Paper server. This enforces proper interpretation of your configured spawn rules to restore behavior.