So, I've been working very hard on a BTB map lately, and I thought it was turning out quite well. But then for some reason when I clicked on my map, it loads up another map. After 10 minutes of trying to figure out what was wrong, I gave up and started over. Then when I was almost done with the map, it happened again. My map was lost just like before. So I'm wondering if this is a glitch or if there is something wrong with my Xbox. As you can imagine, I'm getting pretty frustrated by this. But if I need to, I will start over. So is there any way to fix this/ get my maps back? Thanks.
Sorry dude, but it sounds like you overwrote the save for that map. When using the regular "Save" option, Forge will overwrite the last map that was saved and not the current map you are editing. So, say you are working on your BTB map, save it, and decide to work on another map. If you choose "Save," it will not save over the current map like you'd expect, but rather the map that was saved before it (your BTB map!). This means you should always use "Save As" any time you're working on a map for the first time that day, just to be sure. Does this sound like something that may have happened?
This definitely sounds like the infamous overwrite glitch. Like Lynx said, your best option is to just use the "Save as new" option and rename it a little bit later of a version i.e. v1.1, v1.2. Not only does this help avert this glitch, but you can go back to a later version if you went a direction with the map you ended up not liking. It may require a little more work, but a little extra effort will save you quite a bit of heartache.
Easiest way to avoid this is every time you start a new forging session just reload the map from the menu. I have lost no maps doing this simple action to that overwrite glitch.
This is 100% correct. I have had this issue before when an entire finished map of mine was deleted. The only difference, I realized, was that I hadn't reloaded my map from the file menu. Ever since I have started loading the map every single time I have not encountered this problem.