warjort

Looks like an issue with tombstone, but probably caused by a different error not shown in the crash report.

One of your mods has modified the player to add an entity Attribute. But it hasn't registered/created that attribute properly. The error message does not say which mod is causing the problem.

Looks like an issue with Epic-Knights-Armor-and-Weapons, contact the mod author.

There are 2 things listed in your client log One seems to be an issue with the plasmo mod. You should check you have the latest versions on both the client and server, then contact the mod author. The other looks like this issue? https://bugs.mojang.com/browse/MC-252216 But that doesn't look like it is fatal error. It is marked as "DEBUG" output by Mojang.

That is the server log. It just says you were disconnected: We need to see the client log. The launcher log you posted is from 30 minutes before the server.log?

You can use the EntityJoinLevelEvent and check if it is an ItemEntity to see what NBT its ItemStack has. You can also see if your NBT survives saving and reloading the game. If it does not, you are not modifying the correct ItemStack on the server.

@Override public CompoundTag serializeNBT() { CompoundTag nbt = new CompoundTag(); CompoundTag inventoryNbt = new CompoundTag(); for (int i = 1; i <= slotCount; i++) { inventoryNbt.put(String.valueOf(i), pocketInventory.get(i - 1).saveNBTData()); } nbt.putInt(SLOT_COUNT, slotCount); nbt.putLong(STACK_SIZE, stackCapacity); // HERE you put your inventory in a subtag nbt.put(POCKET_INVENTORY, inventoryNbt); return nbt; } @Override public void deserializeNBT(CompoundTag nbt) { this.slotCount = nbt.getInt(SLOT_COUNT); this.stackCapacity = nbt.getLong(STACK_SIZE); CompoundTag inventoryNbt; pocketInventory = NonNullList.create(); for (int i = 1; i <= slotCount; i++) { // HERE you are trying to read the inventory from the top level tag? inventoryNbt = nbt.getCompound(String.valueOf(i)); pocketInventory.add(i - 1, new DimensionalStack()); pocketInventory.get(i - 1).loadNBTData(inventoryNbt); } }

- Removed for bad formatting -

We have no psychic powers. Show your logs/debug.log and the crash report. If there is no error in the log or crash report, show the launcher_log.txt in your minecraft folder. You can post large log files to https://gist.github.com And if you are using curseforge you need to enable the forge debug.log in its minecraft settings. As it says in the sticky post at the top of this forum: https://forums.minecraftforge.net/topic/89239-excessively-asked-questions-eaq/#comment-415820

Just leave it alone, it's not a real error.

ooooooopppppptiiiiiifineee issue. 🙂 Check you have a version of optifine that is compatible with the version of forge you are using.

optifine issue, check you have a version that is compatible with the version of forge you are using.

That's why there is an error logged. 🙂 It just means the mixin transformer can't validate if the config is compatible with its current version. It will try to use it anyway, so unless you see other errors there is no problem. You can still report it to the mod author so they can stop the log spam. You shouldn't try to modify mod jars yourself. They often have cryptographic signatures which means they won't work properly if you modify the jar.

Looks like an issue with applied energistics. It seems to be trying to use the deobfuscated name of a method? Check you have the latest version then contact the mod authors.

Looks like you are missing macaw roofs mod Macaw roofs again Looks like you are missing the mantle mod.

8985 was fixed in forge 43.1.2, you have 43.1.1 https://maven.minecraftforge.net/net/minecraftforge/forge/1.19.2-43.1.25/forge-1.19.2-43.1.25-changelog.txt

You are missing the AutoRegLib mod.

https://docs.gradle.org/current/userguide/declaring_repositories.html#sub:maven_local https://docs.gradle.org/current/userguide/declaring_repositories.html#sec:case-for-maven-local

Ok, you certainly get a list of possible drops if you ignore that a custom LootItemCondition can do things you can't simulate, e.g. only drop an item the first time a player kills an entity. But a modded entity is allowed to override that method, so it isn't necessarily the logic that is being used for all entities.

See LivingEntity.dropFromLootTable() But I don't see how that helps you? Loot tables contain random drops/custom LootItemConditions. No 2 calls of that code will give the same items in the general case.

LivingExperienceDropsEvent LivingDropsEvent The latter does NOT differentiate the source of the drops, it just gives you a collection of ItemEntitys.

Caused by: java.lang.NullPointerException: Cannot invoke "com.google.common.collect.ImmutableMap.entrySet()" because "ladysnake.illuminations.client.Illuminations.OVERHEADS_DATA" is null at ladysnake.illuminations.client.render.entity.feature.OverheadFeatureRenderer.<init>(OverheadFeatureRenderer.java:26) ~[illuminations-forge-1.19.2-0.0.1.jar%23158!/:1.19.2-0.0.1] {re:mixin,re:classloading} Looks like an issue with the illuminations mod. Given the context this could be a conflict with optifine? Check you you have latest versions of these mods then contact the mod author(s).

This thread has a working forge gui overlay: https://forums.minecraftforge.net/topic/116247-119-detect-if-the-player-is-looking-at-the-sun/#comment-513544 I tried to build your project but I got some error about a java module conflict when I ran forge:runclient Exception in thread "main" java.lang.module.ResolutionException: Module generated_d81a3f9 contains package com.ptsmods.morecommands.compat.client, module generated_846f3c3 exports package com.ptsmods.morecommands.compat.client to generated_d81a3f9 at java.base/java.lang.module.Resolver.resolveFail(Resolver.java:901) at java.base/java.lang.module.Resolver.failTwoSuppliers(Resolver.java:807) at java.base/java.lang.module.Resolver.checkExportSuppliers(Resolver.java:736) at java.base/java.lang.module.Resolver.finish(Resolver.java:380) at java.base/java.lang.module.Configuration.<init>(Configuration.java:140) at java.base/java.lang.module.Configuration.resolveAndBind(Configuration.java:494) at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.ModuleLayerHandler.buildLayer(ModuleLayerHandler.java:75) at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.TransformationServicesHandler.buildTransformingClassLoader(TransformationServicesHandler.java:60) at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.Launcher.run(Launcher.java:104) at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.Launcher.main(Launcher.java:77) at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:26) at MC-BOOTSTRAP/[email protected]/cpw.mods.modlauncher.BootstrapLaunchConsumer.accept(BootstrapLaunchConsumer.java:23) at cpw.mods.bootstraplauncher.BootstrapLauncher.main(BootstrapLauncher.java:141) at net.fabricmc.devlaunchinjector.Main.main(Main.java:86) at dev.architectury.transformer.TransformerRuntime.main(TransformerRuntime.java:217) From what I can gather you are not really using anything from forge for this. You are using architectury's loom fork instead ForgeGradle, you aren't using the forge api directly you are using the architectury api and you are using the yarn mappings. The only part where forge is used is indirectly here to fire the event: https://github.com/architectury/architectury-api/blob/64c1f05efad05a9ef056a7db857065700fe00083/forge/src/main/java/dev/architectury/event/forge/EventHandlerImplClient.java#L61

Looks like an issue with oculus, make sure you have the latest version then contact the mod author.

It needs more memory.