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

1.12.2 Incompatibility with Scape and Run: Parasites v1.9.0A #175

Open
Cephelo opened this issue Jun 29, 2021 · 2 comments
Open

1.12.2 Incompatibility with Scape and Run: Parasites v1.9.0A #175

Cephelo opened this issue Jun 29, 2021 · 2 comments

Comments

@Cephelo
Copy link

Cephelo commented Jun 29, 2021

While this is an incompatibility with an alpha version of Scape and run: parasites, how the biome is generated will likely not be changing. Before testing this, read the alpha changelog, as it will explain how the biome is generated, and how some mechanics work. The issue is the nodes do not generate the infested plains biome - if you need any help finding this issue, please let me know.

@Vetpetmon
Copy link

Vetpetmon commented Oct 17, 2021

Confirmed: tested with and without JEID.

JEID causes Nodes to lag the server, booting even those in singleplayer. Causes massive tick lag, and the biome doesn't actually spread.

Expect result: Nodes do not lag the server, and the biome spreads normally.

Tested with SRP 1.9.0, Alpha 2, latest version of JEID.

Proposed workaround: Maybe nodes will work with Not Enough IDs?

Edit: additionally, no crash log is dropped, only a stall log. Hm.

@Vetpetmon
Copy link

Update: Error caught live in Miami:

https://pastebin.com/L9cSZ1By

Go wild. Either mod and it's developers can use this. Using any JEID version with the biome ID extender will report this.

Opening to LAN reveals just how laggy this incompatibility is, besides just not letting the biome spread. This log snippet shows me getting kicked out of my own LAN server because the SRPPacketBiomeChange packets caused a massive memory leak, frame stutters, and eventually death of the server.

Please prioritize this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants