Unable to find spawn biome что это
Unable to find spawn biome что это
I listed here all the common/recurrent bugs, to begin to correct the most of all as quickly as possible.
If you know an unlisted bug, post the bug description in this topic.
Crashs:
— Very rare random crash when load a world
Multiplayer:
/!\ Chicken/Cow mangers can crash the client when he try to connect to the server /!\
Serious bugs:
— For some graphics card, the character or specific monsters are invisible
— Some antivirus can prevent the game from launching
— Some intel graphics chipsets: shadows shader is totally broken
— Sometimes when I rescue a Cholridian (hit the cage with my sword) the game crashes. (?)
— Crafting anything beyond 9999 without putting it in inventory (held on mouse) consumes materials but doesn’t give any benefit
— NPCs can disappear when load the game (?)
Bugs:
— While in a dungeon / event thing, pausing the game doesn’t pause the event timer
— Keybinding have some problems
— Some runes have the «void» effect (critical immunity)
— The bow can get stuck, which prevents to use the sword if you change your equiped weapon
— Occasionally when a summon is killed by another mobs reflect it stays on field and freezes at full health (?)
— If an enemy kills themselves with your captured monsters reflect ability, they drop souls instead of experience.
Minor bugs:
— No description overlay on quest items
— Chicken is blue on the manger interface
— You can’t remove ores with the hoe so can’t remove grass if there is an ore
— Door stay in the air when you remove blocks around
Design problems:
— No descriptions on equipment empty slots
Not yet implemented:
— Quests: detect items on the ground (required items need to be on your inventory)
Plains biome spawns in Nether, creating MASSIVE gaping holes everywhere #199
Comments
TheVisionaryOne commented Oct 7, 2019
For some reason, NetherEx is generating a «plains.json» file in its minecraft biomes folder (config>netherex>biomes>minecraft). This causes actual overworld plains biomes to spawn in the nether, which produces HUGE gaping holes in the world.
It looks really ugly, and I haven’t found a fix for it. Deleting the json file doesn’t work, because a new one will generate in its place. Replacing the text of the json file with a different biome doesn’t work either.
(For reference, I’m using version 1.12.2)
The text was updated successfully, but these errors were encountered:
LogicTechCorp commented Oct 7, 2019 •
If the plains biome is being generated that means that there is an issue with another biome. Did it suddenly occur? Is this in a new world or an old world? Did you update any mods recently? Can you also send me the plains.json?
TheVisionaryOne commented Oct 7, 2019
The problem occurred only on the second world I created with NetherEx. I was testing a modpack, and installed NetherEx to see if it was compatible with my pack. Everything generated perfectly fine for the first world, and then I generated another one (same session, no new mods or anything), and I started seeing plains biomes everywhere. That should hopefully answer most of your questions.
Also, here’s my modlist, in case it might be helpful.
LogicTechCorp commented Oct 7, 2019
If you remove Biome O’ Plenty, does the issue still occur?
katubug commented Oct 7, 2019 •
Edit: I did just compare your plains.json to the /minecraft/hell.json and they do match in terms of syntax and setup. So I’m not sure what’s going on.
Edit 2: I also have a workaround for you:
B) Copy over the contents of the hell.json and overwrite what’s in the plains.json. This should cause the «plains» biome to spawn as a hell biome instead.
The reason it’s generating as gaping holes is because in the plains.json there are no blocks defined for the biome to be made out of. As to why the plains.json is generating at all, that’s beyond me. It’ll be on you and the devs to work out, but I’ll help if I can.
TheVisionaryOne commented Oct 7, 2019
@LogicTechCorp I thought I had already tested Biomes O’ Plenty, but I guess not! I removed it from my modpack, and the Nether looks fine now. It’s interesting that katubug was able to run both Biomes O’ Plenty and NetherEx together without any problems.
@katubug I tried both changing «isEnabled» to false in the plains.json, and copy-pasting the contents of hell.json into plains.json. Neither worked, and the plains.json file was reset to its default contents once I created the second world since updating the file. I am using a newer Forge version, but that shouldn’t matter much, right?
I tested worldtypes (and disabled Climatic Biomes 2, which provided the main worldtype I was using for testing), but all of them had these broken plains biomes in the nether. Even the default worldtype had them, which doesn’t spawn Biomes O’ Plenty blocks/biomes. I think I’m even more confused than before.
katubug commented Oct 7, 2019
If you create a new instance with just NetherEx/LibEx, does the plains.json still generate? That’s such a bizarre error, I can’t imagine what else could be interfering with it. I would assume that Forge hasn’t changed enough from 2838 to 2847 to cause a bug on that scale, but if I know anything about technology, I wouldn’t rule it out.
LogicTechCorp commented Oct 7, 2019
@TheVisionaryOne Which versions of LibraryEx, NetherEx, and BOP are you using?
TheVisionaryOne commented Oct 8, 2019
@katubug I tried creating a test environment in Forge 2847, and no plains.json file generated. Some other mod must be causing the problem. but it’s absolutely bizarre that another mod is generating files in NetherEx’s folders. Unless NetherEx has some sort of broken compatibility integration with another mod, it seems like NetherEx is completely unrelated?
@LogicTechCorp I’m using the most recent versions of all mods in question for 1.12.2. Biomes O’ Plenty 7.0.1.2441, LibraryEx 1.0.12, and NetherEx 2.0.15.
I’m really not sure where to go from here. Like I said, I already tried disabling Climatic Biomes 2 (which is the only other biome-generating mod in my pack that I can think of), and nothing changed.
LogicTechCorp commented Oct 8, 2019
I am not sure where the issue lies. The plains biome generating is purposeful on my end, but it is to signify that there is an issue.
katubug commented Oct 8, 2019
@TheVisionaryOne You mentioned you had one of the BoP nether biomes disabled, right? Does the issue still occur if you re-enable it?
I guess at this point, troubleshooting wise, the best option is to do the half-and-half method until you find the mod that’s causing it.
If you can get me a modlist with version numbers (via screenshot, maybe) I can help you nail it down.
TheVisionaryOne commented Oct 9, 2019
So it is an intended part of the program. That makes a little more sense than it just randomly showing up. Still weird that there’s an. issue? The biggest issue is the plains biome itself. xD
@katubug I did disable a BoP biome, and at first, I thought that was the cause. I tested re-enabling the biome, but it didn’t fix anything. I’m really confused about what’s causing this, and I would like to get to the bottom of it, but I just don’t have the time to go mod-by-mod.
@LogicTechCorp If the plains biome json is programmed to mark an issue, is there any sort of log or copy/paste text I could send you that would help you nail down what the issue might be?
LogicTechCorp commented Oct 9, 2019
@TheVisionaryOne Try re-enabling the BOP biome, delete the NEX biome config folder, start the game to regenerate the configs, and then disable the BOP biome via the NEX biome config for the biome.
katubug commented Oct 9, 2019
TheVisionaryOne commented Oct 9, 2019
@LogicTechCorp You’re a genius! Originally, I didn’t realize that biomes could be disabled through NetherEx, so I went straight to BoP instead. Re-enabling the biome through BoP and then disabling the biome through NetherEx fixed the problem completely.
TheVisionaryOne commented Oct 9, 2019
@katubug Thanks for your help troubleshooting the problem as well!
You can’t perform that action at this time.
You signed in with another tab or window. Reload to refresh your session. You signed out in another tab or window. Reload to refresh your session.
server thread FATAL: Could not find biome with name (biomename) from biome group (biomegroup) #596
Comments
rakostep commented Jan 14, 2021
OTG Plugin or Mod
OTG Version
Forge or Spigot Versions
Server/Client Log
[The full latest.log file from your server or game client, especially important if you have a stack trace]
[ServerConfigProvider.class:?] 14.01 03:03:12 [Server] INFO at com.pg85.otg.forge.world.WorldLoader.getOrCreateForgeWorld(WorldLoader.java:360)
[WorldLoader.class:?] 14.01 03:03:12 [Server] INFO at com.pg85.otg.forge.world.OTGWorldType.getBiomeProvider(OTGWorldType.java:158)
[OTGWorldType.class:?] 14.01 03:03:12 [Server] INFO at net.minecraft.world.WorldProvider.init(WorldProvider.java:58)
[aym.class:?] 14.01 03:03:12 [Server] INFO at net.minecraft.world.WorldProvider.setWorld(WorldProvider.java:40)
[aym.class:?] 14.01 03:03:12 [Server] INFO at net.minecraft.world.WorldServer. (WorldServer.java:116)
[oo.class:?] 14.01 03:03:12 [Server] INFO at net.minecraft.server.MinecraftServer.loadAllWorlds(MinecraftServer.java:298)
[MinecraftServer.class:?] 14.01 03:03:12 [Server] INFO at net.minecraft.server.dedicated.DedicatedServer.init(DedicatedServer.java:270)
[nz.class:?] 14.01 03:03:12 [Server] INFO at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:486) [MinecraftServer.class:?] 14.01 03:03:12 [Server] INFO at java.lang.Thread.run(Thread.java:748) [?:1.8.0_211] 14.01 03:03:12 [Server] Server thread/ERROR [minecraft/MinecraftServer]: This crash report has been saved to: /./crash-reports/crash-2021-01-13_22.03.12-server.txt 14.01 03:03:12 [Server] Server thread/INFO [minecraft/MinecraftServer]: Stopping server 14.01 03:03:12 [Server] Server thread/INFO [minecraft/MinecraftServer]: Saving players 14.01 03:03:12 [Server] Server thread/INFO [minecraft/MinecraftServer]: Saving worlds 14.01 03:03:12 [Server] Server thread/INFO [FML]: The state engine was in incorrect state SERVER_STARTING and forced into state SERVER_STOPPED. Errors may have been discarded. 14.01 03:03:12 [Server] Server Shutdown Thread/INFO [minecraft/MinecraftServer]: Stopping server 14.01 03:03:12 [Server] Server Shutdown Thread/INFO [minecraft/MinecraftServer]: Saving players 14.01 03:03:12 [Server] Server Shutdown Thread/INFO [minecraft/MinecraftServer]: Saving worlds 14.01 03:03:13 [Multicraft] Server shut down (running) 14.01 03:03:13 [Multicraft] Restarting crashed server in 10 seconds 14.01 03:03:13 [Multicraft] Server stopped «>
Description
I assume it’s OTG not being able to find a biome ID for some reason, been swapping around different presets and the result is all the same, it will say that it can’t find the biome from the biome group.
It processes smoothly if I remove a biome name that’s mentioned but it gets the same error on the next biome in the biomegroup (in WorldConfig.ini)
Tested it now with just OTG installed and now it says it can’t find the biome in vanilla minecraft.
The text was updated successfully, but these errors were encountered: