warjort

I'm pretty sure your problem is actually something to do with your texture being 64x64 instead of the normal 16x16? https://github.com/Blurr0-0/TestMod/blob/master/src/main/resources/assets/test_mod/textures/particle/gray_lego_stud_0.png I tried your mod and it looks to me like 3/4 of the object is buried. i.e. pixels 17 to 64 Rendering is not something I know very well. So I don't personally know if minecraft supports such a thing or what you need to change to make it work properly. Maybe somebody else on this forum can help you? But you might get more insight if you ask on the discord of one of the mods that messes with graphics e.g. rubidium. Otherwise you will probably just have to read the particle rendering code to see how it would handle an oversized sprite.

Post your launcher_log.txt to confirm it actually is an issue with your graphics driver. But if you look at the other links on that thread people have also fixed the problem by downgrading their driver, i.e. NOT using the latest version. Ultimately you need to speak to AMD or whoever sold you your computer for help with the graphics card configuration.

https://forums.minecraftforge.net/topic/123710-minecraft-1194-forge-crash/

Or remove all those mods and add them back one by one to try to locate which one(s) is the causing the problem.

You have a lot of mods that are failing with messages related to create. e.g. This probably means you have mod(s) that are not compatible with your version of create. The logs/debug.log probably has more information? But you need to contact the mod authors for help (after you check you have the latest versions).

Issue with immersive portals. Contact the mod author.

The forge version is tied to the minecraft version. e.g. forge 45 is minecraft 1.19.4

You have the 1.19.3 version of immersive portals. But are using minecraft 1.19.4 There is no 1.19.4 version of that mod (yet) according to curseforge: https://www.curseforge.com/minecraft/mc-mods/immersive-portals-for-forge/files But if you know which mod is causing the problem, you need to contact the mod author. These are the forge support forums. We can only point you to the mod causing the problem. We can't fix the mod.

If a mod is available twice, forge will just choose one of them at random (well actually it will choose the latest version, but in this case they both have the same version). Remove the one from your mods folder.

You don't add mods to your mod folder in the dev environment - unless you know it is the deobfuscated jar with the correct mappings. Correct way: https://forge.gemwire.uk/wiki/Dependencies

https://forums.minecraftforge.net/topic/123710-minecraft-1194-forge-crash/

https://forums.minecraftforge.net/topic/89239-excessively-asked-questions-eaq/#comment-415820

https://forums.minecraftforge.net/topic/89239-excessively-asked-questions-eaq/#comment-415820

You have a lot mods that are not for minecraft 1.19.4 e.g. is which is not the 1.19.4 version of the mod https://www.curseforge.com/minecraft/mc-mods/balm/files You need to check when you download your mods that they are for the version of minecraft you are using.

If you want help with a specific mod, you need to contact the mod author.

One of your mods is not registering its entities properly. The logs/debug.log might have more information?

Some conflict between yamamoveset and epicfight. Check you have the latest versions then contact the mod authors.

https://github.com/VazkiiMods/Quark/issues/4196 https://www.curseforge.com/minecraft/mc-mods/quark/files/4551115 - supposed to be fixed in the latest version

Curseforge says that mod is no longer maintained. https://www.curseforge.com/minecraft/mc-mods/rubidium-toolkit

You don't set the bounding box directly - unless you have your own custom move() implementation. Like entities you set the position, velocity and size and the bounding box is recalculated for you as it moves or you manually change its parameters. See Particle.tick(), move(), setSize(), etc. for how it works. It's hard to say what your problem is without having all the information. Don't post incomplete snippets of code in the forum, put a simple project on github that reproduces your problem. I would guess (I shouldn't have to guess) it is that 2x quadsize since that is only used for rendering? While as I said above, it is the size (which proxies through to the min/max of the bounding box) that is used to (re)calculate the bounding box for collisions.

Code for 1.18.2 that registers a BlockTag LootItemCondition. https://forums.minecraftforge.net/topic/113816-1182-method-for-iterating-over-blocks-belonging-to-a-tag/#comment-505993 It should be the same for 1.19 except If you use the most recent versions of minecraft the ResourceKey is in the Registries class instead of Registry.

https://www.curseforge.com/minecraft/mc-mods/alexs-mobs/files/3785937 alexmobs-1.18.2 is for minecraft 1.18.1 according curseforge.

https://forums.minecraftforge.net/topic/89239-excessively-asked-questions-eaq/#comment-415820 That means the mod wants forge 36 to 39, i.e. minecraft 1.16.5 to 1.18.1 While you have forge 40 or minecraft 1.18.2

https://forums.minecraftforge.net/topic/89239-excessively-asked-questions-eaq/#comment-415820