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

Streams mod is corrupting world generation algorithms #24

Closed
Noire86 opened this issue Aug 26, 2016 · 4 comments
Closed

Streams mod is corrupting world generation algorithms #24

Noire86 opened this issue Aug 26, 2016 · 4 comments

Comments

@Noire86
Copy link

Noire86 commented Aug 26, 2016

Explanation of issue:

Streams mod is corrupting chunk generation while installed with RTG and Climate Control. Several chunks are bald and unpopulated. In addition, bukkit plugins based on a chunk-related things are not working properly. For ex: WorldEdit regeneration of chunks is broken: chunks are regenerating unpopulated (no matter, if this chunk has Streams river or not).

How to recreate this issue:
Try to generate a world with Streams mod and RTG installed. Pregenerate a piece of world with any pregen utils (Worldborder, Chunkgen. etc.) Or regenerate a single-chunk with bukkit plugin like WorldEdit.

The one thing that I could detect is the Spigot Watchdog report of server freeze - it has some Farseek related Exceptions: http://pastebin.com/FZbZccn2

Mods Installed:
RTG 1.1.1-1.7.10
BoP (Latest)
Climate Control (Latest)
Streams 0.2
Farseek

Plugins Installed:
Worldborder
WorldEdit
AsyncWE

Thermos Version:
58 Build

Forge Version:
1614

Thanks in advance,
Noire.

@delvr
Copy link
Owner

delvr commented Aug 30, 2016

Hi NoireDvachevsky, thanks for reporting this. I'll take a look and get back to you.

@delvr delvr added the 1.7.10 label Nov 15, 2016
@delvr
Copy link
Owner

delvr commented Jun 16, 2017

Could you check if this still happens with Streams v1.7.10-0.3 or 0.3.1? That update doesn't specifically address pre-gen but it has some chunk-caching changes that might have fixed it.

If this still occurs, could you tell me which pre-gen tool (with version) you're using and what steps you're taking? I'm not very familiar with these tools so more details will be best. Thanks!

@Noire86
Copy link
Author

Noire86 commented Mar 24, 2021

Sorry for being so late - the problem is still on 0.3 streams and RTG latest

@Noire86
Copy link
Author

Noire86 commented Mar 25, 2021

Backporting commits from version 1.12-0.8.4 fixed the issue on 1.7.10-0.3.4

This commit: b1b580e#diff-ad0947396cb692f50c0e7010e9540c6f889787f50abd915fc2d76600c789abae

@Noire86 Noire86 closed this as completed Mar 25, 2021
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants