Starting July 30th, you will no longer be able to log in to a Curse account that was not merged with a Twitch account. If you have not yet merged your Curse account with a Twitch account, please do so here! Otherwise, your account and its content will be inaccessible.
java.lang.IllegalStateException: Ore block descriptor for StandardOreSubstitute is overspecified with a total match weight of 400.0%.
<Substitute name='StandardOreSubstitute' block='stone'>
Replace vanilla-generated ore clusters with stone.
The global option deferredPopulationRange must be large enough to catch all ore clusters (>= 32).
There are 7 replaces, but we don't see an error of 700%. We see 400%. There's no way I can even see how to get 400% from this segment.
Which brings up two questions:
1. Are you using single player or multiplayer, and
2. Has anyone gotten the 162 version to work? Whoever ported it: Which did you test (single player or multiplayer)? Did you test "Open to LAN" mode of single player?
Alright, I have managed to get COG working in 1.6.2, at least as far as I've tested it (not that far). Ores definitely spawn, but I haven't used the default COG settings enough to know if things are really the way they were before. You guys can hopefully help with that. The source code is now on github here. Contributions/collaborations welcome. And there is a built jar available here. Have fun guys. You've waited long enough. Thanks to JRoush for his amazing mod.
Ok, you are the porter.
What was the testing environment -- single, multi, or LAN? (It's a valid question -- Mystcraft 0.10.5 worked in single and multi but broke in LAN because it was slightly different.)
How do you guys think we should move forward as far as the online-presence of COG? Should we start a new forum thread, derivatize the name somehow to distinguish it from the original? The documentation wiki is really well done, but it's going to become out-dated. I'm guessing there's no way for us to edit it. Hopefully JRoush comes back.
Now that there have been some error reports on your version of the mod @Noogenesis I think it would be fair to JRoush to start a new thread for your version - Naming is not important, but maybe CoG Reloaded or something - Anyway, that way everything related to your version isn't burried in the comments on page 64 here, and people can find what they need for your version easily, and if JRoush Does come back, he isn't bogged down filtering through if that error message was his version or yours.
Do you know how I would allow the 1.6.2 edition of Custom Ore Gen to catch all mod ores? As in where to change the settings?
Catch all mod ores? Well, the answer is, you can't.
Most ores can be caught by the "vanillaOreGen" option. This can be set to false to stop most normal ore placement.
Beyond that, if you want to go from "most normal ore placement" to "all ore placement", you set that to true, and use a substitute to override everything. That's what the stock 1.4.6/1.4.7 config does. I assume the 1.6.2 version is the same, but I have not played with it yet.
As I've stated, that hurts mystcraft (which now has a 1.6.2) and twilight forest. So for me, moving forward, I'm going for the "most" behavior.
Alright guys, thanks to your encouragement, I have started a new thread for the revived version. Please direct all queries and feedback related to my 1.6.2 port to that thread. I'll only be watching this one for the return of JRoush.
Like to build? Check out Charlotte's Utilities - Layout Blocks, Brushes, Prospectors, and more!
Follow me on twitter @charlotte_c_b for updates! You can also find me in irc.esper.net as Ilandria
Development of my mods is made possible by Full Effect Hosting