0000716: Last started/saved game not remembered (+ enhancement suggestions)

View Revisions: Issue #716		[ Back to Issue ]
Summary	0000716: Last started/saved game not remembered (+ enhancement suggestions)

Revision	2011-03-07 23:51 by Zamolxis
Additional Information	SUGGESTION 1 (very nice to have): H3 remembered our last selection only as long as we went back to the same sub-menu (SP, MP or Campaign). So if we clicked the MultiPlayer icon by mistake for example, our last new/save/load game choice for Single Player was lost. So the request is if VCMI could keep separate trace of our last selections for each sub-menu: SP, MP, Campaign and maybe also Tutorial. SUGGESTION 2: When going back to New Game, H3 only remembered our last selection for the scenario, but not all the options we chose. It may be useful if VCMI could remember also our choices for Difficulty, as well as any Advanced Option. Like this, going back to the menu and clicking on Begin would really act like Restart Scenario, with the useful difference that the player will see all his/her custom choices and will have the possibility to modify only one of them (i.e.: max a couple of clicks, as opposed to 20-30 clicks to make again all town/hero/bonus selections). SUGGESTION 3: When going back to both New or Load lists of games, it would be nice if VCMI would also preserve our previous column sort criteria (Player #, Map Size, Version, Name, Victory/Lose condition). I'm less sure about the map size filters on top, if they should be added to this feature as well (I'll leave this up to you, as I see both advantages and risks in having filters on by default). SUGGESTION 4: For the main feature request in this report, as well as the 3 suggestions here above, it'd be nice if VCMI could preserver player's last choice also across sessions. Like this, even if we take a longer break from the game at some point, when we come back, after days/weeks/etc, we can see what was our last choice and pick up from that if we want. This would be a very nice to have again, especially as long as we don't have a "Sort by date" button/column, which would probably be harder to implement as compared to this.

Revision	2011-03-08 00:12 by Zamolxis
Additional Information	SUGGESTION 1 (very nice to have): H3 remembered our last selection only as long as we went back to the same sub-menu (SP, MP, Campaign, prolly also Tutorial). If we clicked the MultiPlayer icon by mistake for example, our last new/save/load game choice for Single Player was lost. So the request is if VCMI could keep separate trace of our last selections for each sub-menu: SP, MP, Campaign and maybe also Tutorial. SUGGESTION 2: When going back to New Game, H3 only remembered our last selection for the scenario, but not all the options we chose. It may be useful if VCMI could remember also our choices for Player Difficulty, as well as any Advanced Options. Like this, going back to New Game > ... and clicking on Begin would act pretty much like Restart Scenario, with the useful differences that the player will see all his/her custom choices and will have the possibility to modify only what he/she wasn't happy with in a couple of clicks, rather than tens of clicks to do all the setup again (flag/towns/heroes/bonuses/duration/difficulty). SUGGESTION 3: When going back to both New or Load lists of games, it would be nice if VCMI would also preserve our previous column sort criteria (No of players, Map Size, Version, Name, Victory/Lose condition). Note: I also thought of the map size filters on top, if they should be added to this feature as well, but I'm not sure if it should include them. I'll leave this up to you, as I see both advantages and risks in having filters on by default. SUGGESTION 4: For the main feature request in this report, as well as the 3 suggestions here above, it'd be nice if VCMI could preserve player's last choice also across sessions. Like this, even if we take a longer break from the game at some point, when we come back, after days/weeks/etc, we can see what was our last choice and pick up from that if we want. This would be a very nice to have again, especially as long as we don't have a "Sort by date" button/column, which would probably be harder to implement as compared to this. Note: The suggestions shouldn't prevent the report from being marked as Resolved if the main feature is implemented. They are just listed here for debate. If I get positive comments, but in the same time they're something that cannot be done at this stage, I can always make splits, creating separate reports for each of them.

Site | Forums | Wiki | Slack | GitHub