Tags
Creators
Details
0.3-SEED-1
Compatibility
Changes
Changelog 0.3-SEED-1
๐ฟ Improvements & Configuration Refactor
๐ ๏ธ Complete Configuration Overhaul
๐ File Separation
-
๐ The biome configuration has been reorganized:
-
๐ต Sounds, display types (e.g., title, action bar), and visual effects are now handled directly in the language files:
๐ fr.yml/en.ymlโ manage both translatable texts and immersive effects.
-
๐ A new file
biomes.ymlhas been introduced to manage:- โก Commands to be executed per biome
- โจ Per-biome behavior settings
-
๐ Command Management by Biome
-
๐ฅ Each biome can now trigger one or more custom commands when the player enters or interacts with it, such as:
/title %player% title Welcome to the Jungle/playsound minecraft:ambient.cave %player%/effect give %player% minecraft:speed 5 1 true
-
๐งฉ Supports dynamic placeholders (
%player%,%biome%, etc.)
๐งน Simplified config.yml
-
The
config.ymlfile now contains only global settings:- ๐ General plugin behavior
- โ๏ธ Global toggles and performance options
- ๐ง Default values and fallback settings
๐ Streamlined Language Files
-
fr.yml/en.ymlnow handle:- ๐ท๏ธ Titles and subtitles
- ๐ถ Sound types (ambience, effects)
- ๐ผ๏ธ Display modes (e.g.,
TITLE,ACTION_BAR,SUBTITLE) - โจ List of visual effects (e.g.,
GLOWING,NIGHT_VISION)
-
๐ก This allows a cleaner, unified immersive experience across multiple languages.
๐ป Refactored Core Classes
-
๐ง The
ConfigManager.javaandLanguageManager.javaclasses have been fully refactored to:- ๐งฉ Support modular and dynamic configuration loading
- ๐งฝ Clearly separate config logic from multilingual handling
- ๐ Improve future maintainability and scalability
๐งฎ New Versioning Convention
๐ท๏ธ Format: MAJOR-Phase.Build
-
Example:
0.3-Seed.20.3โ Main plugin versionSeed๐ฑ โ Current development phase (alpha / pre-beta)2โ Second build in the "Seed" phase
๐งญ This format gives a clear view of the pluginโs development stage and iteration.
This also not the final version of the 0.3, pls wait for it, this version will have more features, if you have suggestion for the future version or got a problem, go to the discord server
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:aVE0EPce:TP3jUAYA"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:aVE0EPce:TP3jUAYA"
}

