Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ingame clock #5890

Closed
DorpsGek opened this issue Jan 31, 2014 · 3 comments
Closed

Ingame clock #5890

DorpsGek opened this issue Jan 31, 2014 · 3 comments
Labels
component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)

Comments

@DorpsGek
Copy link
Member

Simons_Mith opened the ticket and wrote:

Could we have a clock ingame? Showing the real time. Wesnoth has one and it's really handy. Clock functions would also have a particular game function in OTTD I'd be very keen on: The ability to set the autosave frequency to not every X number of game months, but to every X number of real-time hours, which would do a much better job of protecting people from losing large amounts of work on a big map.

Reported version: Version?
Operating system: All


This issue was imported from FlySpray: https://bugs.openttd.org/task/5890
@DorpsGek
Copy link
Member Author

survtur wrote:

Are there any othes usages except autosave by timer?


This comment was imported from FlySpray: https://bugs.openttd.org/task/5890#comment13048

@DorpsGek
Copy link
Member Author

Simons_Mith wrote:

Well, after autosave and having an on-screen clock for when you're playing in full-screen mode, other possibilities might include a timer for network games and then a built-in alarm.

The timed autosave would be the most useful element, I think, then merely having a clock the next most useful, and then the other uses would be potential future option. As I said, Wesnoth has a clock, and like OTTD, it too is a game that can eat /hours/ without you noticing. In fact OTTD is probably worse, because it's more open-ended.


This comment was imported from FlySpray: https://bugs.openttd.org/task/5890#comment13049

@DorpsGek
Copy link
Member Author

andythenorth closed the ticket.

Reason for closing: Won't implement

OpenTTD does not need to jump the shark (again - for diplomacy, I won't say where else it has happened). https://en.wikipedia.org/wiki/Jumping_the_shark


This comment was imported from FlySpray: https://bugs.openttd.org/task/5890

@DorpsGek DorpsGek added component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/) enhancement labels Apr 7, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
component: interface This is an interface issue flyspray This issue is imported from FlySpray (https://bugs.openttd.org/)
Projects
None yet
Development

No branches or pull requests

1 participant