Refined Storage

Refined Storage

115M Downloads

Crash index out of bounds error after using autocrafting terminal

Closed this issue ยท 7 comments

commented

Describe the bug

I made a pattern then before taking out the pattern - after I tried to make a new pattern, it crashed

How can we reproduce this bug or crash?

I made a pattern then before taking out the pattern - after I tried to make a new pattern, it crashed

It still crashes the client (only client) each time I login now.

What Minecraft version is this happening on?

Minecraft 1.21.1

What NeoForge or Fabric version is this happening on?

21.1.203

What Refined Storage version is this happening on?

refinedstorage-neoforge-2.0.0-beta.10

What modpack and modpack version, if any, are you using?

ATM10

Relevant log output

https://gist.github.com/teknium1/cf92650ad27c3f6436759d723ebfac46
commented

So I will want to try this out of course, to fix the bug.
But which pattern do I make?

commented

Also "latest" is not a version number. Need to figure out how to block people from typing that in somehow.

commented

Also "latest" is not a version number. Need to figure out how to block people from typing that in somehow.

seems like the best you can do is either make it a dropdown or make a bot that closes it. The only validation github seems to support is "required" as true or false

https://docs.github.com/en/communities/using-templates-to-encourage-useful-issues-and-pull-requests/syntax-for-githubs-form-schema

commented

Github seems to be very good at building halfway solutions; open source maintainers would benefit greatly from having a dropdown type that maps to the releases ALREADY PRESENT ON GITHUB, but I guess that the idea is too obvious.

commented

Sorry, was in a rush. Updated forge & mod version.

The pattern specifically was like the advanced geocomputer but made when another advanced geocomputer (if I remember correctly) was already in the completed pattern slot

commented

@teknium1 Thanks for the additional details, thanks to that I was able to solve it quickly.

commented

Has been solved in v2.0.0-beta.13.