LexManos

It wasn't Mojang who shut down bukkit it was a member of Bukkit's community. The current solution is Sponge. As for old 1.7.10 stuff, you should really update to current versions. As for using server side only mods, it all depends on the mod. They need to be written in a way that says they are server side only. Don't know about WorldEdit specifically, but I would assume if they have ServerSide only Bukkit version, they have a ServerSide only Forge version as it's similiar codebase.

The problem with most alternative mod loaders, is that they are created out of spite with "Fuck Forge" as their motivation. But then they use our tools, our data, and our work to make their system. That's the thing that pisses me off about things like Rift. I have not looked at Fabric so i can't comment on what they are doing, or if they are doing it correctly/legally. However, I would also advise against using any loader that "gives the hooks to the users", by "exposing" mixins and encouraging the average user to use it. Because that flat out won't work. The reason Forge has compatibility with so many mods is because we've cultivated all the internal hooks as clean changes that make it so modders DON'T have to break things in MC code to make their mods work. So you can get a couple nice mods yes, but it'll become difficult when you start trying to create modern mod packs. As for updating to snapshots. I update the mappings internally when I get time cuz I like seeing what has changed. I would LIKE to make those mappings public but it isn't worth doing as they are not the highest quality and we loose a lot of information. I am looking for people who are willing to help create open source versions of some of the internal tools I use {which I did not create and thus is not my place to release} as well as a better three way binary mapping generator.. If anyone actually wants to help out on that, hop on discord either Forge's or sponge's and we can talk... Anyways, using 3rd party smaller loaders just to explore the new vanilla code is fine. But do not expect stable or useful releases from those.

Damageable Tools were never intended to be part of the dictionary. People just used it because it worked. So we supported it until we couldn't anymore. The changes done were done to comply with vanilla, which no longer has a wildcard value, standards and features. If you need a damageable tool, use a custom ingredient.

Please try and answer your own questions before asking....

https://www.computerhope.com/issues/ch000743.htm

your scala libraries are corrupt, delete them and re-run the installer.

delete your world and rerun it. Most liekly its because you've swapped registration order so many times in dev that it saved the ids out of order. Thats the entire point of Forge tho, to control the IDS and manage them. There isn't a good way to sort the items, and honestly it shouldn't be that big of a deal. And we can't change how they are sorted in Forge because people complain in vanilla. So, just to reiterate, the items/blocks WILL be assigned ids in the order they are registered. This registration order persists between world loads. So if V1 of your mod registers BlockA Item1 Item2 And V2 registers BlockA BlockB Item1 Item2 Item3 The result of upgrading the world would be BlockA Item1 Item2 BlockB Item3. BUT in a new world it'll be BlockA BlockB Item1 Item2 Item3 And no, there isn't anything you can do about this.

JEI *should* sort things by modid or something other then numerical ID {which is the default sort of the registry, cuz Mojang felt like doing it that way} But JEI doesn't have to do it that way. Also, for creative inventory, use your own tab and group them that way. You USED to have to assign all ids, and there were id conflicts all over the dang place. This is one of the main reasons why things were moved to hiding the ids from you. You shouldn't need them anymore.

there could be quite a few reasons, notably that others may have those ids already. However, why does it matter? You as both a modder, and a user should not care about numerical IDs, so... don't.

He means launching, he has no idea what he is talking about. It's impossible to do, so no.

Mojang designed the recipe system to not work well with stacked items. A lot of assumptions, and things similar to the guide book simply do not work. If you control the container, you have the inventory change event, but nothing that should be in recipes.

Ya, sadly it was the latter. So I spent a week or so re-writing everything he has done and getting it working. FG is functional, it needs some quality of life stuff, but it's done enough where I am back working on patch updates in Forge. Now my job is working through the massive crapton of patches that Forge has. My current 'old' directory: Forge is building fine. I finished that up last week. We just arnt publishing to the main download page because we don't want end users downloading things yet. As it's still being worked on. As for other things, cpw has work to do on ModLauncher/FML stuff. And he won't have time to work on that until chirstmas vacation because of real work. But, he is being kind enough to take time out from having with his kids for christmas to do some work on Forge. So Ya... things are being done, you can see what what is being done by watching the git repos. Things are out far enough where modders can start testing things. Giga has some stuff to do to make the MDK a bit more userfiendly. Stuff is progressing, and we're not hiding it. There is no ETA or percentage complete because those are literally impossible to calculate because we are working on things as they come up.

