Tags
Creators
Details
All versions
1.0.2
Alpha
RecipeAdvanced 1.0.2last month 20
Compatibility
Minecraft: Java Edition
26.1.2
Platforms
Paper
Purpur
Changes
Added
- Languages. Every line of text now lives in
lang/<code>.yml: menus, commands, station names, the/ra verifyreport. English and Russian are complete; Ukrainian, German and Spanish cover the player-facing screens and fall back to English elsewhere. Pick one withlanguage:inconfig.yml. - Other plugins' recipes are opt in.
/ra ext list,/ra ext add <namespace> [folder],/ra ext all [folder],/ra ext folder,/ra ext remove— nothing from another plugin appears in/recipesuntil you publish it, and it goes in the folders you name. /ra langreports the active language and names any line that failed to load.
Changed
- A fresh install no longer ships with a demo recipe, three workbenches and three folders. What belongs in a server's recipe book is the owner's call.
Fixed
- The anvil would not hand over a result that costs nothing: vanilla refuses to release a result at zero levels, so recipes with no experience cost drew the item and did nothing on click.
- The brewing stand would not accept a custom ingredient at all — its slots vet what goes in. Placement is now done by the plugin for items a recipe names, and a recipe describes one ingredient and one bottle, applied to every bottle in the stand, as vanilla brews.
- Eighty three menu lines showed "Missing message": a dot in a key was read as
a path separator, so
editor.xpandeditor.xp.furnacecould not coexist. - The editor's navigation column was invisible — closed pages were grey panes on a black pane background. Each page now keeps its own icon.
- Page names never changed language, having been resolved once before the language files were read.
- Recipes for the 4x4/5x5/6x6 workbenches, copied from a full-edition server, quietly became ordinary furnace recipes.
- In
/recipes, every folder printed "click to open" twice. - The furnace and cauldron slot labels were never translated.
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:r4tda2MU:hplRdiYb"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:r4tda2MU:hplRdiYb"
}

