I can answer some of your questions: > * At present, EOS linger is only triggered by victory or defeat. Quit > behavior is unchanged. There are a couple of other EOS states in > WML that I don't understand; "continue" is one of them. I am not > clear on whether they should put the player in linger mode. > Continue probably shouldn't put the user in EOS mode, though I suppose it _could_ and it wouldn't cause major problems. Continue is used for talking scenarios, the difference between it and "victory" being that it doesn't display a "VICTORY! Gold: Turns left: Bonus:" etc message and it doesn't apply the 20% tax on retained gold. Since there's no message at the end of continue scenarios telling the user the game is over, it would probably be confusing to put them in such a situation.
Continue may also be used in some scenarios as a way of removing the 20% tax, but it shouldn't be. (BTW, I would like to suggest making the percentage of gold retained customizable in WML... have an attribute in [endlevel] called retained= that defaults to 80%. Often on RPG scenarios and such you want to let the user retain all of their gold plus any they got on the current scenario, and there's no way to do that currently that I know of...) > There is also a related issue about what how to change autosaves, and > whether it should be changed at all. > > My own preference would be to abolish them entirely. When users want > to save game, they can use the menu. This choice is now available > at any time, including at EOS. > > However, it has been pointed out to me that the other developers like > having autosave enabled by default because it means they are much more > likely to get savefiles with their bug reports. > > Matters are further complicated by the fact that SP players tend to > prefer start-of-turn autosaves, while MPP players tend to like > end-of-turn autosaves. > Autosaves are good, both for testing, bugfixing, and playing the game. They shouldn't be deleted, IMHO. It's true that we could force users to always save when they want to, but that doesn't mean we should - if we can make something more convenient for the user, we should. _______________________________________________ Wesnoth-dev mailing list [email protected] https://mail.gna.org/listinfo/wesnoth-dev
