Running latest version of ruins and OTG. Running forge version 14.23.5.2838.

It seems there's some kind of error when you run both OTG and ruins at the same time. Grass and trees are both appearing in ruins and sometimes hovering over them as well. The grass breaks on random tick updates but it's not ideal. Also, there's a lot of strange spots where it looks like a ruin tried to spawn but didn't and then just removed all the grass in the spot. Screenshots attached. There is no error log for this.

Bald spots:

Grass:

Trees:

A glance at their github sourcecode shows OTG hooks into minecraft much deeper than Ruins does - apparently they outright replace WorldProviders with their own variants. I am a bit surprised Ruins still works with that, honestly.

As for the problem - looks like a timing issue on generation. I suspect it would require conscious effort to make these two mods play nice together. [Don't want to invest the time for that]

Could issues with OTG also cause ruins to spawn on top of each other regardless of settings? I see a lot of ruins that spawn either right next to each other or actually clip into each other.

Short answer: Yes. The mods are obviously incompatible.

Hey guys, thanks for looking at this. The WorldProvider is replaced to allow for dimension-specific features. OTGWorldprovider does inherit from WorldProvider though and where possible calls the base methods, which may explain why this does work partially. What's going on here I'm not exactly sure of, would need to know which resources belong to which mod, and which resources are spawned first. It does indeed look like a problem with the spawn order, or some resources using only base terrain data to determine spawn location/eligibility, instead of looking at the currently spawned blocks (which would include the ruins that have just been spawned). @AtomicStryker is right, this will need more investigation and potentially mod-specific code, which any mod author should try to avoid. @mensreaMC, If you can do a bit more digging on this and provide more information, test with/without resources to figure out which mod is spawning what when, and also test without FromImageMode (not sure if you're using it), then that may give us enough information to make it worth taking a closer look. Feel free to close the issue here and re-open it on the OTG git if that's more appropriate.

Thanks for popping in. As i said, i won't be doing anything about it. If someone else wants to fix and pull request it, that would be fine.