Tags
Creators
Details
1.1.0
Compatibility
Changes
v1.1.0 — Major Rewrite & Feature Expansion
This update completely transforms CuriosPaper into a full in-game custom item creation framework — no more manual configs, no more external editors. Everything can now be created, edited, and managed directly inside the game.
⭐ Major Additions
✔ Full In-Game Custom Item Editor
A complete GUI-driven system for creating and editing custom items:
- Set name, material, slot type, model
- Edit lore
- Real-time item previews
- Save or cancel changes safely
✔ New Data Systems
New modular data models powering the editor:
- ItemData – Core container for everything about a custom item
- RecipeData – Shaped & shapeless recipes
- LootTableData – Chest loot integration
- MobDropData – Entity drop configuration
- VillagerTradeData – Profession & level-based trading
- AbilityData – Triggers & effects for equipped items
⭐ New Editors / GUIs
Item Editing System
- EditGUI — Central editor hub
- RecipeEditorGUI — Drag-and-drop recipe builder
- LootTableBrowser — Browse, add, and configure loot sources
- MobDropEditor — Configure drops for every entity type
- TradeEditor — Build villager trades with full control
- AbilityEditorGUI — Add potion effects or attribute modifiers with EQUIP/UNEQUIP/WHILE_EQUIPPED triggers
⭐ New Gameplay Systems
Ability System
Items can now apply:
- Potion effects
- Attribute modifiers (health, armor, speed, etc.)
Full trigger support:
- EQUIP
- DE_EQUIP
- WHILE_EQUIPPED (auto-refreshing every second)
Loot Table Injection
- Works with all vanilla & custom tables
- Smart matching ("dungeon" → all dungeon loot)
- Fully configurable chance & amount
Mob Drop System
- Supports all mobs
- Chance, min/max amounts
- Looting enchantment support
Villager Trade System
- Profession & level filtering
- Wandering trader support
- 1–2 cost items
- Prevents duplicate trades
⭐ API Expansion
CuriosPaperAPI now includes:
Item Management
getItemData(id)createItem(id)saveItemData(id)deleteItem(id)
Integration Registration
registerItemReciperegisterItemLootTableregisterItemMobDropregisterItemVillagerTrade
Accessory Utilities
- Tagging & validation for accessory slot types
⭐ Improved Infrastructure
- Better error handling & validation
- Improved CustomModelData + NamespacedKey model support
- Cleanup tasks on plugin shutdown
- New event listeners for abilities, recipes, mob drops, trades
🐛 Fixes & Stability Improvements
- More reliable accessory slot tagging
- Fixed duplicate registrations for trades/drops/loot
- Better debug logging across all systems
- File saving/loading is now far more robust
📁 File System Changes
- All custom items now stored cleanly in
/items/ - Automatic serialization via YAML
- No breaking changes — older setups continue to work
Supplementary resources
| File | Type | Size | |
|---|---|---|---|
| Readme for devs.zip | Unknown | 11.1 KiB |
Projects on Modrinth are automatically available through a Maven repository for use with JVM build tools such as Gradle. To learn more about the Modrinth Maven API, click here.
Note: When available, you should use the creator's maven repo instead as it will have transitive dependency information that the Modrinth Maven API does not. You may also end up with duplicate dependencies if you use a mix of Modrinth and non-Modrinth Maven repositories for your dependencies, because the group identifier will be different when served through the Modrinth Maven API.
Maven coordinates:
Version ID:
build.gradle:
repositories {
exclusiveContent {
forRepository {
maven {
name = "Modrinth"
url = "https://api.modrinth.com/maven"
}
}
// forRepositories(fg.repository) // Uncomment when using ForgeGradle
filter {
includeGroup "maven.modrinth"
}
}
}
// Standard Gradle dependency
dependencies {
implementation "maven.modrinth:JLMPHrRw:TSkXhGd2"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:JLMPHrRw:TSkXhGd2"
}

