LexManos

The message at the top is just a gentile reminder that we provide this product for free supported by ads, and the generous community. However, you can bypass all of this by adblock, or using the direct links which are under 'Show All versions'

There is no fix, because THERE IS NO PROBLEM! It is working as intended!

No.. No it's not.. it's attempting to assign a variable. It's nothing to do with looking into a file or anything. Please look into the basics of variables, fields, and what assignments are. No... @ is just how annotations work. Go look into what annotations are.

`itemList` -> First, you should never name a class using lowercase as the start. You should read this: https://www.geeksforgeeks.org/java-naming-conventions/ If you're in the same package, it doesn't need to be public, but public is good for other reasons. Then you didn't actually reference the field, you need to understand the basics of referencing fields from other classes. is is class... oh wait no, you're talking about your original code. You can't have a class inside a method. Also, 'static' has nothing to do with 'nothing in it changes', it is a access modifier, it means that you don't need to have a instance of the containing class to refernece the method/field. You can call it directly. Yup, this will automatically scan the annotated class and register everything to the event bus. Making every annotated event function inside be called for the proper event. THIS IS A PROBLEM! Stop copy/pasting code from 'tutorials' if the 'tutorial' doesn't teach you WHY the code exists then it's a horrible tutorial and you should not use it. The @EventBusSubscriber annotation goes on classes, it then scans the entire class for any static method that has the SubscribeEvent annotation and automatically adds them to the eventbus specified in the EventBusSubscriber annotation. That annotation can go on ANY class, it doesn't need to be a class inside a class. So you could simplify your code a lot. Good, that's what SubscribeEvent does yes. Why do you have 'itemList.hair_fibre =' ? What does that do? Why are you doing it? This one is a little weird, you're making a helper method, that is being used in a inner class, in the parent class... Why are there so many damn classes in this file! Overall, I think you should look into learning some of the basic standards and practices of java coding. Namely access levels, how to reference things from other classes, what a nested class is. As well as the standard naming scemes, as if you ever post code for others to read, following these naming formats allows the reader to understand your code structure from any line. You also have not shown me anything the explains why you are trying to call anything from your 'main' code. Everything is done for you. Thats the POINT of the @EventBusSubscriber and @SubscribeEvent

Go through line by line, and tell me what each does, and why you put it there.

Why are you calling item registration from anywhere?

You have a lambda, inside a function, inside a class, inside a function, inside a class. Think there may be a problem with that?

Generate your JSON at/before build time Don't care how you do it. At runtime, the data should be static. This allows for better control, caching, management, and a ton of other things. Also, stop using upper case in your resource names. There is a reason MC explodes if you try to create a ResourceLocation for it. Edit: Oh god actually looked at your code, you're doing every thing wrong...

As far as I know there is not a mod-compatible way of doing this. But what you would have to do is load every region/chunk and convert it. It's not a simple process, and as I said, i dont know of any tool out there that does it correctly.

No, Optifine is closed source and we have nowhere near enough money to pay him to go open.

Apologies to those who have attempted to register and verify their email address in the last week. Something changed with out email settings, and well, we couldn't send the email to notify me that things broke. We have switch to a new SMTP service and things should be resolved. New accounts should get the verification emails now. Anyone with a pending account should be able to request a resend of their validation email {I couldn't find anything that let me do that in bulk}. Again, sorry for the issue.

Look in the logs folder, and give us the log files. This isn't a issue in Forge, something in your texture pack in providing a invalid texture, and thus getting the default missing texture, which is a purple and black checkerboard. We can't tell you what, as that would be in your logs. But remove your texture pack and you will be fine.

The data shown in the debug screen is the data that the client knows about. And the only data that the client knows about is the data sent over the network And the only data sent over the network is the data that can be serialized And the only data that can be serialized is the data with corresponding metadata values. So yes, The client only knows about what you tell it via the metadata.

Textures are not limited to 16x16, that's just the default aesthetic of Minecraft. It is recommended that you keep your textures square/rectangular and separate. And let Minecraft stitch them all together. However if you MUST use a pre-combined texture. You just need to set your UV's in your model file correctly. Such as Instead of using 0, and 1. Use 0 and 0.333333 if it's a 3 column texture.

1) You need to use the installer and make sure you run the jar in the correct folder. If it can't find the extra libraries it means that the libraries folder is missing. 2) You're running with Java 9+ this will not work for the version of Forge you're trying to run. Use Java 8

When someone who is good at rendering updates the GUIs. Feel free to help out.

some mod your have installed is spamming the console. If you use our logger it should tell you the class name it's coming from. But none of the logs anyone has provided have any spam at all. Best thing we can say is start downgrading mods one at a time to see if ti goes away.

"and I've been occasionally adding mods as I go" That is the issue, when you add a mod that effects world gen, especially the biome layer, you're going to run into these sharp edges. They are between old chunks that were generated before you changed the mods, and new chunks. There isn't anything you can do about this. Maybe go through your old world prune it down to just the things you want, and live with the border/manually make them nice after you stabilize your modpack.

Yes, it is, Forge's recipes are the lowest priority above vanilla itself. If you can't then it's a issue, and we can address it, however, our local tests all work fine. Anyways we can fix this, we do pragmatic recipe replacement generation. it's just a oversight.

"The mod I like isn't out, so no mods are out!" That argument doesn't fly. Anyways, This has been asked and answered.

Forge ModLauncher, and the 'Launcher' artifact in the download page are two different things. ModLauncher is the bootstrap tool that allows us to edit the vanilla classes during startup, it's the replacement for LegacyWrapper that we have been developing for quite some time. It is a more standardized API that was developed from the last 8 years of experience in the Minecraft community, as well as focusing on future java developments. The old one was not compatible with Java 9+, This one is, minus some technical issues that are on hold until Mojang updates their bundled Java version. The 'Launcher' download on our page, is Forge's utilization of that system. It is very important that Pre-ModLauncher code does not interfere with post ModLauncher code. So they are shipped as separate assets. All you, as the end user need to know about, is the Installer. Just run the installer, for the client use Mojang's launcher. For the server, run our launcher.jar.

Update to 28.1.16

16 should fix this, Having issues with java being really stupid with zip files. And making them dependent on your timezone and other things.

Think through your 'suggestions' and understand what you're doing. @OnlyIn is NOT something Forge adds, it is a marker to tell you that the method doesn't exist in the jar Mojang ships. If the annotation is there, it's because it IS needed to emulate the Mojang environment.

no, it's not. It's explicitly against Mojang's wishes, don't do it.