-
Notifications
You must be signed in to change notification settings - Fork 5
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
zeroth scan/map visability (pc 5.7) #163
Comments
Would you say this is a PlayerShip version of NPC "Map visibility (bit 4.3, int)"? |
yes it is, ShowOnMaps is a good title, we are going to have ShowOnMaps appear in some of the other objects soon probably, I still slightly like ZerothScan - at a minimum we need a clear way to say ShowOnMaps/ZerothScan is the same slightly odd field as FirstScan and SecondScan (thus my suggestion of ZerothScan, a link in the docs works as well or having a single place we properly describe it or probably other) |
I don't feel that "zeroeth scan" is all that good of a name for it, considering that it really doesn't have anything to do with scanning. In a limited sensor range game, a ship can go out of range and become invisible, regardless of how many times it's been scanned. |
sure - then can we have some way of linking the format of the bitmask for FirstScan SecondScan and ShowOnMap across the different objects - just so long as there is an easy way to realise all these things are highly related I'm happy |
Having renamed my PlayerShip.Unknown57 to ShowOnMaps:
|
Think this was resolved by #185 but feel free to reopen if you disagree. |
player 5.7 is a bitmap in the same form as first scan or second scan for map visibility (like npc 4.3) I half suggest calling this zeroth scan to make it obvious that its related in form to first scan and second scan
The text was updated successfully, but these errors were encountered: