Luis_ST

if you playing on CurseForge you need to enable the debug.log in the settings

please post new debug.log from the logs folder

first of all please show the full code not only a part (main class), then please use the code feature of the forum or use a paste side is your doClientStuff EventHandler called, use debugger to check?

Why it is so hard to understand that we won't help you to create a custom client, And as D7 told you several times create a mod, you can use the Forge API and Mixin (if required) to add more customizable settings to the client

why did you not use two Blocks, this would fix the light issue? as far as i know this is not a issue/bug But I'm not sure what exactly is the reason that you can't sneak along the edge of the block, I suspect that the hitbox area is not large enough for the player to stand on it

if your value is server side and should be synced to the client you need use a server config (server and client value need to match), if the server value must not match with the client value you can use a common config

A config file is only editable for the user (it's hard to edit the config file of a Mod from another), if a other Mod want to override a value a Datapack would be the best option And in general Datapacks are underrated, I think they have a lot of potential because of Mojnag's Codecs unfortunately i'm not familiar with this json Datapack stuff, but as far as i know did you need a SimpleJsonResourceReloadListener which you need to register in AddReloadListenerEvent

you need to register a BlockColor for your Block inside ColorHandlerEvent.Block via BlockColors#register, it's recommended to implement the BlockColor interface using a lambda expression (Edit) In addition the BlockColor returns the color via a int, if you want the vanilla behavior you can use BiomeColors.getAverageGrassColor

post new debug.log

did you register the EntityRenderer?

Problem with Balm. Make sure you are using the latest version. If the Mod is already up to date, report this bug to the Mod author.

please post debug.log from the logs folder

Keep this forums in english please please post debug.log from the logs folder

post debug.log with the latest version of Allthemodium

on client you always can use Minecraft.getInstance(), then you be able to get the local player

KeyBindings are client side only, you need to use TickEvent.ClientTickEvent instead why did you call KeyBinding#consumeClick, you should only check KeyBinding#isDown? last but not least i would recommend you to check the Item also on server side (in the handle method of the Message), since you should never trust the client

when exactly should the player be able to open the container? please be as detailed as possible is the Packet received on server and how did you test if it works?

do this first, then check if it works if it does not work come back and post new debug.log

Refer to the installation guide of Awesome Dungeon End Also note the logs shows an errors of 3dSkinLayers, Awesome Dungeon Nether (same as Awesome Dungeon End) and Oculus

Awesome Dungeon End requires Library Ferret. Unfortunately the mod does not properly indicate this dependency (only on CurseForge), so the mod simply crashes instead of Forge showing a helpful error message.

this is the issue is the code called, use debugger to check

Problem with Allthemodium. Make sure you are using the latest version. If the Mod is already up to date, report this bug to the Mod author.

ItemStack does not override equals, this means the == operator is used, you need to use IForgeItemStack#equals (requires an ItemStack and a boolean) or you check the Item of the ItemStack, therefore you can use a instanceof check, equals or the == operator depends on your purpose

There is no error in the log you post, please make sure it is the full debug.log If this is the full debug.log please post launcher_log.txt as well

please post debug.log from the logs folder