If you are not connected to the Internet and you edit a Halo 2 forge map and then try to save your new version as a new name using “Save As”, the system will not prompt you for the new file name but will instead save another copy of the map with the same name. There’s no way to “Save As” an existing forge map in offline mode.
This is a horrible bug!
Can anyone reproduce this?
Well, it’s been 2 years with no replies, and this bug still exists. Doesn’t anyone at 343 care about Forge bugs? All I hear about is fixing matchmaking bugs. Please fix this.
I know – you’ll probably lock this topic because it’s too old. But the problem still exists, so please add it to your bug list, if you’re keeping a list. Thank you.
There are a bunch of forge bugs, this being one of them. Unfortunately, there’s no comprehensive list of them all.
I know there are lots of other forge bugs. Many are quite severe. For example, spawning never worked right with forge maps. The only work-around is to have a single spawn point in front of a teleporter, and that teleporter leads randomly to a set of “spawn teleporters” which are located where you really wanted the spawn points to be. A really ugly hack for something that always worked fine on previous Halos.
The bug I mentioned in the first post did not exist when they first released MCC. It was a regression that occurred in one of their updates. Before the update, I was able to “Save As” offline without any problems.
Doesn’t exactly inspire confidence in 343’s Quality Assurance process.