neoforge

Define Kotlin-first NeoForge modding conventions for entrypoints, registrations, and data components.

Updated Mar 31, 2026
One-click install
npx skills add https://github.com/dotBeeps/pantry --skill neoforge
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: neoforge
Source: https://github.com/dotBeeps/pantry/tree/main/morsels/skills/neoforge
Command: npx skills add https://github.com/dotBeeps/pantry --skill neoforge

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

NeoForge modding projects often suffer from inconsistent setup and fragmented conventions. This Skill provides a single, Kotlin-first set of guidelines for entrypoints, event registration, data components, and build scripts to streamline mod development.

Core Features & Use Cases

  • Kotlin-first entrypoints and Forge mod structure with Kotlin DSL build scripts
  • Standardized registration patterns (DeferredRegister, data components, codecs)
  • Clear guidance for event handling, data persistence, and cross-dimension compatibility
  • Use case: teams can onboard quickly by following a unified convention across mods

Quick Start

Initialize a NeoForge Kotlin-first mod project using these conventions.

Frequently Asked Questions about neoforge

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

FAQPage Schema
How do I set up a Kotlin-first NeoForge mod project with consistent conventions?

Use a Kotlin-first NeoForge modding convention to standardize entrypoints, registrations, and data components. It provides unified guidelines for Kotlin DSL build scripts, standardized entrypoints, and DeferredRegister usage across your mod projects.

What is the best way to handle DeferredRegister and data component registration in NeoForge Kotlin mods?

Standardized registration patterns for NeoForge Kotlin mods use DeferredRegister and codecs to manage data components. This approach ensures consistent data serialization and registration pipelines across your Kotlin-based DSL projects.

Can I use Kotlin DSL build scripts for NeoForge modding?

Yes, Kotlin DSL build scripts are supported as part of the Kotlin-first NeoForge modding conventions. These conventions apply to Forge mods built with Kotlin-based DSLs, streamlining your build automation and project structure.

How do I standardize event handling and data persistence across NeoForge projects?

Apply Kotlin-first NeoForge conventions to standardize event handling, data persistence, and cross-dimension compatibility. This provides clear guidance for consistent mod entrypoints and data serialization across all your NeoForge projects.

Does NeoForge support Kotlin-first entrypoints and data component pipelines?

NeoForge supports Kotlin-first entrypoints and data component pipelines through these standardized conventions. They satisfy requirements for consistent mod entrypoints, event handling, and data serialization specifically for Kotlin-based Forge mods.

Why do NeoForge modding projects need standardized conventions for Kotlin development?

NeoForge modding projects often suffer from inconsistent setup and fragmented conventions. Applying a Kotlin-first set of guidelines for entrypoints, event registration, and data components streamlines development and helps teams onboard quickly.