DaisyCore

DaisyCore

Stable release contract

DaisyCore 0.1.0 is the first stable release. Install only cat.daisy:DaisyCore, bootstrap through DaisyPlatform.create(…), close it in onDisable(), and treat tablists as header/footer-only in this line.

Runtime Platform

DaisyCore is the runtime platform for modern Paper features that should feel like one coherent system.

Use DaisyCore when one feature spans commands, menus, sidebars, tablists, text, placeholders, items, and one lifecycle owner instead of a pile of local glue.

Install DaisyCore Build a Plugin Flow

One runtime ownerDaisyPlatform is the normal bootstrap path and owns service startup and cleanup in one place.

MiniMessage firstUse direct MiniMessage strings for feature-local UI and replies by default, then move to shared text later.

UI systems togetherCommands, menus, sidebars, and tablists share one Kotlin-first API language.

Config-friendly laterUse shared text and messages(…) only when the plugin is genuinely config-heavy.

Selective runtime scopeDaisyCore grows where repeated runtime flows benefit from one platform owner, not where extra helpers merely make the feature list longer.

Where DaisyCore is strongest

Commands

Auto-loaded command groups, clean executor helpers, and startup-time availability control.

Menus

Inline-first menu flows, viewer-aware items, and lightweight click handling.

Sidebars

Keyed lines and stable session ownership for scoreboard-style UI.

Tablists

Header/footer rendering with explicit lifecycle cleanup. Richer tab entry formatting is intentionally out of scope for 0.1.0.

What DaisyCore will not do

• own typed config lifecycle or migrations
• own parser or canonical-value rules
• add niche runtime systems just to sound broader

DaisyCore is meant to be the clean runtime owner for repeated plugin flows, not the place every adjacent helper gets pushed into.

Related Product

Pair DaisySeries with DaisyCore when parsing enters the same feature

Keep canonical values and alias handling in DaisySeries instead of leaking parser glue into runtime files.

Open DaisySeries docs

Related Product

Pair DaisyConfig with DaisyCore when text and YAML need ownership

DaisyConfig stores typed text and config state. DaisyCore still renders and owns the runtime UI.

Open DaisyConfig docs

Best first path

1

Install and bootstrap DaisyCore

Start with Install DaisyCore and then move directly to First Plugin.

2

Build one believable runtime flow

Use Build a Plugin Flow before reading APIs in isolation. That is the fastest way to understand the actual runtime value of DaisyCore.

3

Go deeper by system and API

Move from guides into Bootstrap API, Command DSL, and the rest of the runtime references.

Quick links

• Start here: Install DaisyCore
• Main guide: Build a Plugin Flow
• Reference: Bootstrap API