Skip to content

Sophisticated Backpacks screen closes immediately when satchel is injected #19

Description

@UltimatePinkBerryJuice

Using Vercte's Satchels 1.2.0 on NeoForge 21.1.233 / MC 1.21.1.

I added sophisticatedbackpacks:backpack to the supported screens list. The injection is detected correctly (logs confirm it), but the backpack screen briefly flashes open and immediately closes. The satchel UI is visible for a single frame before it closes.

The log shows the screen being detected and fired twice in rapid succession on both client and server threads each time I try to open the backpack:

[13:24:51] [Render thread/INFO] [net.vercte.satchels.SatchelsEventHooks/]: satchels: opened sophisticatedbackpacks:backpack
[13:24:51] [Server thread/INFO] [net.vercte.satchels.SatchelsEventHooks/]: satchels: opened sophisticatedbackpacks:backpack
[13:24:52] [Render thread/INFO] [net.vercte.satchels.SatchelsEventHooks/]: satchels: opened sophisticatedbackpacks:backpack
[13:24:52] [Server thread/INFO] [net.vercte.satchels.SatchelsEventHooks/]: satchels: opened sophisticatedbackpacks:backpack

No errors or exceptions are thrown. The screen ID is correct and the injection fires, but something causes the screen to close immediately after opening. My suspicion is that Sophisticated Backpacks closes and reopens its own screen during initialization, and this second open is what causes the issue.

Other mods that may be relevant: Curios (curios-neoforge-9.5.1+1.21.1) and Accessories (accessories-neoforge-1.1.0-beta.53+1.21.1) are both loaded, and the backpack item is registered in both curios:back and accessories:back slots.

Metadata

Metadata

Assignees

Labels

bugthis does something unexpectedcompatibilitythis relates to mod compatibility

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions