Changelog
Elevador Update – New Recipe Creation GUI

/elevador recipe
A brand new recipe creation interface has been added to Elevador, making custom recipe setup much easier, faster, and far more comfortable for administrators.

This new system was designed to give server staff full control over how elevator recipes are created, edited, and expanded, all through a much more intuitive GUI.

What’s included in the new recipe GUI:

• Create and edit recipes directly from an admin-friendly interface
  
  
• Support for Shaped and Shapeless recipes
  
  
• Support for exact recipes and non-exact recipes
  
  
• Choose the result item of the recipe
  
  
• Set the result amount
  
  
• Create recipes that result in either:
  
  • custom elevator parts
  • or the final elevator
• Choose the color of the final elevator
  
  
• Rename custom parts and recipe results
  
  
• Much easier workflow for adding more elevator recipes without messy manual setup
  

This means administrators can now build full elevator crafting chains in a much cleaner way, including custom parts, exact ingredient costs, different recipe styles, custom outputs, and colored final elevators.

On top of that, the entire system remains fully compatible with:

• Folia
• Paper
• Spigot

This update makes the plugin much more powerful while keeping recipe management simple, practical, and flexible for server owners and staff.

Elevator Essentials — Advanced Crafting Guide
The plugin allows you to create custom crafting trees using external ingredients or intermediate components. This enables configurations such as:

• A + B = C
  
  
• D + E = F
  
  
• C + F = ELEVATOR
  

Administrators can use vanilla items or items from other plugins (ItemsAdder, Oraxen, CustomCraft, etc.) without needing to depend on their specific APIs.

Step 1 — Register External Ingredients
Hold the item in your hand and use the following command:

• /elevador item set A
  
  
• /elevador item set B
  
  
• /elevador item set D
  
  
• /elevador item set E
  

This saves the complete ItemStack into the configuration under: parts_crafting.external_items

Automatically generated example:

YAML
external_items:
a:
id: minecraft:iron_block
b:
id: minecraft:redstone_block
d:
id: minecraft:redstone_torch
e:
id: minecraft iston

These items are then referenced as: ext:A, ext:B, ext , ext:E.

Step 2 — Define Internal Parts
Parts are items created by the plugin that serve as intermediate components. Example:

YAML
parts:
C:
material: SMOOTH_STONE
name_fallback: "&eElevator Part C"

F:
material: IRON_PRESSURE_PLATE
name_fallback: "&eElevator Part F"

These are referenced as: part:C, part:F.

Step 3 — Define Recipes
Recipes function as logical blocks. Basic Example:

YAML
recipes:
part_c:
type: shapeless
result:
type: part
id: C
ingredients:
- ext:A
- ext:B

part_f:
type: shapeless
result:
type: part
id: F
ingredients:
- ext
- ext:E

elevator_final:
type: shapeless
result:
type: elevator
ingredients:
- part:C
- part:F

Final Result:

A + B → C | D + E → F | C + F → ELEVATOR

Creating Larger Tech Trees
Yes, you can create as many steps as you like. Complex Example (Double the steps):

1. A + B = C
   
   
2. D + E = F
   
   
3. C + F = G
   
   
4. G + A = H
   
   
5. H + F = ELEVATOR
   

Configuration:

YAML
parts:
C:
material: SMOOTH_STONE
F:
material: IRON_PRESSURE_PLATE
G:
material: POLISHED_ANDESITE
H:
material: OBSERVER

recipes:
part_c:
type: shapeless
result: { type: part, id: C }
ingredients: [ext:A, ext:B]

part_f:
type: shapeless
result: { type: part, id: F }
ingredients: [ext , ext:E]

part_g:
type: shapeless
result: { type: part, id: G }
ingredients: [part:C, part:F]

part_h:
type: shapeless
result: { type: part, id: H }
ingredients: [part:G, ext:A]

elevator_final:
type: shapeless
result: { type: elevator }
ingredients: [part:H, part:F]