Spawn time problem in forge. Objects lost forever?

I'm surprised that's even possible, it wasn't in Halo 3 for exactly this reason. It's odd that Bungie would change that.

However, you should be able to force spawn the objects by selecting one of the same object that hasn't been 'never/no'd (spawn a new one if you did it to all of that object), then go to the object properties and set the runtime minimum to the highest possible. This should force the 'never/no' objects to spawn so you can change the respawn settings back to what they should be.

 

If you spawn another object of the same type set the settings to Place at Start: False and Spawn Time: Never, and then without leaving the match (so the item is still sitting there) hover over it or select it and hit B to bring up the Tools dialogue box. Select "Delete all of these." It should delete any objects of the same type and settings from your map for good.

Before doingthis, note your budget, and make sure when you delete all o those, your budget increases by double the amount of the item you just placed (meaning that both got deleted). If it doesn't, you'll need to make sure you're setting everything on the new object the same as the old one that you can no longer get to.

EDIT: Damn, ninja'd! With another perfectly valid way to fix this problem.

 

I meant to suggest the 'delete all of these' option as a backup path to fixing it, though in answer to your question: no, it will delete all of that type of object, regardless of spawn settings. If you have others of that object that you'd rather not delete, you should avoid this solution if at all possible.

Can you try setting the runtime maximum even higher than the number currently placed on the map, then raise the runtime minimum to how many there actually are, thus forcing the objects to spawn? I don't know why the runtime max is changing by itself like you said, but hopefully this should allow you to get around it.

 

Spawn another of the same object that you perma deleted, press B to goto option tools, and select 'Delete all of These'.

There you go, the gone objects are now,, gone?... start a new round, and replace them where you wanted them to be

 

Might wana read the rest of the thread before posting there, dude .

EDIT: On the subject of the auto-save: Forge seems to keep whatever you've done to a map when you quit, even if you haven't saved before quitting. However, it doesn't actually auto-save, just keeps the changes as a sort of temporary file. If you reselect your map from the map list, it should revert to the point at which you last saved, so no need to back up with duplicate map files like you've been doing.

 

Have you started a new round with this done?

 

might want to realize when I came to this thread, your post wasn't there Sorry i don't refresh the thread before posting.

 

Hmm, I don't know what to suggest then I'm afraid. I'll try to get in to Forge and see if I can recreate this tomorrow, then try and come up with a fix (it's 5am here so I should really be getting to bed ). If someone else doesn't reply with a workable answer before then and you need a solution sooner, you may just have to go with the 'delete all of these' option and then just replace the objects you didn't want to delete but will have to by using this option. Time consuming, I know, but it sounds like it may be the only way around it at this stage sadly.

Sorry, I refreshed after posting my comment and looked at the users viewing the thread to see if the OP had checked back, I didn't see anyone else apart from him on the viewing list so, when I saw your post, I thought it was a pretty safe bet you'd just come in and only read the first post. Based on that, and the fact that your post therefore took over 10 minutes to type based on what you're saying, I'd say it was a pretty safe assumption. However, apologies since this apparently wasn't the case.

 

Glad to see you got it working, and apologies for my answer being a bit off. The delete all of these option is indeed the last resort, but it's good you didn't have to revert to it.

However, seeing as this is still a legitimate issue, working to find an easy fix is still a worthwhile endeavor. I'll fiddle around with it when I get my Xbox back tomorrow.