-
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
Ship index #152
Comments
PlayerShip bit 5.8 is ShipNum, char/byte. |
Not sure what bit 2.2 became. Seems to still be an int. Almost always 0 except when it's 1 |
if you set the char of bit 5.8 to always be 0 you are unable to select any ship other than ship 1 (IE 0) on the client and connect - thus I think 5.8 has to be ship num, 0xff being fighter as suggested seem likely esp if it was a signed value and set to -1 as an "this is not a ship num" value (this presumably can be tested with captures?) |
Analysis of my "top 15 capture files with the most ShipNums", obviously messed up by those pesky humans being allowed to rename ships and even fighters, but hopefully fairly convincing?
Where |
Until v2.3.0, bit 2.2 of the player ship object was ship number (1-based). We are uncertain what field it is now. We suspect bit 5.8 is now ship index (0-based), but we've also observed a value of
0xff
, which puts makes that less certain. Ship number/index is a pretty important value to know, so let's try to figure out what it is.The text was updated successfully, but these errors were encountered: