[1.19.2] Crash when configuring backpack locked slots

Question

[1.19.2] Crash when configuring backpack locked slots

Shedao-Shai opened this issue 2 years ago · 4 comments

Shedao-Shai commented 2 years ago

Describe the bug
Crash when configuring locked and/or display slots in a backpack.
https://gist.github.com/Shedao-Shai/013b363e1de396ae25d00ea5cdb4fa93

Please go to Discussions to add new feature requests / suggestions or comment on existing ones.

To Reproduce
Steps to reproduce the behavior:

Place backpack
Open, and lock a slot into a specific item (in my case it was stone)

Expected behavior
The backpack should have just accepted the configuration and been all fine and dandy

Versions
Sophisticated Backpacks: 1.19.2-3.18.29.719
Sophisticated Core: 1.19.2-0.5.12.130

Forge: 43.1.32

P3pp3rF1y · Answer 1 · 2022-10-24T15:29:40.000Z

@Shedao-Shai could you share more info on the backpack where you're trying to set this up? An idea that I have is that it could be related to frequent server>client updates that some upgrade may do for some reason and knowing more on what upgrades you have in there or how you're using them would help.

Shedao-Shai · Answer 2 · 2022-10-24T23:12:17.000Z

The only upgrade present is a tier 4 stack upgrade (base backpack with 1 chests worth of slots), otherwise there is no upgrade present (crash happens in both) and the backpack is placed in the world. What I am doing is opening the backpack, placing an item in, locking the slot, then setting that same slot as a display. It typically hangs when I try to lock the slot, then crash moments later.

…

On Mon, Oct 24, 2022 at 10:29 AM P3pp3rF1y ***@***.***> wrote: @Shedao-Shai <https://github.com/Shedao-Shai> could you share more info on the backpack where you're trying to set this up? An idea that I have is that it could be related to frequent server>client updates that some upgrade may do for some reason and knowing more on what upgrades you have in there or how you're using them would help. — Reply to this email directly, view it on GitHub <#625 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AFUQCD5QMCWHVQGVA5V5F3LWE2TPBANCNFSM6AAAAAARJQQCAY> . You are receiving this because you were mentioned.Message ID: ***@***.***>

Shedao-Shai · Answer 3 · 2022-10-19T21:14:40.000Z

I will note that this does not happen every time, its very intermittent

P3pp3rF1y · Answer 4 · 2023-03-28T21:07:01.000Z

I am still not able to recreate and haven't got any other reports for this issue so I am guessing this is some odd mod interaction and I am closing the ticket. In case you can recreate with specific steps with just sophisticated mods or are able to get me info on what exact mod needs to be in the pack for this to break feel free to create new ticket with that info.

Share to