Replace pf_special with a scoped enum (PathfindingFlag) and add more flags #76026
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.
Summary
None
Purpose of change
The current flags do not support all functionalities required (e.g. whether a piece of terrain is sheltered or unsheltered), and lack granularity with e.g. GOESUPDOWN requiring extra checks for ramps, whether it goes up or goes down, and so forth.
Additionally, using a scoped enum is good practice and will hopefully prevent accidental misuse of the enum type.
Describe the solution
Part of #75945. The additional flags aren't presently used as they are intended to be part of a new pathfinding implementation.
I've assigned the
RAMP
flag to implyGOESUP
and notGOESDOWN
. I'm not sure if this is correct.Describe alternatives you've considered
Testing
There have been exactly zero functionality changes. The new flags are compatible with the old ones, and have been swapped in where appropriate. If it compiles, it should run.
Additional context