Some Ideas for CraftBooks Custom Drops Mechanic
Nessuno ha ancora preso questa issue.
Valutazione
- Difficoltà
- 5/5
- Tempo stimato
- Più di una settimana
- Idoneità per principianti
- 12/100
Direzione di ricerca
This is a broad wishlist of several features with no named files, tests or entry points, so there is no clear starting point in the payload. Before writing code, a newcomer would need to find where CraftBook currently defines custom drops and read the existing configuration, then ask a maintainer which items to take on. Done would mean one scoped piece, agreed on in the thread, rather than the whole list.
Scritto dal modello di indicizzazione a partire dal testo della issue.
Descrizione
The Problem
Currently, CraftBook's custom drops and block/mob handling are relatively basic and lack support for advanced conditional logic, dynamic item modifications, and event-driven mechanics.
Specifically, server owners cannot implement many common survival and RPG features through CraftBook alone, such as:
- Entity State Conditions: Checking environmental or biological states (e.g., whether a mob is burning when it dies, or checking if a goat still has its horns).
- Tag-Based & Dynamic Drops: Pulling random items dynamically from Minecraft item/block tags (e.g., loot pools based on
#minecraft:fishesor#minecraft:ice). - Dynamic Item Properties & NBT: Setting custom durability/damage values on dropped weapons (like an Illusioner dropping a bow with a random durability loss), custom model data, or dynamic lore (e.g., player skulls displaying the killer's name and timestamp).
- Tool-Tier Restrictions & Event Cancellation: Preventing players from breaking blocks if their tool tier is too low (e.g., requiring a diamond pickaxe) and canceling the break event.
- Tool-Break Triggers: Handling drops when a tool or weapon actually breaks (
on tool break), allowing players to salvage materials (like getting a stick or nuggets from a broken tool). - Player-Specific Event Rewards: Creating custom PvP trophies like player heads with dynamic killer and date information.
A Solution
Expand CraftBook's configuration system to support more advanced gameplay hooks:
- Conditional Drop Rules: Add options for entity states (e.g.,
is-burning: true) and tag-based drop pools. - Item Customization in Config: Support for Custom Model Data, dynamic durability, and placeholder-based lore (e.g.,
%attacker%,%date%) within drop definitions. - Tool & Break Control: Optional block-protection rules based on tool tiers directly within CraftBook configurations.
- Tool-Break Mechanics: A configuration section for item breakage drops (rewarding players with crafting components when tools break).
Alternatives
Currently, server admins are forced to use separate heavy scripting plugins (like Skript) alongside CraftBook just to handle basic customized survival mechanics, tool-tier progression, and conditional mob drops, which leads to fragmented configurations and plugin bloat.
Anything Else?
General use cases where these features would be extremely valuable:
- RPG & Hardcore Survival Servers: Enforcing tool progression (e.g., restricting ore mining based on pickaxe tiers) and introducing environmental risks (e.g., taking damage when breaking glass with bare hands).
- Immersion & Economy (Salvaging): Rewarding players with scrap materials when their tools or weapons break (e.g., iron/gold nuggets from metal tools, string from bows) to create a more integrated recycling loop.
- Environmental Interactivity: Rewarding players with cooked meat if a mob dies while burning, or rare drops only under specific conditions.
- PvP Trophies: Customizing player head drops to act as memorial items or bounties with dynamic killer tags and timestamps.
- Lingua principale
- Java
- Stelle
- 323
- Fork
- 164
- Metriche di merge delle PR
- Nessuna PR unita negli ultimi 30g
Preparare l'ambiente
- Nessun Dockerfile né file Docker Compose
- Nessun modello di pull request
- Leggi la guida per i contributori
Come iniziare
- Leggi tutta la issue e poi la guida ai contributi del progetto.
- Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
- Fai un fork del repository e lavora su un branch.
- Apri una pull request che faccia riferimento al numero della issue.
Altre issue di EngineHub/CraftBook
-
status:pending type:bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 75/100
-
status:pending type:bug
Difficoltà 2/5 1-3 ore Idoneità per principianti 70/100
-
status:pending type:bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 58/100
-
status:pending type:bug
Difficoltà 3/5 1-2 giorni Idoneità per principianti 62/100
-
status:pending type:bug
Difficoltà 4/5 3-5 giorni Idoneità per principianti 35/100
Tutte le issue di EngineHub/CraftBook
Issue simili
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
-
bug level:trivial
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
exoego/keycloak-fuhito#666 ·
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 72/100
ant-media/Ant-Media-Server#8185 ·
I maintainer di solito rispondono entro 4 giorni
-
desktop grp:about type:graphics-bug ui-public
Difficoltà 1/5 Meno di un'ora Idoneità per principianti 68/100
I maintainer di solito rispondono entro 1 giorno
-
Difficoltà 2/5 1-3 ore Idoneità per principianti 77/100
I maintainer di solito rispondono entro 1 giorno