Some Ideas for CraftBooks Custom Drops Mechanic

Aberta
#1,387 0 comentários 0 reações 0 responsáveis Ver no GitHub

Ninguém assumiu esta issue ainda.

Avaliação

Dificuldade
5/5
Tempo estimado
Mais de uma semana
Facilidade para iniciantes
12/100
Tipo de issue
Funcionalidade
Clareza
Precisa de esclarecimento
Status de atividade
Ativa
Stack de tecnologia
java
Domínio
game-dev

Direção de pesquisa

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.

Escrita pelo modelo de indexação a partir do texto da issue.

Descrição

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.
Linguagem predominante
Java
Estrelas
323
Forks
164
Métricas de merge de PRs
Nenhum PR com merge em 30d

Preparar o ambiente

Primeiros passos

  1. Leia a issue inteira e depois o guia de contribuição do projeto.
  2. Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
  3. Faça um fork do repositório e trabalhe em uma branch.
  4. Abra um pull request que referencie o número da issue.

Mais de EngineHub/CraftBook

Todas as issues de EngineHub/CraftBook

Issues semelhantes

Mais issues de Java

Receba novas issues na sua caixa de entrada

Um resumo curto de issues do GitHub para quem está começando.