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

Land info build date is also renovation date. #11123

Closed
Gadg8eer opened this issue Jul 9, 2023 · 2 comments
Closed

Land info build date is also renovation date. #11123

Gadg8eer opened this issue Jul 9, 2023 · 2 comments

Comments

@Gadg8eer
Copy link
Contributor

Gadg8eer commented Jul 9, 2023

Motivation / Problem

Originally posted by @DorpsGek in #4415 (comment)

We could ofcourse opt to be obnoxiously specific about what the date means: "Date at which the last construction or rebuilt at this station took place". But that bloats the interface for no good reason.

We actually need to update the build date as it's used by NewGRFs and TTDPatch/OpenTTD have behaved for a decade like this, thus changing it would break quite a few NewGRFs. Even then it would be wrong given the former example.

Originally posted by me here

Suggestion for "unfixable" station date "issue"

How about "Last build/renovation date" or even "Build/renovation date"? Shorter, just as accurate and not that hard to implement, unless I'm mistaken?
I get this is an old and unjustified "issue", feel free to close this immediately if the suggestion isn't useful.

When a station layout is modified in any way, the "Built: YYYY" section of the station's land info is also the renovation date. While fixing it properly would not be trivial, I propose a simpler short-term solution.

Description

Just change the basic string from "Built" to "Built/last renovated" or possibly "Most recent construction". 2TallTyler suggested "Built/renovated" to be as short as possible.

I added a minor change to the language file. Apparently I forgot to submit it.

Limitations

A more long-term solution is to record the original construction date and then also record the most recent renovation, but nothing in-between (it doesn't seem like anyone needs a history of the whole station).

Checklist for review

Some things are not automated, and forgotten often. This list is a reminder for the reviewers.

  • The bug fix is important enough to be backported? (label: 'backport requested')
  • This PR touches english.txt or translations? Check the guidelines
  • This PR affects the save game format? (label 'savegame upgrade')
  • This PR affects the GS/AI API? (label 'needs review: Script API')
    • ai_changelog.hpp, game_changelog.hpp need updating.
    • The compatibility wrappers (compat_*.nut) need updating.
  • This PR affects the NewGRF API? (label 'needs review: NewGRF')
@2TallTyler
Copy link
Member

Sure, feel free to make a PR with your suggested change. It would be this line in english.txt: https://github.com/OpenTTD/OpenTTD/blob/master/src/lang/english.txt#L2970

I am going to close this issue, as the bug tracker isn't really the place for suggestions; it gets cluttered way too quickly if we do that. 😄

Side note: I saw your translator request for en_US. I don't have the permissions to handle your request, but please don't try to fix this issue by changing a single translation — it needs to be done in english.txt and then propagated down to translations. 😃

@ldpl
Copy link
Contributor

ldpl commented Jul 9, 2023

Part of the problem also is that station build date is sometimes more useful than modification date.

@Gadg8eer Gadg8eer changed the title Suggestion for "unfixable" station date "issue" Land info build date is also renovation date. Jan 5, 2024
Gadg8eer added a commit to Gadg8eer/OpenTTD that referenced this issue Jan 6, 2024
Fixed OpenTTD#11123 in the primary text file.
2TallTyler pushed a commit to 2TallTyler/OpenTTD that referenced this issue Jan 12, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants