Some Ideas for CraftBooks Custom Drops Mechanic

Ouverte
#1,387 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
12/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
java
Domaine
game-dev

Piste de recherche

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.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

status:pending type:feature-request
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:fishes or #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:

  1. Conditional Drop Rules: Add options for entity states (e.g., is-burning: true) and tag-based drop pools.
  2. Item Customization in Config: Support for Custom Model Data, dynamic durability, and placeholder-based lore (e.g., %attacker%, %date%) within drop definitions.
  3. Tool & Break Control: Optional block-protection rules based on tool tiers directly within CraftBook configurations.
  4. 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.
Langage dominant
Java
Étoiles
323
Forks
164
Métriques de merge des PR
Aucune PR mergée en 30 j

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de EngineHub/CraftBook

Toutes les issues de EngineHub/CraftBook

Issues similaires

Plus d'issues Java

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.