0xf754c8fe:0x0e seen

[NoseyNick]

From a 2.6.0 game, which did have at least one Jump-Ship in it (specifically, a Warp Dreadnought and a Jump Ximni Missile Cruiser):
fec854f70e00000000000000e0d8fc3d # 2.6.0 payload
fec854f70e0000000000000064a2da3e # 2.6.0 payload
fec854f70e0000000000000084451d3f # 2.6.0 payload
fec854f70e00000000000000843f453f # 2.6.0 payload
0xf754c8fe is of course officially "simpleEvent" (#52), not sure what this subtype 0x0e is.

[NoseyNick]

Now seen 208 of these across 20 games, v2.6.0 and 2.6.204beta
NOT always Jump-ship games - that was presumably a red herring.
Will need to work out how the heck to reproduce this one :-(

Payload:
u32 subtype = 0x0e
u32(?) unknown1 = 0
float unknown2 = 0.001 to 0.887

[NoseyNick]

Transferring comments from dup #109 :

Observed in the wild, 226 times in 25 games, 12 were v2.6.0, 11 were v2.6.204, 2 were v2.6.3

Integer type = 0xf754c8fe - officially JamCRC("simpleEvent") [Server to client]
Integer subtype = 0x0e
Integer (?) always 0?
Float (values 0,0.00475 - 0.8866 observed)

Seen a few times in "real world" games and a load of times in "playtesting for protocol hacking", which HOPEFULLY means I stand some change of reproducing it. Purpose unknown at this time. Was mid-game. DamCon teams were running around repairing stuff. Tried looking for the same floats in other places, doesn't match anything else.

The docs also mention __server_hypothetical__2 Type: 0xf754c8fe:0x02 - yes, there are two __server_hypothetical__2, one subtype 0x02 (never seen) and this subtype 0x0e

If nothing else, I guess this one is no longer "__server_hypothetical__", and the docs deserve some payload field/type details?

[rjwut]

I'm renaming the hypothetical and unknown packets after their type and subtype so that hopefully we don't get name collisions in the future.

[NoseyNick]

Do you feel e2132eb "fixes" this ticket, if 0xf754c8fe:0x0e still needs research ?
I don't mind either way, I'm happy to open another ticket if/when I ever find out more about 0xf754c8fe:0x0e if that's how you'd rather it was done?

I guess this is mostly a question of whether you'd prefer an empty ticket-queue, or a ticket-queue that includes quite a few "known gaps that need work"?

[rjwut]

Actually, it was a mistake to close this ticket. Oops.