Codechange: Scan station catchment tiles when removing station from nearby towns/industries. #12129
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation / Problem
On a map with lots of towns and industries, along with lots of stations, iterating the complete town and industry pool to (possibly) remove the station from town and industry nearby stations lists can take some time.
This is most noticeable when a company goes bankrupt as lots of updates are done together, but also has a small impact on removing stations parts.
Description
Stations also have a list of catchment tiles covered, which is updated after the town and industry nearby station lists are cleared.
So we can avoid iterating all towns and industries when updating station catchment, and scan a limited portion of the map instead.
This provides a modest performance benefit when many towns/industries exist:
reset_company 1
stop_ai 2
Limitations
Relies on
catchment_tiles
not missing any tile. It shouldn't do as that would cause other issues too.Checklist for review
Some things are not automated, and forgotten often. This list is a reminder for the reviewers.