Create

Create

86M Downloads

Sequenced Assembly Recipe with more then 6 steps are bugged in JEI

TBiscuit1 opened this issue ยท 3 comments

commented

Describe the Bug

Custom Sequenced Assembly Recipe can have more then 6 steps, but going over it starts to create weird things with JEI, especially with more then 7 steps

Reproduction Steps

  1. Create a custom recipe with 6 Steps
  2. Check JEI and see that it renders correctly
  3. Change the recipe so it has an extra step (7)
  4. Check JEI and see that it is touching the border
  5. Change the recipe so it has an extra step (8)
  6. Check JEI and see that it is starting to go out of bounds
  7. Change the recipe so it has an extra step (9)
  8. Check JEI and see that it can't show the tool tip of out of bounds step
    ... For info, going higher doesn't do any more stuff

Expected Result

To not go out of bounds, or at least, not after only 8 steps

As a fix, it could make it go create rows when it goes over 6 steps, it would be possible to squeeze 2 more row and so make the sequenced going all the way to 18 steps without breaking

18 Steps is more then enough for any crafts

(oh and as a bonus, make the roman number go past 6)

Screenshots and Videos

Your average sequence
image

A sequence with 7 steps
image

A sequence with 10 steps
image

Crash Report or Log

No response

Operating System

Windows 7

Mod Version

0.4.0b

Minecraft Version

1.18.1

Forge Version

39.0.10

Other Mods

I am creating a modpack and it's when I discovered the bug, but due to the nature of the bug, Create and JEI alone will cause the bug

Additional Context

No response

commented

This issue has been marked as stale because it has been inactive for 3 weeks. It will be closed if it remains inactive for another 3 weeks.

commented

This issue has been closed since it has been inactive for 3 weeks since it was marked as stale.

commented

Bump. Hoping this gets fixed as I have some custom recipes for a modpack that go over six steps, and would like for them to be legible in JEI.

Edit: Expected the bot to reopen the issue when I posted this. apparently not how this works.