LexManos

1) Don't yell 2) We have a tech support forum for a reason 3) Just delete Forge's files from your MC folder. It doesn't install anything outside that folder.

This is not caused by Forge, but it is caused by one of your mods. No idea which one. The issue is *something* is setting the revenge target of the zombie to null, between when the AI starts running, and when it alerts others to help. Best bet we could tell you, is to start removing mods and see when it stops.

Talk to Mojang, they dictate what version of Java we support by what version they ship in their launcher. If we get them to update we can update as well. Unfortunately, as it sits, the core library we use (ASM) has us stuck if we update it to support 11+, it no longer runs on 8, which is what Mojang ships.

Forge Version: 1.14.4-28.1.0 Minecraft Version: 1.14.4 Downloads: Changelog (Direct) Installer (Direct) MDK (Direct) Intro: Whelp, the time has finally come, we are ready to do our first Recommended Build for 1.14.4! I want to thank everyone who has helped work on this and get it ready to go. This has been a long road, and I admit it has been a lot longer than I wanted it to be. Unfortunately, some things went wrong, some aspects took way longer than they should have. But we move forward. This is one of the biggest updates to Forge that we have ever done. Everything has been re-written from the ground up to hopefully provide us a platform that will last the next 10 years. Here is a basic overview: Versioning: You may have noticed, that our version number has changed a little bit. This was done to cleanup some redundant information and more directly link our versions to our source code. Our versions are now in the format `{MinecraftVersion}-{ForgeVersion}.{RBNumber}.{CommitCount}`. Launcher: In order for Forge to modify the game, we have to use a system that allows us to modify the java code as it is loaded. Initially we created a system called LegacyLauncher, which we shared with Mojang this allowed them to load their old versions into their new multi-profile launcher. However Java9 was released, and broke it. This is a fundamental change in how Java works and required us to re-design our basic loading system. We now have a new loader called ModLauncher that is designed with Java9+ in mind. So hopefully it works for the next decade! Installer: There are a lot of things that Forge does at startup, some of them is to apply our patches to vanilla's code, and transform vanilla's code to SRG names so that mods can work between minor Minecraft versions. This used to be done every time you started the game. We now do this once, at install time. This will save a bit of time while starting the game. Mods: We have changed quite a bit about the mod loading system, basic mod life cycle events are now run in parallel during Minecraft start. This should help decrease the load time. We have also removed a lot of cruft that has existed since the Risugami ModLoader days. Which will allow for cleaner, more flexible code. Overall the mod dev experience should be a lot better. Coremods: As much as I hate it, mods that edit bytecode will always be a thing. LegacyLauncher had a system that allowed any mod to edit anything in anyway they wished. This has caused a lot of issues due to modders implementing them wrong. The new ModLauncher system has a similar thing in place, however we have also released a new `Coremod` project that is intended to be the default system anyone who was making a Coremod. This new system uses Java's JavaScript engine to isolate the coremod from the rest of the game. Which should solve the most common issues in existing coremods. MDK: We have completely re-written all of our build tools. The new system treats Minecraft and other Mod dependencies as normal gradle dependencies. This means you no longer need to use special 'setupWorkspace' tasks before being able to build your mod. It also means that more systems should be able to support the work space as it is more in line with a basic java work space. We are currently targeting Gradle 4.9, however we have reports that it works all the way up to 5.5. Data Generators: Minecraft uses many data files, typically in the form of a json file. These are used for Blocks, Models, Textures, Recipes, Tags, and so much more. There are some people in the community who think that this is bad because it is difficult to create that many data files. No programmer in their right mind would do that by hand. Mojang themselves have used data generators from the beginning. We finally convinced them to expose this to modders, and Forge has enhanced them for use by Modders. We plan on adding even more features to this system, so feedback is highly appreciated. MCPConfig: Minecraft is released in obfuscated names, since our inception we have use MCP to provide us with the information needed to turn the game into something we can work with. This project started off as a set of python scripts and tools. But now with ForgeGradle and other projects the python is no longer necessary. So we have moved to just providing the Mapping data. This is now a public project which allows more community interaction, and feedback. These mappings are published to Forge's maven, and can be used in any project you wish. The only restriction is that you can't re-distribute and create derivative works. This is purely a technical necessity. These mappings are designed to be stable and compatible across Minecraft versions as best as possible. If multiple mappings were released that conflicted with each other it would cause nothing but a headache. We also worked with the community to design some naming standards, you can view more information on that on github. Mojang's Official Mappings: Starting with Snapshot 19w36a, Mojang has started providing their obfuscation logs. Which in theory is a great asset to modding as it will help people understand the code. However, Mojang released these mappings as All Rights Reserved, which means we can't actually use them in any way. So until they clarify things we will continue to work on Forge and use SRG names for our development/publication. The hope is that Mojang gives us some limited rights so that Modders can use these names in their own mod code, as well as publishing on places like Github. But until that happens I advise anyone who looks at these mappings to be very careful to not use them in anything you publish to anywhere. This include in jar files of your mod, or in the source code you publish to your SCM. We will keep you informed when we get updates from Legal. Fluids: Minecraft introduced the concept of 'waterlogged' for things like stairs, fences, and slabs. This introduced a formalized 'Fluid' system in Minecraft. This has caused us to need to re-write our Fluid system. We are trying to work with Mojang to make the vanilla system more flexible for modders. We will continue to develop this system as modders give feedback and make it as best as possible. Changelog: As Forge and all of it's tools have basically been re-written from scratch, the changelog is huge. You can view the raw changelog here. For more information on all the other tools in the Forge ecosystem you can view our Github. Don't worry, more detailed lists will return in future RB, this one is just to large too aggregate properly. Closing Remarks: This has been a long time coming, to those who are concerned about the time it took. I would like to remind you that now that our major re-write is over, we should be back to our same-day update schedule we have achieved for the last several Minecraft versions. These are major changes, so I would suggest people join our Discord and work with each other to update, find bugs, etc. I fully expect, as with any software release that there will be bugs. Please report them so that we can fix. Some of you may also have noticed, that there are only the direct downloads at the top of this page. This is because we have reached our Patreon goal and removed ad links. Nobody likes ads, but running Forge costs money. We also have a merch store. If anyone is interested. [/shameless promotion] Lets get back to work!

