AllTheMods / All-the-mods-9-Sky

All the mods skyblock pack for 1.20.1 Forge
52 stars 38 forks source link

[Bug]: "+" Button missing in Crafting Station in JEI #592

Open capripio opened 1 month ago

capripio commented 1 month ago

Possible Fixes

Yes

Modpack Version

1.0.9

What happened?

"+" is missing after new bookmark button has been added into JEI. Work fine normal crafting table.

Screenshot 2024-07-21 120947

latest.log

No response

Developer reports

No response

dbuzman commented 1 month ago

I have the same thing. Crafting station, the + does not show up, vanilla crafting table both show up.

desagas commented 1 month ago

It is completely missing in the latest update. Ugh. Let's hope they do not pass this off as "not planned" like some previous changes.

Burjo83 commented 1 month ago

Was about to post this bug. To add further to this bug. I have noticed the + (Move item) button is missing only when there is a connected inventory (Chest).

edited for spelling

medskifearx commented 1 month ago

same here, i was trying to find on the config and idk how to fix that problem

VLange80 commented 1 month ago

same here. Kinda killed my starter storage setup "@sophisticated connected to the crafting station" 2024-07-26_10 21 18 2024-07-26_10 21 30 2024-07-26_10 21 34

Zetta269 commented 1 month ago

I can confirm this. Not just only in JEI, but in just using the Crafting Station itself

Trunks19814 commented 2 weeks ago

i have the same Prob MC and the Buttons below not working

nearbyttv commented 1 week ago

[Render thread/ERROR]:Recipe Transfer helper class tfar.craftingstation.jei.TransferHandler does not work for container class tfar.craftingstation.CraftingStationMenu. The Recipe Transfer Helper references inventory slot index [10] but it does not allow modification. this is the client side error you get when accessing the crafting station while its connected to a storage (chest, sophisticated storage, barrel, etc.) this bug breaks early game storage and makes early progression a major challenge in some cases.

confirming this is still a bug on latest release of 1.1.1