warjort

As was said above. If you are using non-api classes at compile time you are doing it wrong. The curios discord is the place to ask.

If this is the full log and there is no crash report, show your launcher_log.txt

You don't even show the error. You truncated it. All I can tell you is it is one of these mods with a broken/conflicting mixin Check you have the latest version of these mods.

The ones that were added by the dodgy software you downloaded that redirect your network requests away from mojang's site to who knows where? There are no other entries in your hosts file.

It's in the comment of that *deprecated* method.

There are many different ways to do this. The simplest would be entity.setCustomName() see NameTagItem. Another would be to override renderNameTag() in your EntityRenderer if you want to keep the stats separate from the custom name.

Looks like you don't have forge's maven in your plugin repositories? example from the mdk: https://github.com/MinecraftForge/MinecraftForge/blob/1.19.x/mdk/settings.gradle

Looks like an issue with DynamicSurroundings, check you have the latest version then contact the mod author.

Remove those invalid entries from your hosts file then restart windows and try again.

ItemBlockRenderTypes.setRenderLayer() but as it says there, you should put it in your block model json instead.

It uses it for the particles and determining the texture to use. You can use it for the actual entity rendering. I was just pointing out the pattern for setting the color at entity creation time and getting that data to the client.

Looks like an issue with the graveyard mod, check you have the latest version then contact the mod author.

Click "show all versions" then next the installer you want to download is an "i". Hover over that for the direct download link. The real fix is to uninstall your broken browser plugin(s) and/or clear your browser cache.

I know virtually nothing about fluid rendering, but why wouldn't you retrieve the fluid color "lazily" either when you create the projectile or less efficiently during the rendering? e.g. see how the arrow handles the potion color for tipped arrows (ID_EFFECT_COLOR).

The code for the bow is hardcoded, see AbstractClientPlayer.getFieldOfViewModifer() But you can do your own similar logic by subscribing to ComputeFovModifierEvent

The same code. Those ItemProperties.registers needs to be called within an enqueueWork() so they run on the main render thread instead of concurrently with other mods doing the same thing.

Please start your own thread.

I linked it above, you need to change Items.BOW to item - ItemProperties.register(Items.BOW, new ResourceLocation("pull"), (itemStack, level, entity, i) -> { + ItemProperties.register(item, new ResourceLocation("pull"), (itemStack, level, entity, i) -> {

That is a generic windows error code which means "Application Hang". Like when it pops up the window saying "Application is not responding".

That's your prerogative, or you could post your debug.log that actually contains the error with the teleport. Instead of doing the obvious, you chose to argue.

On the contrary I like helping people. What I dislike is lazy people that expect us to do all their work for them. You clearly didn't look at the logs before dumping them on us and you even said in your original post that you weren't sure they were even the correct logs. What are you going to do when you publish your modpack for others to use? I hope you don't intend dumping all your users bug reports on us. As I have said to others before, if you don't have the skills to build a modpack (which includes reading and understanding errors), use a prebuilt one by somebody who does.

Optifine issue, make sure you have the correct version of optifine compatible with the version forge you are using.

Nope. Your debug.log ends during the early bootstrap. It hasn't even loaded the mods let alone loaded the world in which you could crash during a teleport. I will take your advice and ignore your posts in future since you clearly don't appreciate the help you are given for free. I ignored this post before (like others probably did) because it was unanswerable and only responded when you "bumped" instead of considering why it might be the case nobody answered.

down 🙂 if you can't even be bothered to post the correct logs there is no way to help you.

Your question is unanswerable in its current form.