Luis_ST

The server must be started with the .bat/.sh file. If your server host does not support the new system talk to them.

Why to the server, the effects of the Totem are client side only, you need to send a (custom) Packet from server to client. This can be done as follows: <your simple channel>.send(PacketDistributor.PLAYER.with(() -> <the server player>), <your custom packet>);

Are you sure you know basic java, since the "Menu method" is the constructor. The Component is the title of the Screen you can use Component#empty for testing.

Please post the actual error message you get and please avoid posting images of errors and code, use the Forum code feature or a paste side instead.

You should take a look at this FCW page, especially into this entry.

That should work yes. This will now blit a texture at screen pos 0/2 (x/y) with size 192/192 (w/h) with texture offset 0/0 (x/y).

blit is a method in the Screen class you need to call it after setting up the RenderSystem. If you don't know how to call a method you need to learn basic java before modding minecraft.

Vanilla handles the Totem of Undying in LivingEntity#checkTotemDeathProtection. The particles and the totem overlay are handled via ServerLevel#broadcastEntityEvent with event id 35. Note this will call the vanilla logic of the Totem on the client in ClientPacketListener#handleEntityEvent. I you wish to have a custom behavior you need to send a custom Packet to the client which handle this for you.

You need to blit the texture to the screen via #blit.

You can use https://gist.github.com/ or similar paste websites.

Where did you call it please show more context?

If you using CurseForge you need to enable the debug.log in the settings. I guess this is is a issue with CurseForge

What did you mean by "try to call the screen"?

Please post debug.log from the logs folder. What did you mean by "in Forge", Forge is not a File Explorer?

PlayerTickEvent would be the better option, check there if TickEvent#side is LogicalSide#SERVER. Also note that is fired each tick twice so make sure you check TickEvent#phase against Phase#START or Phase#END.

This error is often an indication that the max fps are set to 0, edit the options.txt file in your game directory and change the maxFps value.

Show what you have tried.

Which version did you use since this is not 1.19.2 code?

I digged a bit into the vanilla code and i found MultiPlayerGameMode#destroyTicks (requires an AT). The only problem is this is client only, if you subscribe to ClientTickEvent in a client only EventHandler class you can access to the MultiPlayerGameMode instance via Minecraft#gameMode. If you use destroyTicks % 20 == 0 you can call the code each second, inside there you send a custom Packet to the server which will damage the Player on server. As I said before, this is unfortunately client only, which means it can easily be modified by other Mods. For this reason it will be difficult to verify this on the server, in this case you might damage the Player even though it doesn't mine a Block.

Player#displayClientMessage Note in your case the second argument must be true

Maybe BlockEvent.BreakEvent it is fired when the player has mined the Block, but has not been removed from the World yet (after the Event). If you create an EventHandler with EventPriority#LOWEST, you can make sure you are one of the last EventHandlers. Then you can get the break speed of the given BlockState and you can calculate the start time.

Unfortunately there a lot of Mods which could cause the crash. The first thing you could try is to remove all magic performance Mods (like Rubidium, etc.) If the error remains please post debug.log from the logs folder. If you using CurseForge you need to enable the debug.log in the settings.

This is still not the debug.log it's debug-1.log, please post a screenshot of your logs folder.