Leaderboard

Forge for 1.16.1 The first Forge build for 1.16.1 is now live thanks to the hard work of: covers, illy, jd, garrett, giga, and the rest of the forge crew. With their help we were also able to release the updates to MCPConfig for 1.16 and 1.16.1 the same day that vanilla did. The Nether Update has brought a lot of changes to many systems, and as with any update there are likely to be bugs. We are still evaluating and working on some of the systems like dimensions and trees to come up with the best system to allow for modders to integrate with vanilla’s new dimension system. We are also expecting Mojang to release a 1.16.2 fairly shortly and are prepared to work on updating to it as soon as they do. As with every update, there are bugs and other minor things to be expected. Please report them responsibly and have fun with the new version! Changes to the LTS There are a couple changes happening to the Long Term Support system originally introduced here. We are moving the LTS from 1.14.4 to 1.15.2 to reflect the community being more active and also changing how we chose what version the LTS will be to be more maintainable. We are now going to be supporting the latest (n) and second latest (n - 1) versions, with the reservation of potentially having the LTS being n - 2 if something is Mojang ends up really making a mess of a particular version. That being said we still will be providing critical fixes for all possible versions. Do not worry about 1.14 being instantly dropped while we are still working on updating 1.16, as we have a customary grace period for while everything is still in flux before we start strictly enforcing the LTS rules. New Team Members We are happy to announce we've added a few new members to the Forge team officially. These people have been a part of the community for a while and have been helping out a lot. The first two are new members of the 'Toolchain' team. Which is responsible for some of the backend tools, like the decompiler, update scripts, gradle and other internals. The others are joining our ever growing list of Triage team members. Who are responsible for managing the issues and pull requests on our github. They are the front line of bug reports and feature requests, treat them with respect and listen to what they tell you! Toolchain covers1624 JDLogic Triage AshersLab Curle OrionOnline pupnewfster

Hi, used Minecraft 1.16.1 and forge-1.16.1-32.0.7-installer.jar on Ubuntu 20.04. Tried different openjdk versions from 8-14, none worked. Minecraft was running once, stopped via console, this was a fresh install. My install command : java -jar forge-1.16.1-32.0.7-installer.jar --installServer the part where it fails : Data io/netty/internal/ Processor failed, invalid outputs: /home/regnator/mc/./libraries/net/minecraft/server/1.16.1/server-1.16.1-slim.jar Expected: 6cbe49c4d26497791d1d511c2d3b7d1fa46fa2e9 Actual: 3f1b64c684df16a25e6c44079b06ac12131db572 /home/regnator/mc/./libraries/net/minecraft/server/1.16.1/server-1.16.1-extra.jar Expected: 79ed2a48582a58ce917a04344c35c9c9abb557e2 Actual: 501b61ed1857f6452fe36a5faaf1265d38999c6f full logs : https://privatebin.net/?29f4d24ddf99dcf7#4ykHNhbSaNdwNfu2HEzyrUgUp9dw4527zrCXdqx43d1r EDIT: Still fails with forge-1.16.1-32.0.14-installer

Forge 1.16.1 32.0.7 just dropped and that *does* use vertical biome detection (visible in the nether from the vanilla F3 screen). Doubt many people know much about this right now... Time to investigate...

Yeah, I know. If a mod wants to shut down the thread, let them. But until then I'll help whoever I want out.

So THAT's where the issue is coming from, ok I understand now. Note that 1.12 -> 1.13 things changed from prefix to suffix, so if things like this don't line up, try switching them around

1.15.x is our new Long-Term Support candidate. I presume it'll remain the default until the grace period ends and we move to 1.15.x & 1.16.x, by which point the default branch *should* move to 1.16.x. Can't be certain though, because we're a long way away from a recommended build. Early beta, you see.

It looks like some mod forgot to end the buffer after applying a transform to the world, causing the block that renders next (the door) to behave weirdly. I'll quickly check to see if i can narrow down which one of those mods is being weird. At a glance, it looks like removing Optifine isn't causing it, more that the hacks and changes that Optifine make to the game, solve it in some weird roundabout way. Which is, as you can guess, bad for consistency.

This is a known bug, and we're working on fixing it. It should be solved in one of the next few updates.

I did find the git branch, my eyes probably skipped over it. But I did check. Either way, the earliest change on the branch/build isn't even 24 hours old yet. It was committed at near-midnight last night.

ArrowItem, ArrowEntity and BowItem will be a lot of help here. I believe there is also a Projectile class? (Also look at ShootableItem, I think it's called) That would be a good place to start -- when you boil it down, all you want to do is: 1) Make an item... 2) Which spawns a new entity when you right click... 3) Which then travels until it hits something... 4) And if it hits an Entity, damage it. Of course there's more you'd want to do, such as making it arc, charging up the bow, consuming ammo, etc..., but those are the basic steps. If you're familiar with onItemRightClick and making entities, you're already most of the way to something functional

Decompiling and changing a mod without the author's permission is against our "code of conduct", and is not encouraged. There is a public git repo of MorePlayerModels here, but it is for 1.10.2 and you're on your own to update it.

If someone benchmarks a clean Forge install and a Fabric install, then the performance might be a tiny bit (not even noticeable) better on Fabric's side due to its lightweight. However such result is not conclusive, as Forge does a lot more (event system, utils, etc) than Fabric. Try benchmarking both API with 100+ mods and Forge API will manifest its advantage. Judging APIs solely for its performance is like comparing Tetris to a first person shooter game. "Hey Tetris uses up less RAM and CPU so it is much better than the FPS game!" But yeah, people might prefer Fabric if all they want is to add a simple tweak/mod to the game. At the end of the day, it is really up to the user and his/her use case.

Looks to be SteveKunG's Lib causing the crash. It looks like it's only used by Indicatia and More Planets, which you have neither of. I can't see why you even have it installed, so better to remove it.

1.7.10 is not supported on this forum. Update to receive support. Only 1.15.2 and 1.16.1 are supported on the Forum and Discord.

BooleanProperty

Yeah, your code is useless for what D7 suggested. You're using spawn eggs to change the spawn entity of an existing spawner block and doesn't deal with stack NBT at all.