Jump to content

Recommended Posts

Posted (edited)

Ok, I seem to be at the end of my wits this error about my dimension. When I go to try creating a world, Minecraft throws a data pack error complaining (AFAIK) about my dimension not being properly registered.

Log of the last launch: https://gitlab.com/-/snippets/2537039

Dimension JSONs: https://gitlab.com/NoahJelen/paradisemod/-/tree/1.18.2/src/main/resources/data/paradisemod/dimension

Dimension type JSONs: https://gitlab.com/NoahJelen/paradisemod/-/tree/1.18.2/src/main/resources/data/paradisemod/dimension_type

Noise Settings JSONs: https://gitlab.com/NoahJelen/paradisemod/-/tree/1.18.2/src/main/resources/data/paradisemod/worldgen/noise_setings

Biome source class: https://gitlab.com/NoahJelen/paradisemod/-/blob/1.18.2/src/main/java/net/paradisemod/world/biome/PMBiomeSource.java

Main dimensions class: https://gitlab.com/NoahJelen/paradisemod/-/blob/1.18.2/src/main/java/net/paradisemod/world/dimension/PMDimensions.java

The noise settings were created with this data pack generator: https://misode.github.io/

Edited by NetherNoah777
Posted

I changed your deep_dark dimension to this:

  Quote

{
    "type": "paradisemod:deep_dark",
    "forge:use_server_seed": true,
    "generator": {
        "type": "minecraft:noise",
        "settings": "paradisemod:dd_noise",
        "biome_source": {
            "type": "minecraft:the_end"
        }
    }
}

Expand  

And it stopped complaining about that dimension and started complaining about the others, so it looks like there is some issue with your custom biome source.

Minecraft instead of giving the real error is saying your dimension is not registered, maybe because it failed to deserialize it using the codec?

You will probably have to use a debugger to see what is really wrong with it.

Boilerplate:

If you don't post your logs/debug.log we can't help you. For curseforge you need to enable the forge debug.log in its minecraft settings. You should also post your crash report if you have one.

If there is no error in the log file and you don't have a crash report then post the launcher_log.txt from the minecraft folder. Again for curseforge this will be in your curseforge/minecraft/Install

Large files should be posted to a file sharing site like https://gist.github.com  You should also read the support forum sticky post.

Posted

Ok, I think I finally fixed my problem! It seems like both my biome source and noise settings were causing issues. I was able to fix the biome source issue with the debugger and I ended up hard coding my noise settings.

  • NetherNoah777 changed the title to [solved] Frustrating error with my dimensions when I try to create a world

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Unfortunately, your content contains terms that we do not allow. Please edit your content to remove the highlighted words below.
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

Announcements



  • Recently Browsing

    • No registered users viewing this page.
  • Posts

    • "I want to understand how complex mods with ASM transformation and coremods work, such as Xray or AntiXray. Why do they break when you simply rename packages? What features of their architecture make refactoring difficult? And what techniques are used to protect these mods? I am interested in technical aspects in order to better understand the bytecode and Forge loader system."
    • I can't figure out if you're looking for help trying to steal someone elses work, or cheat at the game....
    • Title: Why Is It So Hard to Rename and Restructure Mods Like Xray or AntiXray? 🤔 Post text: Hey everyone! I’ve been digging into Minecraft modding for a while and have one big question that I can’t figure out on my own. Maybe someone with more experience could help or give me some advice. Here’s the issue: When I take a “normal” Minecraft mod — for example, one that just adds some blocks or new items — I can easily change its structure, package names, or even rebrand it entirely. It’s straightforward. But as soon as I try this with cheat-type mods like XrayMod or AntiXray, everything falls apart. Even if I just rename the classes, refactor the packages, or hide its identity somehow, the mod either breaks or stops working properly. XrayMod in particular is proving to be a nightmare to modify without losing its core function. So my question is — why is this so much harder with cheat mods like Xray? Is there something fundamentally different about how they’re coded, loaded, or protected that prevents simple renaming or restructuring? And if so, how can I actually learn to understand someone else’s cheat mod enough to safely refactor it without breaking the core features? I’ve already been spending over two months trying to figure this out and haven’t gotten anywhere. It feels like there must be some trick or knowledge I’m missing. Would really appreciate any thoughts, tips, or references — maybe there are guides or techniques for understanding cheat-mod internals? Or if you’ve successfully “disguised” a cheat mod like Xray before, I’d love to hear how you did it. Thanks in advance for any help or discussion. ✌️
    • just started making cinamatic contect check it out on my channel or check out my facebook page    Humbug City Minecraft Youtube https://www.youtube.com/watch?v=v2N6OveKwno https://www.facebook.com/profile.php?id=61575866982337  
    • Where did you get the schematic? Source/Link? And do use an own modpack or a pre-configured from curseforge? If yes, which one On a later time, I can make some tests on my own - but I need the schematic and the modpack name
  • Topics

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.