LexManos

The level.dat is backed up before writing for this exact reason, erroring while writing. Use the backup. There isn't anything we can do about stuff like this. The world isn't 'destroyed' it simply has different mappings. My suggestion, stop doing things that kill your memory.

You should not be able to get that type of error from that version of the installer. Either way, run the installer from the command line and give us the log. It looks like you're not connected to the internet.

Bah I hate crowdin its a pain to update files. The next build will have this fixed. you could always download the corwdin files and use it as a resource pack: https://crowdin.com/download/project/minecraft-forge.zip

Try again

You're right this doesn't belong here, it's a issue in the Bigreactors and EnderTech mods.

And thats why I didn't respond to you when you first posted this. I'm not going to get into this argument. Properly thought out suggestions and feature requests are accepted. These do not qualify. Locking thread before this turns into a flame fest.

I wanted to implement something like your loader screen because I thought it was more then just a hack. After reviewing it, it wasn't worth implementing. As for the others, they are either already completely possible with current hooks, not thought through, horrible names, or just horrible concepts in general.

Update Forge and read the EAQs -.-

IronChest{5.4.1.702} [iron Chest] (ironchest-universal-1.6.4-5.4.1.702.zip) Unloaded

Logs

I don't have time for trolls, if you're not intentionally trolling then you are sorely misinformed on how programming, the world, and minecraft work. Tired of this shit.

1) We dont support 1.6.4 -.- 2) THere is ALWAYS a log of some kind, there are these awesome things on your launcher called tabs. One of them being 'Developer Logs' you know cuz its kinda freakin important.

*waves magic wand* Everything 'works' now. That is all we can do unless you provide us with the logs like we ask -.-

Seems your having graphics issues, update your graphics card and remove anything you have installed that isn't vanilla or Forge. Also use the spoiler tags next time.

Sadly that is not something that we can tell you right away what is the issue One of the mods you have installed is trying to generate a structure without well, telling minecraft the pieces. Not something we can deal with as it's a mod issue.

Because Mojang, but yes, 1.8 they change ItemStacks to save/load from names if they are available. The whole 'save storage space' is a moot issue when it comes to item stacks, because there simply isn't that many of them to be an issue. But ya remember that vanilla data is very tied to the specific universe that you're dealing with. IDs are not guaranteed to be the same across universes.

Sucks to be you, you should fix your graphics card issues. You will not get support for making mods for older versions here. If your computer is as you say a year old it should have no problem running 1.7.10 when configured correctly.

Again, we do not support making mods for older versions. You will get no support for that here. Update.

Do not mod for 1.6.4.

If whatever tool you're using to export the data is not saving it with either their full registry names, or a internal id to name mapping then this is a fault of the tool you're using not Forge. IDs mean NOTHING anymore. And will NOT be the same between worlds and setups, this is why we synchronize the data when connecting/loading worlds. It should not mess up existing ids in maps, if it does provide full logs and details of this so that we can track it down. Most cases where ti does its due to modders breaking their item registrations. As for using a different ID map per world, Shouldn't happen within the same run of MC, however, again ids mean nothing anymore. This is exactly how it is suposed to function. When your current modset it loaded it assigns ids to everything. Due to you adding a new mod which most likely injects new items or blocks somewhere in the middle of the load order, it gets assigned its ids before part of the old mod set. This some ids get shifted. When loading old worlds we load the old id map and then assign any remaining new ids. Since the first load doesn't have this id map, and it should not. The ids will be different. Again the issue you're running into is caused not by Forge but by your export tools not respecting the name registry. 'Noppes' is wrong in this case it is entirely possible for him to save things via their registry name and not ids. Using ItemStack.save obviously saves via ids because this is what Minecraft is designed to do. Same reason World.save saves via ids. If you are saving data to be used across universes {sets of worlds} then you need to save in a id-agnostic way. Not side effect, intended behavior. Yes Feature Working as intended. Complain to 'Noppes' for doing it wrong. Or whoever it is that is writing the data to a cross world format.

Your log clearly states where the issue is by listing the stages of each mod. Take that mod, find what version of MC its for *googles* oh look its for 1.6.2 *looks at version in your log* 1.7.10... Not gunna work!

Not going to happen and not going to be supported. It can be done if you want to spend to time and learn how gradle works. However we can not support it due to legal reasons. As for the setup not having internet, you can setup your own lan with a cheap laptop, setup the db on there and have the kids computers pull from that. Anyways, there isnt much we can do to support you as I said because 1) you're in bad legal areas 2) it's out of our scope of support.

Not much we can do here, this is a crash in your native graphics drivers. You may want to try changing its version {if its up to date back date a version or two they may of introduced a bug}

EAQ

Feel free to PR it with these justifications, untill then dont care they are rather arbitrarily stuck in places anway.