Post the full log files. There is nothing to fix on our end. as it installs fine for most users. You may try updating your java.

What? Our tools already do that, they match the names as best they can and then migrate our mappings. This changes literally nothing in the SRG/MCP update process. It just makes a big legal/community headake until the legalities are fleshed out by Mojang.

No, this will be irrelevant for the update cycle. Forge, and other projects have had access to this information for years. As I have stated many times, the concept that Forge is slow to update is a dirty lie spread by people who just want to disparage our good name. 1.13 is a SPECIAL CASE that took a while as a explicit decision. As we took the time to re-write the entire toolchain/codebase. NORMAL updates take less then 24 hours to do. And we will be continuing that tradition now that our rewrite is finished. MCP will still exist, as there are a lot of things that MCP allows us to have that these mappings do not. Documentation, parameter names, better names, better code from injected data/managed data. This is NOT as useful as people are thinking. And with the legal issues it's actually detrimental to the community as a whole. As the only people who benefit from this, are the ones who do not respect Mojang's copyright. There already are projects that just straight up use the mappings, deobf/ship Mojang's named classfiles/decompiled code. Those projects will get popular because there are members of this community who are not respectable. There probably will be a major fanbase harassing everyone about using the names. But, Forge WILL respect Mojang's copyright, so as is we can't publicly use these names.

We will be making an announcement about it when we can. The current state is that it means almost nothing for us. As the license doesn't allow for us to actually USE this information. We are waiting to hear back from Mojang's legal team {This is all stuff they could of answered before the public announcement by asking us, but whatever} Keep an eye on Github/Twitter and we'll keep you updated.

https://github.com/MinecraftForge/MinecraftForge/commit/4dc34b7d5b945b9d4fa86223771fcfecea7de293

This may be a symptom of a known netty issue. We are trying to find it's root cause somewhere in Netty's code. But it's proving illusive. However, you should be able to still connect if you keep trying.

It's also against Mojang's express wishes if you are creating your own Launcher. They do not want anyone to enter their logic credentials into anything that is not official. And if you dont take launch credentials then you're letting anyone play the game without buying it. So... neither of these cases we support.

provide your data pack or one that illustrates the issue and the steps to reproduce. As it sits, pretty sure we don't mess with anything scoreboard related except to fire a few events around it.

Do not make core mods when you haven't the foggiest idea about basic java mechanics.

Make sure you only download forge from our web site. And then post your installer logs/screenshots. If you're using legit downloads then it will install correctly.

You can install multiple versions they do not interfere with eachother. as long as you have different game directories in your profile. However, deleting the version folder IS "uninstalling" forge as that's all forge does, stick a few files in libraries, and a few in the versions folder.

Reimporting the project a second time will. Eclipse has to request the sources before they are generated. Dont upload mojangs property to 3rd parties. esp5if fg is specifically designed to do the task.

I've started a proper report for you here: https://github.com/MinecraftForge/EventBus/issues/34 I am unable to reproduce, please provide test code/mods and we can take a look.

If you install Forge once, then you can usually get away with updating it again 'offline' because the installer does contain the main Forge jars. However if any libraries change, then you need internet to get them. Not only does this save duplication of a lot of data in every installer, but in the case of Minecraft itself, a lot of legal hassle. You can however just move those needed libraries from a computer you own that has them to another. The installer is smart enough to check if they exist before trying to download them.

values() creates a new array every time you call it so people can't do values()[0] = null; and screwup other people. So yes caching it is recommended.

there is no uninstaller, but you can manually delete the versions folder if you wish.

first off, that screen is horrible, at least make the window a smaller size so the text is readable for us. Secondly, that would be a issue with java. You need to update to atleast J8u111 to get the LetsEncrypt certs... Tho... why vanilla is using lets encrypt for realms... I have no idea.

Yes, your computer does. Run jarfix https://johann.loefflmann.net/en/software/jarfix/index.html

The fluid system is being worked on. Right now we are waiting for king lemming to push his changes. Once those are in we can deal with adding specific things people want. Until then, feel free to comment on the WIP PR for fluids. Instead of here.

You can run the jars. All the exe is is a wrapper for the jar to run java for you. Rather then deal with the crap that is Launch4J we decided to just ship the normal Jar. Unless you can come up with a system that works on modern computers, and on macs/windows We're just gunna keep it as the jar itself.

Remove the mod from the server. Done.