What is this yes/no screen?

[superriku11]

I recall having this same screen come up when I updated Mindcrack before. Pretty sure it only happens when Minecraft itself updates though, not an individual mod or mods. Sorry if this has been answered already but I browsed 3 or so pages back (since the update is recent) and didn't see anything.

What is this screen? I clicked yes since it gives me the impression it's some mod loader's "Want to update settings for new version?" confirmation, due to the fact Mindcraft's JAR updated. Though I really have no idea. The game still plays normally so there seems to be no negative consequence of hitting yes. I'd like to know what it is though.

 

[Velotican]

This screen appears whenever the block IDs recorded in your world save's log and the ones being used by the game don't match. If the details are blank like this, there are actually so many changes that the game gave up trying to display them all.
If you have the console enabled when you see this screen you should be able to see a full list of the changes in there. Most of the time clicking Yes won't do anything serious to your world but you should always backup before upgrading.

 

[superriku11]

This screen appears whenever the block IDs recorded in your world save's log and the ones being used by the game don't match. If the details are blank like this, there are actually so many changes that the game gave up trying to display them all.
If you have the console enabled when you see this screen you should be able to see a full list of the changes in there. Most of the time clicking Yes won't do anything serious to your world but you should always backup before upgrading.

So it actually would've been a better idea to click no? Because I was actually wrong when I said clicking yes didn't do anything. My game starts stuttering after a few seconds (and consider that my computer can maintain 200 FPS on the highest settings and never has massive FPS drops) and then crashes. I do have a backup before the update. I'll try loading it later and clicking No instead. Unless someone tells me another solution before then or tells me clicking No would be useless.

 

[Velotican]

If you click No it will abort loading the world to protect your save file.

How serious this screen is varies, because the warning will be triggered if the name of a block using the same ID changes even if it's actually the same block.

For my part I've not had problems running my personal pack which has effectively the same settings and IDs as FTB but if it happened to change something critical you could get symptoms like you're describing, but it would be something very specific to your world and difficult to troubleshoot.

Is there any machine actively running in your world right now, especially one involving bees? The changes to Extra Bees IDs were the most extreme on my end.

 

[superriku11]

If you click No it will abort loading the world to protect your save file.

How serious this screen is varies, because the warning will be triggered if the name of a block using the same ID changes even if it's actually the same block.

For my part I've not had problems running my personal pack which has effectively the same settings and IDs as FTB but if it happened to change something critical you could get symptoms like you're describing, but it would be something very specific to your world and difficult to troubleshoot.

Is there any machine actively running in your world right now, especially one involving bees? The changes to Extra Bees IDs were the most extreme on my end.

The only machine actually running for me is an Industrial Centrifuge. There may be a tree farm (Arboretum, Logger, some pipes, and all running on a Biogas Engine) running but I think it's engine was out of fuel. I know the Industrial Centrifuge was running though since I saw it where I logged in.

And I have not even touched the bees. So that certainly wouldn't be an issue. The only bees actually in my world data at all are ones in storage which I found in a dungeon.

 

[Velotican]

It might help if we see what the console spits out when you try to load the world from your backup. Crash logs could also be useful.

You could also try restoring the backup, downgrading to Mindcrack v7, disabling any active machines and processing, upgrade back to v8.0.1 and then see if you encounter the same problems.

I'm not sure whether this was v7 or v8 but at some point the Extra Bees hives in the world have had their block IDs changed, so even if you haven't been using bees before now the worldgen could still be having slight issues cleaning up after itself. I didn't encounter this but something silly (and probably very basic) is happening to you here.

 

[superriku11]

It might help if we see what the console spits out when you try to load the world from your backup. Crash logs could also be useful.

You could also try restoring the backup, downgrading to Mindcrack v7, disabling any active machines and processing, upgrade back to v8.0.1 and then see if you encounter the same problems.

I'm not sure whether this was v7 or v8 but at some point the Extra Bees hives in the world have had their block IDs changed, so even if you haven't been using bees before now the worldgen could still be having slight issues cleaning up after itself. I didn't encounter this but something silly (and probably very basic) is happening to you here.

Problem with the logs is that the launcher logs overwrite themselves if I reload the launcher. There's no crash logs since the game doesn't actually reach the crash screen. It hangs on "Shutting down internal server" however system monitoring indicates there was file system access to the save file before it crashed, and shortly after it's CPU usage drops from 100% of one core to about 3%.

I remember the launcher saying something about PermSize in red though so I did some searching and found this thread and post: http://forum.feed-the-beast.com/thr...8-stuttering-and-semi-crash.9542/#post-110359

I launched with that Java flag and I have no problems now. Running smoother than before it seems (though I started using VSync since I realized when I said I had 200 FPS that it was obviously off) and there is no more crashing. I don't know why but it seems everyone who encounters this problem is on OS X. Probably because you can only use Java 1.6 on OS X where as on GNU/Linux, Windows, or others you can use Java 1.7.

 

[Velotican]

Glad you solved it. Generally Minecraft mods are actually built with Java 7 in mind these days although some still use 6 to maximise compatibility.

 

[Malkuth]

Dont think the blank screen means there are so many it can't list them all.. This happens every update. Blank yes or no.. And usually means a block name might have changed but not the ID.. In this case hitting yes will just load your game like normal.

What you don't want is to have a list of items on that screen it doesn't recongnize.. But at any rate pushing yes loads the game anyway with the missing blocks if any.. And no just shuts it down.

 

[superriku11]

Glad you solved it. Generally Minecraft mods are actually built with Java 7 in mind these days although some still use 6 to maximise compatibility.

Yeah I'm aware most mods are made with JDK 7. Unfortunately some library that Minecraft utilizes through Java isn't updated on OS X like it is on other systems, so it forces you to use Java 6. It seems to only be in the modpack though, since I can load regular Minecraft with Java 7. So I assume some mod is responsible for it, in which case, that mod really should just fix itself rather than hoping the library gets updated soon.

 

[EternalDensity]

This happened to me the previous two or three times I updated (I clicked Yes with no ill effects) but when updating from DW20 5.00 to 5.01, it actually had some text there for a change, mentioning two items I haven't used yet (one was omniwrench) so I clicked Yes again and it seems to be still fine.

[edit] Relevant: http://www.reddit.com/r/feedthebeast/comments/17jalk/decisions_decisions/ (currently the top post in /r/feedthebeast)