Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Scrolling through waves on 'Death Tome Gate Pearl' in EMI crashes game #913

Closed
endobson opened this issue Mar 27, 2024 · 9 comments
Closed
Labels
Bug Modpack specific bug. Mod Issue Bug within a mod. Status: Fixed In Next Release

Comments

@endobson
Copy link

Modpack Version

1.20.1

Describe your issue.

I open inventory, EMI is on the right. Enter "Tome Gate" or similar in the search bar to and hover over the 'Death Tome Gate Pearl'. Scroll with shift held, and observe crash

Crash Report

https://gist.github.com/endobson/502e6d7c3f2bd8f049b5c300233affe3

Latest Log

https://gist.github.com/endobson/f9cf93425093becf2657ada55027acbc

Have you modified the modpack?

No

User Modifications

No response

Did the issue happen in singleplayer or on a server?

Singleplayer

Discord Username

No response

@endobson endobson added the Bug Modpack specific bug. label Mar 27, 2024
@Shadows-of-Fire
Copy link

Screm, @SiverDX I thought you checked for these issues

Shadows-of-Fire added a commit to Shadows-of-Fire/GatewaysToEternity that referenced this issue Mar 28, 2024
@SiverDX
Copy link

SiverDX commented Mar 28, 2024

don't accept candy commits from strangers

@TheUnnamed44
Copy link

When scrolling through the pearl's waves in the recipe window, the game does not crash, but rather the screen says "Error Rendering":

2024-03-28_13 55 02

And when hovering, a massive block of error code is shown:

2024-03-28_13 55 07

@SeooY
Copy link

SeooY commented Mar 28, 2024

I can confirm that the GatewaysToEternity-1.19.2-3.2.3 release fixes both of these issues.

@MuteTiefling
Copy link
Contributor

Unfortunately, that appears to be tagged as NeoForge, so the Curseforge launcher doesn't let us see it. Not sure we can actually include it in the pack as a result, but that's more @NielsPilgaard's area of expertise.

@HeatherComputer
Copy link

No 1.19 jar should be tagged as for neoforge, so that's something the mod dev needs to sort. Regardless, doesn't the curseforge launcher let you see stuff that's tagged for both forge and neoforge?

@MuteTiefling
Copy link
Contributor

Not when the mod loader doesn't match, no.
image

If I manually add it, it even warns against it:
image

@MuteTiefling MuteTiefling added Mod Issue Bug within a mod. Status: Awaiting Mod Update Fixed in the mod responsible, but not yet released. labels Mar 28, 2024
@HeatherComputer
Copy link

Ah I see, it's tagged neoforge only. @Shadows-of-Fire you might want to change that.

@Shadows-of-Fire
Copy link

Fixed, loader got mismatched during a buildscript backport

@NielsPilgaard NielsPilgaard added Status: Fixed In Next Release and removed Status: Awaiting Mod Update Fixed in the mod responsible, but not yet released. labels Apr 10, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Modpack specific bug. Mod Issue Bug within a mod. Status: Fixed In Next Release
Projects
None yet
Development

No branches or pull requests

8 participants