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

Disabling vanilla ore generation doesn't work. #139

Open
Trinsdar opened this issue Jul 17, 2018 · 23 comments
Open

Disabling vanilla ore generation doesn't work. #139

Trinsdar opened this issue Jul 17, 2018 · 23 comments
Assignees
Milestone

Comments

@Trinsdar
Copy link

Trinsdar commented Jul 17, 2018

This is my orespawn.json: https://paste.dimdev.org/ciwoluzafo.json
I have B:"Replace Vanilla Oregen"=true in the orespawn config.
OreSpawn-1.12-3.3.0.136

Edit: I should note that I have Geolosys installed in case that might be conflicting.

@dshadowwolf
Copy link
Contributor

We have had some other reports of Geolosys getting in the way - if it is that, then CoFHWorld would also be failing here, as we use the same method of stopping generation. That is, we cancel the event for all vanilla material types.

Looks like another test environment needs to be setup.

@Trinsdar
Copy link
Author

I'll test in just geolosys + orespawn, cofh + geolosys, and just orespawn

@dshadowwolf
Copy link
Contributor

Hrm... this is strange, then. As I noted on the MMD Discord, the code we use for managing the "replace vanilla ore generation" is close to identical to what is in CoFHWorld - there might be an issue with the conditional that controls the event handler registration, though, hrm...

@Trinsdar
Copy link
Author

ok this is wierd. just by itself and geolosys it works but it doesn't work in my pack. I have to do more testing though.

@Trinsdar
Copy link
Author

so there's no vanilla ore gen even without the vanilla override set to true which means that geolosys is disabling vanilla ore gen.

@Trinsdar
Copy link
Author

means I can't tell if it's geolosys or orespawn that's having the problem.

@Trinsdar
Copy link
Author

upon removing geolosys vanilla ore gen worked so therefore geolosys stopped vanilla ore gen.

@Trinsdar
Copy link
Author

and your vanilla removing works by itself so no problems there.

@Trinsdar
Copy link
Author

I think I can safely say that another mod is intefering with geolosys in my pack.

@Trinsdar
Copy link
Author

I don't think it's orespawn

@Trinsdar
Copy link
Author

Trinsdar commented Jul 18, 2018

mabye it's minerology?
it did create an errored file underneath the config file

@jriwanek
Copy link
Member

Can you pastebin it please.

@Trinsdar
Copy link
Author

I can upload the file. I can't pastebin it as its a .errored file and I don't know how to open it.

@Trinsdar
Copy link
Author

@jriwanek
Copy link
Member

It's a text document with a funny extention, opens just fine in notepad++.
Not 100% sure, but I'd assume something in it is invalid.

@Trinsdar
Copy link
Author

@dshadowwolf
Copy link
Contributor

I'm not positive - I think the bit starting at line 133 might be the culprit:

    # Adds blocks to rock layers (format is mod:block as a semicolon (;) delimited list) [default: ]
    S:sedimentary_whitelist=
    earthworks:block_slate; 
    earthworks:block_slate_green; 
    earthworks:block_slate_purple; 
    earthworks:block_chalk

I think this might need to be:

S:sedimentary_whitelist=earthworks:block_slate;earthworks:block_slate_green;earthworks:block_slate_purple;earthworks:block_chalk

Just to satisfy the Forge config parser

@jriwanek
Copy link
Member

Give it a go, let us know, really it should be an array instead of a big string. (We should fix that at some point)

@Trinsdar
Copy link
Author

looks like minerology isn't causing it as when just it, base metals, base minerals, orespawn, and geolosys are in vanilla ores don't spawn. yet they spawn in my pack. I'm going to upload the mods and configs i have so you can test.

@Trinsdar
Copy link
Author

I probobly won't link it till later tommoraw/today(it's 12am) since it's taking a long time to upload.

@Trinsdar
Copy link
Author

@jriwanek jriwanek added this to the 3.4 milestone Jun 26, 2021
@dshadowwolf
Copy link
Contributor

Has this been tested with the fixes that went in on the Maven recently ?

@jriwanek
Copy link
Member

Not yet, no.

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

3 participants