Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] item minecraft:shears #1748

Open
11pickfk opened this issue Nov 2, 2022 · 1 comment
Open

[BUG] item minecraft:shears #1748

11pickfk opened this issue Nov 2, 2022 · 1 comment
Labels
status: unverified type: bug Something isn't working

Comments

@11pickfk
Copy link

11pickfk commented Nov 2, 2022

Whenever I try to join my server I am greeted with the message

Internal Exception: com.google.common.util.concurrent.UncheckedExecutionException: java.lang.illegalStateException: Recipe minecraft:shears (net.minecraft.item.crafting.ShapedRecipes@6789b471) produces unregistered item minecraft:shears (net.minecraft.item.ItemShears@7154a248)

https://gist.github.com/11pickfk/6dccad75c83828ec8a494d3501117df1

Also found this within logs

[00:19:46] [Client thread/FATAL] [gregtech]: Seems like invalid recipe was found.
[00:19:46] [Client thread/FATAL] [gregtech]: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[00:19:46] [Client thread/FATAL] [gregtech]: Ignoring invalid recipes and continuing loading
[00:19:46] [Client thread/FATAL] [gregtech]: Some things may lack recipes or have invalid ones, proceed at your own risk
[00:19:46] [Client thread/FATAL] [gregtech]: Report to GTCE github to get more help and fix the problem
[00:19:46] [Client thread/FATAL] [gregtech]: ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
[00:19:46] [Client thread/INFO] [gregtech]: ForgeMultiPart found. Legacy block conversion enabled.
[00:19:46] [Client thread/INFO] [gregtech]: TheOneProbe found. Enabling integration...
[00:19:46] [Client thread/INFO] [gregtech]: Initializing ore generation registry...
[00:19:47] [Client thread/INFO] [gregtech]: Reloading ore generation files from config...
[00:19:47] [Client thread/INFO] [gregtech]: Loaded 72 worldgen definitions
[00:19:47] [Client thread/INFO] [gregtech]: Registering cover behaviors...
[00:19:47] [Client thread/INFO] [gregtech]: Registering dungeon loot...

Not sure if that is what is causing the issue, I'm not good at reading logs

https://imgur.com/a/yWzOH43

@11pickfk 11pickfk added status: unverified type: bug Something isn't working labels Nov 2, 2022
@Exaxxion
Copy link
Collaborator

Exaxxion commented Nov 3, 2022

The error on connection happens when you have some kind of recipe registration mismatch between the client and server. You're either using configs that result in substantially different item registries (e.g. AE2 channels are on in one place and off in the other) or you have a broken client pack install.

A cursory look reveals an exception for a malformed json file in one of the mods you're using (f5fix?), an error trying to patch Pistons by RandomPatches, a mod called LLibrary crashing because it couldn't retrieve it's Patreon user list and were not diligent enough to handle that very foreseeable circumstance, several errors related to blockstates that could probably be explained by pack scripts removing stuff, AdvancedRocketry trying to blacklist a biome by ID number which does not exist, multiple errors pertaining to reading the stat of monsters from Apotheosis from its configs, Actually Additions reporting it couldn't parse the Configuration Items config, a ton of errors from some mod called DLDUNGEONS (many pertaining to harvestcraft integration), etc.

The pack you're playing on is also using a rather old version of GTCE (1.10.0, the last release was 1.17.1 a year ago).

The error about invalid recipes from GTCE are informative rather than crashes. They wouldn't register on the server either because as formulated the recipes are impossible to use.

My suggestion is you reinstall the modpack and try connecting to the server again. This does not at all look like a problem with GTCE specifically, but either a broken pack install or a poorly configured pack.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
status: unverified type: bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants