Skip to content
DaisyCore

DaisyCore

DaisyCore

Section titled “DaisyCore”
One Mega Paper Library

The premium Kotlin-first toolkit for Paper plugins that want one dependency, one platform owner, and zero library sprawl.

DaisyCore brings commands, menus, sidebars, tablists, placeholders, items, and runtime ownership together so your plugin stack feels coherent instead of stitched together.

dependencies {
    implementation("cat.daisy:DaisyCore:1.0.0")
}
Start HereRead the API
One dependencyInstall DaisyCore once and bootstrap only the systems your plugin needs.
Auto-loaded commandsProviders are discovered at startup through DaisyPlatform.
Shared runtimeMenus, sidebars, tablists, and placeholders follow one lifecycle model.
Paper + Kotlin firstModern APIs without exposing the internal module sprawl.

What DaisyCore includes

Section titled “What DaisyCore includes”

Commands

Auto-loaded providers, Kotlin DSL builders, and one command bootstrap path through DaisyPlatform.

Menus

Immutable menu definitions with session-based runtime handling, inventory safety, and refresh support.

Scoreboards

Sidebar-first sessions with keyed lines, invalidate-by-key updates, and clean platform ownership.

Tablists

Header and footer rendering with per-player sessions and a simple baseline API that stays honest.

Placeholders

A shared placeholder registry so menus, sidebars, tablists, and messages can resolve viewer-aware values consistently.

Items

Reusable item builders that keep Adventure text and inventory rendering code cleaner across the platform.

Why DaisyCore

Section titled “Why DaisyCore”

One dependency, shared foundations, cleaner plugin code

DaisyCore is designed so normal plugin projects depend on one thing. Internally, the repo stays modular. Publicly, your plugin code gets one bootstrap path, one text model, one placeholder system, and one family of Daisy-branded types.

Start here

Section titled “Start here”
1

Install

Add DaisyCore to a Paper plugin project.

2

Bootstrap

Create a DaisyPlatform and own your plugin lifecycle cleanly.

3

First Command

Define an auto-loaded command provider and let DaisyCore discover it.

4

Build the Full Flow

Connect a command, menu, sidebar, and tablist in one small plugin feature.

Current status

Section titled “Current status”

Current command discovery: DaisyCore currently scans your plugin jar for @DaisyCommandSet providers at startup.

Scoreboards and tablists: both are production baseline systems. They are meant to be usable now, while leaving room for deeper transports later.

Where to go next

Section titled “Where to go next”