warjort

This link has a guide for 1.16 -> 1.17 including a tool for semi-automating it and a reference to a bot on the forge discord for getting new names from old names. https://gist.github.com/50ap5ud5/beebcf056cbdd3c922cc8993689428f4 The 1.19 changes (including another tool) are linked here: https://forums.minecraftforge.net/topic/114502-forge-411-minecraft-119

I don't think its documentated, but you need to return a new ItemStack not the original. Something like: @Override public ItemStack getContainerItem(ItemStack itemStack) { // Copy the original var result = itemStack.copy(); // Damage it result.hurtAndBreak(1, ForgeHooks.getCraftingPlayer(), player -> { if (player != null) { player.level.playSound(null, player.getX(), player.getY(), player.getZ(), ITEM_BREAK, player.getSoundSource(), 1.0f, 1.0f); } }); return result; }

Create for 1.18.2 requires at least forge 40.1.60 https://github.com/Creators-of-Create/Create/blob/0c5ccf38ee15f446f385290f2238f2ae975681cd/gradle.properties#L11

Post a link to your debug.log

The problem is you haven't told curseforge that it needs to enable the debug.log for forge. It is a toggle button in the "advanced" section. Curseforge calls the jvm arguments "additional arguments". It's at the very bottom. Anyway, I think your problem is with the create mod, see the link to the issue I posted above. You should be speaking to them on how to fix it. If the issue is only with LAN games, you can try setting up a real server.

Your behaviour class runs on the server. While the mobInteract runs on both the client and server. https://forge.gemwire.uk/wiki/Sides So you are only modifying that value on the server. But it needs to be on the client for rendering. You should define the petrified flag like you have the cloak color so the data is synched from the server to the client.

That doesn't contain an error either. It doesn't show you starting minecraft. Did you restart the launcher after the crash? That will clear the log. Also, do you have a file beginning hs_err_pid in your minecraft folder that is from the time of the crash? If you do, don't post the whole file just post the first 20 lines so we can see the error.

That's immersive engineering doing it for its hemp plant.

You can ignore it. It's not a real error. It's mixin trying to tell the mod developer they should specify which versions of mixin they support. Or you can report it to the mod developer.

Youd didn't post the debug.logs Those are the latest.logs which doesn't show debug information. Since it looks like you are using curseforge, you need to enable the forge debug.log in curseforge's minecraft settings. Anyway, one of your logs contains this. Which looks like this create issue reported by somebody else: https://github.com/Creators-of-Create/Create/issues/3973

Your problem is you are using java 19. Mixin doesn't support that. Use java 17 instead.

Refer to the optifine download page for their compatible versions of forge and optifine (including preview releases).

Post a link to your debug.log From the error, I would guess one of your mods has bad (probably empty) version information in its mod description. The error message doesn't say which one.

The launcher_log.txt is in the .minecraft folder not the log folder. Or see my footer for curseforge. It's the log for Mojang's launcher.

The details of what you are asking are off topic for this forum. This is a support forum for answering specific questions, not teaching or mod design advice. For particles, look at the section named particles here: https://forge.gemwire.uk/wiki/Main_Page How you draw them is up to you in the render() method of your Particle class. For drawing a ray of light you might want to look at how vanilla does BeaconRenderer.renderBeaconBeam() or a mod like Botania's mana animation Animations are done by changing data in the tick() method then referencing that in the render() method. The base Particle class already has code for moving particles around using "physics". see Particle.tick() The DE energy core is a BlockEntity which has a BlockEntityRenderer and client side ticking for doing custom rendering/animation. See the previous link for topics on those. If you are new to modding, I would suggest you start with simpler examples. Don't try to run until you can walk as the saying goes. 🙂

I am reluctant to get involved in this thread since I know virtually nothing about custom model loaders. 🙂 I just want to suggest you look at what ForgeClientMod ClientForgeMod does. This is just another mod, the only thing special about it, is that it is preinstalled with forge. e.g. it creates the composite loader mentioned above, along with others. You might also want to look at: https://docs.minecraftforge.net/en/1.19.x/rendering/modelloaders/#custom-model-loaders

The event is fired when ItemStack.matches(from, to) == false so yes, durability changes mean the event is fired. You can do your own additional filtering in the event e.g. using ItemStack.isSameIgnoreDurability(from, to) or one of the other equality tests in the ItemStack class.

There is still no error in that log. Post the launcher_log.txt, Maybe that has logged something? To try without optifine, just remove the jar There is a message about it finding 2 copies of world edit. It looks like it selected to use the most recent version correctly.

https://forums.minecraftforge.net/topic/117960-1192-trying-to-give-player-creative-flight-in-survival-mode

You are trying to use the 1.18 version of twilightforest with minecraft 1.19 download the correct version for your minecraft: https://www.curseforge.com/minecraft/mc-mods/the-twilight-forest/files/all?filter-game-version=1738749986%3a73407

You need to show the relevant code. Obviously, there is something wrong with your model or texture. Guessing: Your texture actually contains black pixels in the parts you select? Others would be you are not setting the RenderType correctly or you have cullface wrong in your model (although it doesn't look like you can see through the world in that image?)

That way of doing it is very inefficient. The PlayerTick event is called on the client and server at both the start and end of each tick. You should be checking event.side and event.phase to limit when you do things. The onUpdateAbilities() sends a network packet to the other side. So, your code would be sending 4 network packets per player per tick. Here's a more efficient way: @Mod.EventBusSubscriber(modid = MODID) public class Events { @SubscribeEvent public static void equipmentChange(LivingEquipmentChangeEvent event) { if (event.getEntity() instanceof Player player && event.getSlot() == EquipmentSlot.OFFHAND) { // WARNING: Proof of concept code not the correct logic player.getAbilities().mayfly = event.getTo().is(Items.DIAMOND); player.onUpdateAbilities(); } } } That event only happens on the server and only when the equipment actually changes. The above works for me, using diamonds in the shield slot as my trigger. WARNING. The above logic is not complete. One example is, it would remove flight from creative mode players when they remove the diamond. Another is it doesn't set flying=false when the diamonds are removed.

I can confirm the EntityAttributeCreationEvent is fired during registration before the configs are loaded. But you don't have to code it that way. You can set a default max health in that code. Then in your entity constructor you can apply a permanent attribute modifier from your configuration. I am the wrong person to talk about this stuff. I generally avoid config files like the plague. They are just a way for users to break things. 🙂 And only multiply the amount of testing you have to do with different combinations of config options.

Issue with the oculus mod. Check you have the latest version then contact the mod author.

The error says there is a problem with your corail_woodcutter-server.toml configuration file It should be in your saves/<SAVE-NAME>/serverconfig/ directory If you don't have a backup of this file, you can delete it and it should recreate it with default values.