Possible, but never going to happen. Without reiterating things i've stated thousands of times, its not feasible and it would piss off EVERYONE.

Optifine is the same issue yes, it improves SOME users, but in our testing breaks things on a lot more. If it works for you good, but don't believe it is a magic fix-all thing. Also, personal opinion here: I don't like that its closed source and hacks around internals magically, i'd much rather SEE what it is doing/claiming to do.

Since it's been brought up, gunna pimp out my Paetron for those who don't like the ads. Money is a necessary evil, sorry. Link in my signature.

Don't trust everything you read on the internet kid. Especially of it's a magic mod that suposidly increases MC performance. There is a reason why Speiger has been banned from not only Forge, but many other major MC projects. Yes, Forge keeps some extra data about the textures in memory. This is to speed up rendering, lighting, and the like. There is a triad off of some extra memory usage for massive decreases in cpu usage. And at the end of the day, RAM is cheap, CPUs are not. Also, The guy who wrote the changes Forge does is now actually employed at Mojang rewriting their rendering engine. So i'd trust his code over Speiger's. The same goes for any other "performance" mod you see out there. There are good reasons they arnt officially part of Forge. Most of those mods break other mods, simply because the deep level of control that mods have over their own data and MC.

Or if you dont want to use Twitch, just run the Forge installer from our site. Run install client for running client side/single player. And put mods from curse in the mods folder.

That what we will be doing for 1.13, the first few builds will only have the bare bones of what we have gotten done. But we arnt working on FORGE itself right now, we're finishing up the installer, gradle, building, etc... All the NON-Forge parts of the modding ecosystem. Once those are done and good to go, then we'll start forge builds and start working on Features. As it sits there are only a few things left, the most nosed being IntelliJ run configs and TESTING. I've been public about this on my twitter, so those who wanna help can help., if they know how.

And this kids, is how NOT to ask for help.

You can't get something that doesn't exist yet...

You must use java 8

Never gunna happen.

I have no sympathy for you players who use Netease, their entire business model is bad and abuses the hard work that we here at Forge, and other modders do. If they want to start complaining that I don't produce Forge fast enough, then they can start helping out. But no they just sit back, toss DRM onto things, and just rake it in. It'll be done when it's done.

If it was from our official site, then it's fine. Windows likes to say anything it detects as a executable file, that hasn't paid them a stupid amount of money to be on their whitelist, can harm your computer. Because it can, even stuff on their whitelist can, any executable code you download from the internet can harm your computer. But if you trust the people you're getting it from, then you just ignore that. Always be on your guard, make sure you're getting what you expect from the host you expect. We also provide the signatures of each file on the downloads page so people can verify that it didnt get corrupt while downloading.

Alright, i've skimmed this but the last part with recommending people use @Optional is just flat out wrong. It wouldn't 'not run' it would be stripped from the class. Thus any code calling it would error. Using ASM hacks is DISCOURAGED. At the end of the day all you have to do to make your code have a soft dependency on anything else, is simply not load the code with the hard dep unless you know the dep is satisfied. Have event handlers from other mods? if (Loader.isModLoaded(modid)) BUS.register(new DepSpecificEventHandler()); Have caps that could not exist at runtime? @CapHolder public static final CapabilityHolder<Foo> FOO_CAP; private Object myFoo = null; TEInit(){ if (FOO_CAP != null) myFoo = new Foo(); } It really isn't that difficult. The JVM doesn't know a class exists unless the code referencing is invoked/resolved. If statements are usually enough to prevent this, if that doesn't work {something deeply resolves the code} then you can hide it even more with a Supplier.