UPDATE: As of 1.1.0 this now affects both Single Player games and Multiplayer servers. Quick note: Through testing, this does not appear to be a Mystcraft bug. I have found this bug is only specific to Single Player Ultimate. It does not affect the Ultimate server, nor the Direwolf20 pack (server or single player). This is odd because it's the same Mystcraft version in the Direwolf20 pack as Ultimate. Steps to reproduce the problem: Create a new single player world (creative or at least cheats enabled is best to get the creative notebook). Set up writing desk and book binder etc, and write a stable age Simple Example: Standard Terrain Single Biome Mushroom Island Biome Normal Sun Normal Moon Normal Stars Normal Lighting Normal Weather Clear Modifiers I'm choosing Mooshroom Island for the example because it's a rare biome so it's obvious when it goes wrong. Press F3 to bring up the debug info (important for a detail coming up). Then put the book in a stand and visit the age. What I expected to happen: Land in (if using the example above) a mooshroom island single biome age. What actually happens: Watch the debug info as soon as you go to the age. Assuming the example above, the biome info initially lists as Mooshroom Island, however it then clears away and remains blank for a few moments while the world generates. When the world generates, it is often something completely different (I usually got void ages, but cave worlds were common too). Note the debug info now lists a new biome, not Mooshroom Island, and if you fly around, it often isn't a single biome age either. My workaround: After creating a scrambled age, I checked the agedata nbt file for the age and found it to be written exactly as I wrote it in the writing table. No mention of void or cave worlds. So to fix the issue: Stop Minecraft Go to the DIM_MYST# folder for the age and delete all the mcr region files (make sure to only do this for the age that has the problem!) Start Minecraft Visit the age The age now generates correctly! I wanted to report this, because as I've said at the top, this seems to be a FTB Ultimate pack bug that only affects the Single Player mode. It does not appear to be a Mystcraft bug. I noticed that Single Player Ultimate has several ExtrabiomesXL biomes disabled where as the Ultimate server config does not. So I tried enabling those biomes again and seeing if the problem persisted, and it did, so this is not an issue with different ExtraBiomesXL configs. Something else is at play here that makes it only affect single player. Some more details can be found on the Mystcraft forum thread I made while trying to figure this problem out: http://binarymage.com/forum/viewtopic.php?f=9&t=806
Don't know exactly how these things work, but would the mod launching order have an affect? For example, is there a difference between the mod pack in when the mystcraft and possibly ExtrabiomesXL are launching? Perhaps in Direwolf20 modpack Mystcraft launches after ExtrabiomesXL, but in Ultimate it launches before and thus gets rearranged by ExtrabiomeXL when that launches. Not a programmer here, but thought that might be a possible issue to check into.
Hey, nice post! Do you mind if I link this to another thread? The OP there, whizzball, wrote a guide on Mystcraft, and he isn't really aware of this...but I have had huge problems with SMP. I'd recommend for you to put this in FTB Chat, not bugs. Yes, it is a bug, but this is more of a helpful guide. Maybe edit this post to show the bug (and it's workaround), and make a guide (complete with screenshots ) to help other players get past it. Most don't realize it's a bug, it's a new edition and people think that it's their fault at bad age making (like I did).
Feel free to link or even just copy paste the whole thing into any threads you like, I posted it in a public forum for the very reason of getting the word out I posted it here in "Bugs" because the workaround shouldn't be needed if the bug gets fixed. Also as it states above, this only affects Single Player. I haven't been able to reproduce the bug in SMP, Mystcraft age creation works correctly there, so double check your pages if you're having trouble in SMP.
Yea I've had problems with SMP, most of the time it's a void world. Since it's in the "bugs" section, not as many people will read it, but it's still a great guide.
Well the world in the OP up there should work consistently (at least it has for me in SMP), as well as the three ages I've listed here: http://forum.feed-the-beast.com/thr...ver-ages-help-with-symbols.14507/#post-167654 If you try them out and still get void ages, then maybe the bug does exist in SMP, but I haven't been able to reproduce it in SMP (it only happens in Single Player Ultimate for me).
No, It's single player, oops...misspell. It's been in SSP, haven't gotten a chance to make an age on SMP, though I thought the two were pretty much the same since 1.3?
Yup, so did I. But as this only affects the Ultimate mod pack, there may be some configuration difference between the single player mode and the multiplayer server. (I already noticed there's different ExtraBiomes settings for Single Player than there are in Multiplayer as I said in the OP, but this doesn't seem to be the problem either).
If you're good at that kind of stuff, you should figure out the problem with it. I assume the server loads it before the player touches it, so if you were to somehow get a chunk loader in there before it generated, it may work.
Unfortunately I don't think that would work. The issue is with the initial generation of the chunks. Can't really put a chunk loader into chunks that haven't even been generated yet. Once they're generated, they're already wrong and the fix is to simply delete them and have them re-generate correctly. It's possible that someone at FTB knows exactly what differences there are between Single Player and Multiplayer Ultimate and they'd be better suited to finding the source of the problem. I'm using Mystcraft in multiplayer now, this problem only affected me when I was testing and preparing some ages, so I'm no longer "waiting on a fix". I will test any new updates to Ultimate and report if it still happens or not, but I'm not going to try to track down the cause as I've got very little leads on where it might be. Sorry.
Well, if you could, that's what the server does. It chunk loads the Mystcraft world before you ever go in it. I think it's something to do with the player. Maybe Mindcrack should have some tests done with Mystcraft, as it has some FTB mods Direwolf doesn't. If you're not up to it (you said you don't need a fix), I could try to find some people to test it who know Mystcraft well enough or people who can get a server up to test.
Thanks! This is the exact problem I was having. There's only one problem I keep having after the fix, though. When I go back to the age (after deleting the mcr files) the age loads as it should but I get reoccurring damage from an invisible source. Nothing shows up on my status but I get half a heart damage per second even with quantum armor.
It might still be an unstable age depending on how you wrote it. Is it scorched surface? (e.g. if you take off the quantum armor and press F5, are you on fire?). Does the damage stop if you go underground? If the damage stops when you've been underground for a minute or so, it's probably some instability effect. Not sure why it wouldn't show up in your status, but the quantum armor might be nullifying it immediately as it starts. Maybe try creating the age a few times with slightly different settings to see if the results change. I have some tips in a thread linked 7 posts up ^
Thanks. I'll check that out tonight by going underground...if I live long enough. hehe. I'm pretty sure the ages were supposed to be stable, I even did one exactly as you did with the same issue resulting. BTW, I posted this issue on Reddit and then when I found this post last week I linked to it. Great job find finding this solution! I was bothering me since Ultimate came out. Edit: Double post.
Adding an update to this to say this still happens in Ultimate 1.1.0 and now also affects multiplayer too. I have edited the original post to reflect this. Issue opened: https://github.com/Slowpoke101/FTBLaunch/issues/586 http://desk.feed-the-beast.com/index.php?/Default/Tickets/Ticket/View/TYN-285-71836
