Tags
Creators
Details
Licensed ARR
Published 4 years ago
Updated last week
All versions
26.3.0-3.0-fabric+forge+neo
Release
[Fabric/Forge/Neo] 26.3.0-3.0last week 648
Compatibility
Minecraft: Java Edition
26.3
Platforms
Fabric
Forge
NeoForge
Quilt
Supported environments
Server-side
Singleplayer
Required content
Any compatible version
Changes
- Big 3.0 update of Biome Spawn Point! :) Various fixes and features added.
- Fixed the spawn biome not being found when the game language isn't English.
- Fixed players spawning just outside of the chosen biome, or in a different biome than the one that was found.
- Fixed Village Spawn Point moving the spawn to a village outside of the chosen biome.
- Players now spawn on land instead of in water when the chosen biome continues underwater, like beaches.
- The spawn biome is now picked using the world seed, so the same seed gives the same spawn point.
- Added the /biomespawnpoint reload command, with /bsp as a shorter alias.
- Added the /biomespawnpoint enable and disable commands, which enable or disable a spawn biome in the config file.
- Added the /biomespawnpoint repick command, which moves the world spawn point to a random new spot in one of the spawn biomes.
- Added the /biomespawnpoint reset command, which moves the world spawn point back to where a new world with the same seed would place it.
- Added the 'biomeSearchRadius', 'minimumDistanceFromBiomeEdge' and 'preferSpawningOnLand' config options.
- Biome tags can now be used in spawnbiomes.txt, e.g. '#minecraft:is_forest'.
The complete changelog with detailed information about previous versions can be found on my website:
> https://serilum.com/mods?changelog=biome-spawn-point
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:mtfbtanr:iJnqmNM6"
}
// Legacy Loom dependency
dependencies {
modImplementation "maven.modrinth:mtfbtanr:iJnqmNM6"
}

