LexManos

Minecraft 1.12: The newest version of Minecraft has been released. Forge has been updated to support this new version. However due to the way Mojang implemented the Recipe changes there are a lot of under the hood changes that we need to do. Most notably re-writing on of the largest/most intricate systems of Forge, The Registry system. This will take some time, so do not expect a recommended release quickly. However if you are a modder you can start using the current versions to build against. Some API's may change in the early days of Forge so be sure to be ready for that. I'm sorry, I usually try my best to maintain binary compatibility, but it's just what will need to happen. For users, you can use the current builds. But just be warned that things are actively being developed and we ask to please responsibly report issues on the forum. Once I finish the rewrite and get a stable recommended build of Forge out I will make a more detailed post listing all the major changes like I always do. New Policy on Coremods: Sadly core modding is still a thing. As always we request that you guys attempt to work with us to get changes into Forge instead of core modding it yourself. However, if you MUST we have decided to put forth to the community a few 'Best Practices' for core modding. The intention is that large communities such as FTB, Technic, and Curse work with us to promote these best practices. 1) Coremod must be the coremod only, and no extra library/features/apis/etc. There are far too many coremods in the community that package tons of classes that have nothing to do with the modifications they make to the game together so that people will be forced to use their coremod just because they want a utility. This is bad. So Coremods themselves should be limited to JUST the IFMLLoadingPlugin, and IClassTransformers, and as few utility methods needed to make those hooks run. 2) Coremod binaries must be signed. This is a very basic thing that just verifies the person/organization we think made the coremods actually did. It also verifies that the file that was downloaded has not been modified in any way. As it sits there will NOT be any central authority on the keys used to sign things. So Self-signing will be allowed as long as you provide the community your signature. Starting in 1.13, with the loading system rewrite, users will be prompted to accept signatures of coremods. It is our intention to work with people like FTB, Curse, and others to make these signatures easy to use and manage. For example a user would say they trust FTB, and wouldn't be prompted for every coremod that exists in a FTB modpack. For the technical side you can read more about Jar Signing here: https://docs.oracle.com/javase/tutorial/deployment/jar/signindex.html 3) Coremods should be visible source. This will be a controversial standard, but my thoughts on it is that if you're screwing with someone else's code (which is the only reason to ever write a coremod), then you should be willing to show what you are doing. It is stressed that this is VISIBLE SOURCE only. It is not a requirement that you allow others to use your code, or modify and distribute it. It's simply that we can see it. The signatures and visible source are NOT designed to be security measures. As there is nothing preventing malicious code from being signed and a user accepting it. This is just the risk you run with Minecraft modding as you're running compiled code from random people on the internet. This is however designed to make the community more open and try and stem the number of coremods out there that have no reason to be coremods. Major Policy change: I am happy to officially announce a new member of the Forge team. Everyone welcome Mezz. His official responsibilities are to be the Pull Request, and Issues manager. Basically, he's the guy you yell at if your PR/Issue is rotting on github. He's the guy who is tasked with reminding me that they exists. He will be the one responsible for filtering all the PRs/Issues before they get to me. So I don't have to deal with telling you guys to follow the standards like making a test mod, posting logs, etc.. In addition, he is also the one who decides if old versions will have PRs accepted. Yes this means there will be a limited development system for older versions. How far back that means is ENTIRELY up to Mezz. However the rules are that ANY pr adding features for a old version MUST be applied and accepted for the current version FIRST. Save for features that would have no place in the new version. Example being adding a new achievements hook when the new version removed achievements. It will still be our official stance on this forum to only provide support for the Current version, and the previous version. However, if the community wishes to have a few dedicated people step forward and become our Legacy support team them I am willing to work with them and see what we can set up. The main reason we do not provide support for old versions is simply we do not have the manpower. So start helping out! Response From Sponge:

Unless something majorly screws up our installer CANT download corrupt libraries as everything is checksumed. If things DO error then we need logs because it will scream the error in the logs. It sounds like you're going through a hosting provider that is doing something rather wrong. So go talk to them. Beyond that, go update to 1.11.2 at least if you want support on this forum. As for what is a error deserving of being on github, if you're not a modder. Then you shouldn't be making issues. Errors must also be verified to be EXCLUSIVELY Forge's issue. 10 seconds of searching would of found the same issue on this forum, and google, as its not a bug on our end. Anyways this doesn't need to go on anymore, point is use the forums for tech support and don't argue with me on github when I tell you nicely that that's not the place for stuff -.-

Give a full directory listing. MD5s of the files you're using Exact command and working directory that you're running. Give some actual details. You say you're a server admin. Yet you provide nothing for us to even try and help you. As Cloudy has said, this issue is caused by the server not being able to find the minecraft jar file. The minecraft jar file MUST be in the current working directory and have the EXACT name "minecraft_server.1.12.jar" All of this is setup properly for you by the installer. Hence not our bug. Bitching about my 'professionalism' will get you no sympathy. I told you to go to the forum because its a PEBKAC error NOT a bug and then you argued with me so I locked it.

We do not support crawling out site.

User was banned for using a cracked launcher

Tamas just updated Mercurious so this should be resolved. Im going to push a ASM library fix in a few mins. Edit: Oh wait its the updater, ya he hasn't done that yet. He'll do that in a few mins.

I'm the one who updates MCP, I updated it a few days ago. It'll be released whenever. But ya, experimental builds are up. THEY DO ERROR and there is missing APIs. So be warned. It'll take a couple more days of work, just be patient.

1.12 is in dev, dont use it.

make your workspace literally ANY other folder except the project folder A workspace can not be inside a project.

Dont have your workspace in your project.

The old beta days are still on SF, Haven't gotten around to putting them up on files cuz honestly don't really care. If someone wants to pull them together in the proper maven format i could toss them on. But thats old jar modding days.. pretty evil.. I'd probably just add a separate 'archive' page.

Delete the coremods. And update to 1.11.2

You have installed bad coremods, stop using coremods. And update to 1.11.2.

1.6.4 is not supported on this forum.

First of, your resource pack is horribly broken, you should stop using it. Secondly, update to 1.11.2. I'm not sure what version you're on because your class names dont match any in the last few versions, but you're not on 1.11.2

What exactly are you downloading? Also you probably have .jar files associated with your archive tool. Just run java manually: java -jar {forge installer}.jar

There is a logs folder in my minecraft directory, we need FML-client-latest.log

Same thing, also it's a coremod, you shouldn't be using coremods anymore TMI got replaced by JEI which isn't a coremod. Use that

You installed vein minder for 1.8, you need the 1.11.2 version.

If you remove optifine post a new log. And you should update because you should always be on modern versions if you want people to give you support.

1) Update to 1.11.2 2) Remove Optifine {Its the cause of the crash}

The rider system was changed from a rider to a passenger based system. The entities positions are still updated in code there are a few places you can hook into. But no this exact function has no place to be coming back. There are other ways to do what you want most likely.

you missed the .jar in the file name

You don't That's a shitty thing to do in this community and anyone who does it should be chastised and their mod never used. There isn't much more anti-community thing to do then to actively go out of your way to hide what your mod is doing. Beyond that it is just makes people think your mod is doing something malicious. "What does ModX do?" "I don't know it's all obfuscated what are they trying to hide" "Must be stealing passwords or breaking things" You will get no help here in your efforts to be an ass.

You do not need to directly use proguard.