General > Discussion

Do you want a save&quit option from the battlescape?

(1/3) > >>

damiac:
After my previous feedback thread, it seems that the dev team is willing to accept patches for a save&quit option from the battlescape.  Essentially, a player should be able to do a battlescape scenario over several playthroughs, but should not be able to easily savescum.  So the only option should be "Save & Quit".  This would need to save the current battlescape situation, write into the campaign save that a battlescape save exists, then exit the program.

The next time this campaign save is loaded, it needs to load the battlescape save, then delete it.  Think of a roguelike here, where you can save and quit, but once you reload, the save is deleted, thus preventing the player from reloading that save again to get a better result.

So, firstly, is there a great desire in the player base for a feature like this? I personally have trouble fitting a long battlescape scenario into the time I have to play games, so it would be great for me.  But I also can't code it!

So I figured it makes sense to see if the community is interested in something like this, and then maybe we can nail down how it should be implemented.  Finally, maybe we can actually create a patch to submit to the dev team to bring this feature into the game.  I think it would open the game to more people who can't devote long chunks of time, but still want to play the game.

geever:
I wouldn't say so... (about accepting)

-geever

damiac:
Yeah, in the thread where I brought this up originally, Geever brought up an important point, if this were to get submitted as a patch and accepted, the dev team would then need to keep it maintained whenever the battlescape variables change.  So due to that, any battlescape saving code would have to be a seperate fork, meaning it would be lost when the next version comes out.

Of course, since it seems to take a while between releases, the code would last for a while before it was obsolete. 

I am probably underestimating the work involved here, but wouldn't a battlescape save, at its most barebones level, just need to be able to dump all the battlescape information from memory into a file, and then on load, dump the contents of that file back into memory?  I guess I'm wondering if this battlefield info is all sitting in a structure, or if it's more scattered than that.

pete conway:
Nah!... I think that the option of retrying the mission is good enough, I understand that base attack missions are long and can be tedious but there are ways around that... one way is to make sure you have some cannon fodder to hand, and another is to ust the cameras,... neither of which I did when I first 'complained' about getting wiped on easy mode.

My opinion should not carry much weight here as I am a bit of a one life masochist... Hadrcore (one life) mode from Skyrim to Minecraft... Just one mistake is all it takes :'(

damiac:
Pete, the idea isn't about making the battlescape any easier, or even any faster.  It's about the fact that sometimes real life demands our attention, and it would be nice to be able to come back to a battle in progress, rather than having to start all over again, or play in a sub-optimal way, losing good soldiers, just to keep the mission time reasonable.

Navigation

[0] Message Index

[#] Next page