1.1
Compatibility
Changes
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:
external_items:
a:
id: minecraft:iron_block
b:
id: minecraft:redstone_block
d:
id: minecraft:redstone_torch
e:
id: minecraft:piston
These items are then referenced as: ext:A, ext:B, ext:D, ext:E.
Step 2 — Define Internal Parts
Parts are items created by the plugin that serve as intermediate components. Example:
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:
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:D
- 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):
- A + B = C
- D + E = F
- C + F = G
- G + A = H
- H + F = ELEVATOR
Configuration:
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:D, 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]
Available Ingredient Types
| Type | Prefix | Example |
|---|---|---|
| Vanilla | mat: |
mat:IRON_INGOT, mat:PISTON |
| Captured External Item | ext: |
ext:A, ext:B |
| Internal Parts | part: |
part:C, part:F |
| The Elevator | elevator |
elevator |
Reload Changes
After modifying the config, use:
/elevador reload
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:mh8VXkIk:1OssnPvs"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mh8VXkIk:1OssnPvs"
}

