LexManos

They didn't find a way around it, they use the fact that Wolverness won't actually file directly against them because hes not that kind of guy. But the point is, no we are not going to build Bukkit's API into Forge. Mainly because its to restrictive for modders, and it has been fairly stagnant even before the DMCA so it'd be coding things in the wrong direction. Beyond that, I flat out don't have the time of patience to do it myself so it'll never happen. We've tried pushing for people to help write an Abstraction Layer but that didn't get any support. So here we are, modding like we do. As for permissions, which really is the only thing Forge lacks that Spigot/Bukkit 'provides'. There was a discussion a while ago about doing something like this. But it never got past the definition of 'context' which is kinda important.

Use the official Mojang launcher.

That is not what I asked for -.- Speak with your server host and have them walk you through it.

1) Stop using 1.7.10, the current version is 1.12.2, if you want support on this forum use the current version 2) This is not a error it is fully working as intended.

Just as a note, when you install Forge you will see 3 'mods' installed. Forge, FML, and MCP. The FML/MCP mods are there just to give credit where credit is due as those are projects necessary to create Forge. They are not actual mods that run anything. Just entries in the mod list to be nice and give credit. {Well, FML runs things, but its all the Forge project now}

Well yes.. because that's not a valid directory. And why are you trying to add cpw to your deps? You probably want: http://files.minecraftforge.net/maven/cpw/mods

Post your full log file, and show exactly how you're running the jar. Installing the client to the %AppData%/.minecraft folder (which is a hidden folder by default) is intended. As thats where the launcher looks for things. Installing the server can be done anywhere. *something* you're doing is telling the game to look into the D drive. We do not know what.

Show us exactly how you're running the server. You're most likely not running it in the proper working directory. the [forge jar] part should have NO directory paths. The only way this can happen is if it can not find the 'minecraft_server.1.12.2.jar' in the current working directory.

A few notes: 1) You can't always trust the first oredict entry to be a valid itemstack. You may need to expand it to a random one. 2) https://github.com/MinecraftForge/MinecraftForge/blob/1.12.x/src/main/java/net/minecraftforge/common/crafting/IConditionFactory.java

What error exactly does it say? There are many reasons it cant read a jar file. Possibly permissions issues, or you've downloaded corrupt jars. Seriously provide your logs. Also update to 1.12.2.

Then post you log.

Just use your json files.

He said run the INSTALLER jar not the UNIVERSAL jar.

It's a perfectly valid use for deprecated. Everyone has their own code styles. Java doesn't have a proper internal or overide only annotation. So this is what we have. Deal with it.

1) Don't not for 1.10, you should always be on the the latest mc version 2) don't use mcp, that's only for advanced people with explicit need for it 3) there is no thing as smc I'm going to assume you meant src and that has been outdated for years. Everything is i n a proper package now. 4) you NEED to know the basic of java, your use, and how to run commands before nodding. So start there.

There is no "they". As stated, if nothing has changed in your MC setup then most likely its some other software you have installed like a Firewall or Anti-Virus.

There is no legacy compatibility issues if Minecraft itself forces the change. Such as the >64 and lcasing as they did in 1.12.2. Stop being a smartass. And no, there is no good way to determine if you're in a 'Dev environment' If you find a way that is 100% reliable and doesn't rely on hacky hacky shit. Then sure we can think about it because A LOT of things could use a Dev Time explosions.

For legacy reasons we can't we just bitch about >64 and not lcased. https://github.com/MinecraftForge/MinecraftForge/blob/f49411745352fce16f633e05b250a87f23048166/src/main/java/net/minecraftforge/fml/common/FMLModContainer.java#L136

The Forge log WOULD show those errors are networking errors such as that are logged. But if thats the case then you seem to of given us the wrong computer's log files. But if as you say that you have been using this setup fine for over a year, and haven't changed anything Forge or Mod wise. Then its something else thats the issue. New version of your firewall, or AV blocking things possibly. The launcher shouldn't have anything to do with it as at the end of the day you're just launching the same game.

Your JSON looks fine, and should load fine. Or error if its not the proper syntax. Its more likely that you're not loading it at all because the file isn't in the right spot. If you're using a IDE be sure to clean the workspace and make sure it rebuilds the 'bin' version. Eitherwise, post your source/exact paths/etc. And yes, you should use a longer more unique domain name.

The 404 errors are perfectly fine and inteded, if you can launch the game then we need the FML logs. And reading the ones you provided: [11:45:22] [main/INFO] [FML/]: Forge Mod Loader version 13.20.1.2386 for Minecraft 1.11.2 loading You should update to 1.12.2 The rest of your log isn't useful. It doesn't show anyone trying to connect, or the 'opening to lan' message.

Sadly we can't it requires a major re-write of the launching mechanism that allows us to do the core patching of Minecraft. There isn't a way to apply this retroactively. We're hoping to have the new system in place for 1.13+ which will definitely land before September, so there you go.

Seriously, Use the event not the static registries. Timing of registration is important. So stop doing it in random places. I was tempted to name the event 'RegisterYourStuffHereAndStopBreakingEverythingElseSeriouslyStopRegisteringYourCrapInRandomPlacesItBreaksThingsAndHoldsUsBackFromBeingAbleToDoCoolThingsThatWeveBeenWantingToDoForFourYearsNow' but I decided against that as it was a bit long

Your log is running Java 9. And the only cause of this issue is you running java 9. So be sure.

http://mcforge.readthedocs.io/en/latest/events/intro/