alcatrazescapee/chocolate

A mod that fixes some annoying bugs with vanilla's data driven world gen in 1.16

chocolate's Issues

Future request: Fixing mob and block hitboxes

I know that hitboxes of some mobs and blocks really frustrate people. For example hoglins and scaffolding. Maybe oak doors can have those holes get carved too or something. This kind of future could be helpful and make things a bit easier when hitting mobs like hoglins.

Fix bug "MC-194811" (Missing structures will destroy saved worlds)

This is a really annoying bug that has to do with world gen so I thought I'd ask, is it possible for you to fix this bug: MC-194811 ? Am not sure what you will need to do to fix this but if you could take a look i'd appreciate it. Cheers!

Possible vanilla bug you can fix?

Chocolate has unlisted dependency on Forge 34.1.33, resulting in unexpected crashes with anything lower

crash-2020-10-29_22.19.21-client.txt

no idea what to say, but here you go

doesn't allow my game to start. Crashes at 100%. Ignore my crafttweaker scripts

log:
latest.log

Modlist:

MC-187938 (Custom dimensions don't update on /reload)

Might be worth looking into, it seems to fit the bill of requirements - just to see whether it can actually be fixed.

https://bugs.mojang.com/browse/MC-187938

[1.16.5] Error when stopping server

When stopping a server, a configuration error is shown which may cause the server to hang forever without actually stopping.

Here is the error from the log:

[31Mar2021 15:50:11.454] [Server thread/ERROR] [net.minecraftforge.fml.config.ConfigFileTypeHandler/]: Failed to remove config ./world/serverconfig/chocolate-server.toml from tracker!
java.lang.NullPointerException: null
	at com.electronwill.nightconfig.core.file.FileWatcher.removeWatch(FileWatcher.java:134) ~[core-3.6.2.jar:?]
	at net.minecraftforge.fml.config.ConfigFileTypeHandler.unload(ConfigFileTypeHandler.java:76) ~[forge:?]
	at net.minecraftforge.fml.config.ConfigTracker.closeConfig(ConfigTracker.java:114) ~[forge:?]
	at net.minecraftforge.fml.config.ConfigTracker.lambda$unloadConfigs$2(ConfigTracker.java:88) ~[forge:?]
	at java.lang.Iterable.forEach(Iterable.java:75) ~[?:?]
	at java.util.Collections$SynchronizedCollection.forEach(Collections.java:2067) ~[?:?]
	at net.minecraftforge.fml.config.ConfigTracker.unloadConfigs(ConfigTracker.java:88) ~[forge:?]
	at net.minecraftforge.fml.server.ServerLifecycleHooks.handleServerStopped(ServerLifecycleHooks.java:135) ~[forge:?]
	at net.minecraft.server.MinecraftServer.func_240802_v_(MinecraftServer.java:682) ~[?:?]
	at net.minecraft.server.MinecraftServer.lambda$startServer$0(MinecraftServer.java:232) ~[?:?]
	at java.lang.Thread.run(Thread.java:834) [?:?]

Question: does the mod fix a lag spike?

whenever I remove choco fix from my modpack, I start experiencing frustrating lag spikes, I've checked the mod's page and it's not mentionned there.

Crash with Advanced Rocketry

The Server crashes when a player tries to build a rocket.

Advanced Rocketry version: 2.0.0-10
Forge: 36.1.13
Chocolate Version: 1.3.0-1.16.4
Stacktrace: https://gist.github.com/Seniorendi/184038f7f0150858a43feed517b7cfe3
In the log is a text with "Please Report this to Chocolate!" this is the reason why I'm here.

Question: does this mod also fix the weird chunk border generation that tends to happen when adding / removing biomes?

Performance issues with AMD GPU's? Or Systems?

So my build is completely AMD, never had issue running anything until I found out that mods alike to foamfix cause issues and so same thing happening here. I Don't know if it's something that's solvable or it just exists, but I wanted to inform it regardless. Only fix I've found is not using it, but now its a requirement for BYG.

(Enhancement) Return to Start Menu on Crash

Since Vanilla Fix won't be receiving a Minecraft Forge 1.16.3 update in the foreseeable future, can you please add the ability for crashes to return to menu, instead of closing the game?

This is especially helpful to people like me who play large modpacks with 15 minute start-up times, as well as people (also like me) who are unlucky and discover every possible block combination that causes crashes.