DavidM

Oh The Biomes You'll Go is made with MCreator and is broken. You should remove it (the authors are moving on to Forge though).

The other players would have to install the mod on their clients for the model to work.

Please read the EAQ and post logs. Also make sure you are pressing the key for chat according to your in-game settings.

I don’t think anything regarding Applied Energistics has changed. You might have set up something wrongly. You might want to post screenshots of your setup so others can check it. 46 cows is not that many, so depending on your preference it might be easier to hook up fluid importers to each milker instead of using redundant drums.

For each player, you can store his settings of all other players in the player’s capability. Capabilities can be persistent, and seems to be an appropriate option here. Check out World Saved Data. Send a packet to the server (with a handler that opens the GUI from server side) when the key is pressed.

There is this server plugin called Matrix that does a pretty good job of detecting cheats (although not Forge relevant). I’ve tested the plugin for my friend’s server with custom written cheats, and it seems to do well with simple cheats (ones created without an anti cheat in mind). If you need better anti cheats then I’m afraid you will need more moderators.

If you are using Java 8 and the game is crashing, then the crash is not caused by your Java version. There are millions of reason that Minecraft could crash, and changing Java version won’t fix them all.

Create a tickable tile entity -> stores the current mined block position -> break the block at that position and increment the position storage every tick. If RF is needed, use Forge Energy capability (as explained in the official documentation).

There is too much things that might go wrong with “saving the stitched results” of mods. 1. The config might change. While the mod ID and version stay the same, a mod might change results in TextureStitchEvent based on the config values. 2. Some mods can have Easter eggs based on current time (some mods even have varying registry entries during holidays like Christmas to add in Easter eggs items). 3. Some modders might accidentally label the version wrong (i.e. forgot to bump the version). While this have almost no effect as of now, with your proposed system such mistakes can make the entire game unplayable. In general, a checksum of mod ID and version is not a definitive method of checking whether the stitched texture map has changed. Due to the flexibility of Forge, it is hard (if not impossible) to check if the stitched texture would change. However in 1.14 the loading of mods is parallel, so the overall loading time would not be so long.

Cheaters won’t install anti cheats to get themselves banned though... Cheating is done by modifying the client. Cheaters have access to the client, therefore all “client-side anti cheats” are fundamentally flawed.

DeferredRegistry already automatically sets the registry name. You are also setting It manually, resulting in:

My bad. Don't know where I got that from.

You might want to look at how vanilla handles the portal (check vanilla obsidian class).

If I am a malicious player playing on a server, I can modify my clients to send fake quest complete packets. Your current packet handling code will allow me to obtain quest rewards over and over, since it does not check for 1) if the quest is already completed 2) if the player has the quest items in his inventory.

There is no need to inject code in this case. You might want to look at how vanilla code handles sprinting and manually simulate/trigger it.

Never compare registry names when you can just compare the two references. In your case you just want to know if the item is an instance of potato, so your previous check should work (although it would be better with ==).

The AA is just the alpha value (in the range of [0, 255]). You can use 255 (opaque) if you do not want transparency.

Do not make custom clients.

The server should also check if the operation is successful (if you haven't added that already). Clients could just send fake information to the server, which would carry them out if no check is in place.

Forge is a rather complicated API and will be unnecessarily confusing for people who are not familiar with Java. Learning Java through making a mod might be slower than the combined time of learning Java properly + making a mod. On my setup, I can view the source code of a class by pressing cmd and left click on the class name. Hotkeys like this varies depending on your setup, so it is recommended to get familiar with your specific IDE (i.e. read its manual).

The debug log is actually better than the crash log when asking for help, as the debug log contains more information. @Pantosh The log seems incomplete. Are you sure that is the correct/full log?

We use our IDE and read the source code regarding the Mod annotation.

You should report to its author.

This is irrelevant to this thread. Please make your own thread. MCreator mods are badly made and are likely to break (although might not at first). I would suggest to remove any mods created by MCreator.

AFAIK there is no default way to increase the reach range for entity. You will have to do your own recasting on the client side (basically simulate what vanilla Minecraft does).