ChampionAsh5357

The version you are using is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. Currently supported versions are 1.19.2 (Latest) and 1.18.2 (LTS).

The version you are using is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. Currently supported versions are 1.19.2 (Latest) and 1.18.2 (LTS).

If you want to send it to everyone, you'll need to call PlayerList#broadcastChatMessage, which you can obtain from the MinecraftServer from a ServerPlayer (see the sides doc on how to know what side you are on). If you only want to send it to yourself, then you can call ServerPlayer#displayClientMessage.

You're going to need to provide more information as this does not mean anything. Simplest thing to do is to invalidate caches, which you can google for your IDE, and see if that fixes any of the issues.

You provided the method you need to call, so why are you calling something else? Just call that method you mentioned.

Entities and block entities are essentially uploaded and rendered to the vertex buffer every frame and, as such, needs to be constructed over and over again. They cannot be batched and cached into a single call like baked models are. That's why, unless there is particularly complex logic or there are animations, it's recommended to use baked models and custom model loaders. Technically, there are ways to fix this by doing proper OpenGL handling manually such that the models are uploaded once and then transformed and placed within shaders, but that is out of scope and goes against Minecraft's rendering system, so that would not be supported here.

Oh, so it is just a tmux (terminal multiplexer). Still would be a non-Forge related question in any sense.

The version you are using is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. Currently supported versions are 1.19.2 (Latest) and 1.18.2 (LTS).

Ah, fun. We only support Forge here, not third party extensions. Please ask wherever the loader provides support.

Call it in `#getAddEntityPacket`. You'll basically need to send it pretty much every tick, otherwise the data may be wrong at certain times. As for how to: https://docs.minecraftforge.net/en/latest/networking/simpleimpl/

Just copy the properties of the head part to the hat. You can look at how the humanoid armor layer does it.

Don't use java models. They're only recommended for entities. You can even do most of their logic with custom model loaders. That's because they can't, at least when in a non 90 degree rotation. You can use translations and scaling to get around that limitation, but you'll have to work with it. You can use a different object loader (such as OBJ) if you prefer, but if not, then it's simply trial and error.

We do not support making launchers. We only support developing Forge mods and playing Forge mods for the latest and LTS versions.

What is a screen? This seems like a linux specific question where you need to have the process attached to the background or not the current session terminal. You could probably just use tmux and run the command in there.

Provide the entire debug.log. Otherwise, weedle out the mods into those that are crashing and those that aren't by removing mods in batches.

Show your folder structure. Where is the mods folder? Additionally, OptiFine only works with very specific versions of Forge, so you should probably check that it's supported.

Ask alternos support. This is probably an issue with them.

What are damage particles? The particles from the potion effect? The particles from when you crit a player?

The debug.log is incomplete as it doesn't contain the error. You may need to look at the launcher output and copy it. Additionally, if a mixin error doesn't happen in dev but in prod, it most likely has to do with your jar not have a refmap. In any case, you should probably ask sponge where they have mixin support about this or ask in the #non-api-modding channel on the Forge discord. You'll probably receive better help there.

It's fine. Though, I am unfortunately the worst person to ask. I tend to go through the vanilla source to figure out what's going on and work backwards to develop and improve it, only asking questions when there isn't a well defined path to backtrace. Typically, it's the same as programming any other work: think of a concept, develop the usecases, build them out, integrate them with the system you are working with. If I ever have loader specific questions, I typically ask here or on discord to receive answer. That's not to say there isn't any good repositories for sources. I just typically don't look at them since everyone has their own programming style, some of which may be bad in modern versions in Minecraft.

You may have a misassociated jar file. This can typically be fixed by downloading and running Jarfix.

The version you are using is no longer supported on this forum. Please update to a modern version of Minecraft to receive support. Currently supported versions are 1.19.2 (Latest) and 1.18.2 (LTS).

"type" in the level stem represents the dimension type. It doesn't have anything to do with the surface rules. You can look at slicedlime's vanilla worldgen jsons for examples.

You're not understanding how the bow works. But even if so, you only have two models, so the bow doesn't make much sense. You basically need the default model, which I assumed is your relaxed, to have an item override to when a value is one, which can be determine by the item property, you use a different model. Your default model only needs to show the states it can switch to, not every possible state.

Documentation is written by the community. Most classes in Forge are fully documented for their purpose as a public API; however, as Minecraft is obfuscated and separate code, as you have pointed out, it is typically left to the community to document these procedures. Forge does have the official docs and the community wiki; however, both of these sites are more or less community driven, the former with extra checks provided by members of the documentation team which have time to look over and verify the topics. Currently, I am the main active member who contributes to these two sites as a maintainer of both, but I have not had a lot of time recently to add new pages as I typically like to conduct as much research as possible to make the documents robust enough for a basic understanding of the system. Additionally, it takes time when Forge updates between Minecraft versions that I need to review and reverify all the information again, which is a separate undertaking. I've spent the past few months slowly working on menus and screens actually, but trying to document the information for people without prior knowledge is difficult along with the quantity of information. Ideally, more people could contribute such that I can take a more review-based role, but that depends on the community as well. If you're willing to contribute after getting an understanding for yourself, make a PR to the docs or make edits on the wiki, it would be more than helpful.