There's two ways we can resolve this issue:
Number 2 is the ideal solution, but takes much more resources, which we still haven't been able to prioritize given that this does not affect that many people. I could do Number 1 as a temporary solution but it's more of a band-aid and would end up being more restrictive than the glitch, so I feel like it is probably more harm than good (?)
You're welcome to voice your feedback about how I respond to bug reports, but please do so in the Site Feedback forums. In the bug report forums, let's keep the focus on resolving bugs. I appreciate the reminder ping about this topic.
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
Nothing to forgive. I'm not upset, I really did appreciate the reminder ping, and I tried to give a better reply this time since I did read back up and see how a followup was neglected. But this is still off topic so again, please head over to Site Feedback if you want to discuss the communication concern further. Happy to meet you there.
Option 1 was mentioned because it is a valid solution. It would prevent the glitch by preventing users from meeting the conditions that cause the glitch to appear.
This glitch is a side effect of how scroll data is stored, and the ideal solution is to change the way we do it to be more robust and efficient, so that it can store a lot more scrolls using less data and be way less restrictive. A limit will still need to be introduced but we'd be able to place it high enough to not be prohibitive (like 100)
We made the mistake of not having limits in a lot of Subeta's early code, but it turns out they are necessary because the code still does have inherent limits no matter what - you just run into them via things crashing (like this scrolls bug) if no limit is explicitly set.
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights
Let's try to stay on-topic to the bug report, please. This isn't the place to discuss how different players choose to play the game!
[edit] I think the suggestions or feedback forums might be best if you want to discuss/suggest more significant changes to how scrolls work. This bug report is about how scrolls crash under certain conditions and this issue will be addressed either way <3
🐝 ☕ bug (he/him) | your friendly neighborhood code wrangler. stay in the loop! join and check out the latest admin post highlights