-
-
Notifications
You must be signed in to change notification settings - Fork 125
Description
Description
Debatable how much of a bug this is but at the very least it is a default behaviour change that is not mentioned in migration section currently.
Presumably due to the change introduced in 0.4 with using AircraftType's actual MovementZone and SpeedType for landing zone checks (hook FootClass_IsLandZoneClear_ReplaceHardcode), Landable=true AircraftTypes that are not AirportBound can freely land on water as they please assuming their SpeedType has not been changed to one that prevents this (Aircraft usually don't declare SpeedType which uses default value of Winged which allows all land types to be traversed). One could consider this an expected outcome of the fix but it is also generally undesirable and currently entirely undocumented.
At a glance the previous behaviour and behaviour after if explicitly setting SpeedType=Track or something is basically identical, although this will also restore the original 'issue' of being unable to order such aircraft on water at all.
As a note, landable jumpjet vehicles with SpeedType that allows traversing water will not land on water as likely some part of the jumpjet locomotor processing blocks this, doesn't appear to be the same for fly locomotor.
Phobos Version
0.4
Conditions to reproduce
No response
INI code
[SOMEAIRCRAFT]
...
MovementZone=Fly
SpeedType=Winged
AirportBound=no
Landable=yesSteps to reproduce
- Acquire aircraft with
Landable=noandAirportBound=noin game. - Order said aircraft on a body of water.
- Watch as the aircraft comfortably lands on water.
Expected behaviour
- Aircraft refuses to land on water.
OR
- This change in behaviour is documented.
Actual behaviour
- Landable aircraft now land on water, modders are not informed of this change in documentation.
Additional context
0.4 is first stable release with this issue, present in some pre-0.4 dev builds as well.
Checklist
- The issue happens on the latest official version of Phobos and wasn't fixed yet.
- I agree to elaborate the details if requested and provide thorough testing if the bugfix is implemented.
- I added a very descriptive title to this issue.
- I used the GitHub search and read the issue list to find a similar issue and didn't find it.
- I have attached as much information as possible (screenshots, gifs, videos, debug and exception logs, etc).