Hipposgrumm / armor-trims

2 stars 1 forks source link

Disabling JEI doesn’t disable JEI #30

Closed V972 closed 10 months ago

V972 commented 1 year ago

Forge: 40.2.10 Jei: 1.18.2-9.7.2.1001 Armor Trims: 1.18.2-1.3.2

debug.log latest.log

Hipposgrumm commented 1 year ago

Finally, an issue that is unique to a specific version.

Hipposgrumm commented 1 year ago

Or maybe it's not version-unique...

Hipposgrumm commented 1 year ago

Disable the option EnableQuickMaterials, it seems to be broken.

Hipposgrumm commented 1 year ago

Send me your config file, I wanna try to reproduce this myself to fix it.

Hipposgrumm commented 1 year ago

I released a new patch so this is hopefully no longer an issue.

V972 commented 1 year ago

I...don' think it got fixed :(

The world joining stops during this line

image

and just hangs

I tries disabling JEI option, but it didn't help.

Here's my config: armor_trims.toml.log (I added .log to the extention cause GitHub doesn't let uploading .toml)

V972 commented 1 year ago

Tried downgrading JEI from 10.X to 9.X (some mods/addons are incompatible with it), didn't help.

wabeb325 commented 11 months ago

With REI the game runs normally, but it gets stuck loading recipes and the disable function still doesn't work. There are no news of this issue, right? 😔

Hipposgrumm commented 11 months ago

REI works fine since there is no built in compact for it. I am also now back to work on Armor Trims Backport so this issue should be getting fixed.

wabeb325 commented 11 months ago

What I meant by REI is that unlike JEI, REI does load, but this message pops up when you enter the menu and blocks REI functions. And as with JEI, it takes a while until it loads completely and the message disappears, so I saw it related to each other. image

rei.log

Hipposgrumm commented 10 months ago

After having half rewritten how recipes are generated, hopefully this is fixed now. Also I don’t know if the issue with disabling JEI was ever present but it’s fixed now.

V972 commented 10 months ago

I don't see 1.3.4 on MD or CF and version newest 1.3.3 version still has the bug

Hipposgrumm commented 10 months ago

I only said the bug was fixed in the new version. I never said it was out yet.