ScorchDroid 0.9.2

A privacy fix, and a tutorial that describes the controls this version actually has.

Fixed

• A single-player game no longer advertises itself. It was registering an NSD service on the network and forming a Wi-Fi Direct group — which holds the radio, can keep the device off its normal Wi-Fi, and announces a solo game to anyone looking. Every game on this port runs a server, because there is one engine and it is always the host, but that is an implementation detail and is no longer treated as permission to publish. The listening socket stays open, so a solo game can still be joined by someone told the address by hand — it just isn't announced to the room.
• The HUD no longer spends a line on your own IP address in a solo game, and the Wi-Fi Direct status messages no longer fire there. One of them is how this was found: "No Wi-Fi Direct: the nearby devices permission was refused" greeted the player over the tutorial's opening card.

Changed

• The tutorial teaches 0.9.1's controls. It still described separate weapon and FIRE buttons; there is now one wide bar that names its weapon, tapped to fire and held to change weapon. A new step covers the hold, which is the one control in the game that announces itself to nobody.
• Its slider step stopped lying by omission. It named the two aiming sliders by their readouts, but a readout only appears while the slider is moving — so at the moment the card is on screen, neither slider reads anything. Two of the three sliders read degrees in any case. It now says how to tell them apart: drag one and watch.
• README corrections. Desktop cross-play now has a test guarding its two foundations (the protocol strings and the mod manifest), the suite is 413 checks rather than "over 200", the client/host join runs twice — over TCP and over a socket pair through the same bridge Bluetooth uses — and there are twenty-three patches, not eighteen.

Notes

413 host-test checks pass. The solo/hosting split was verified as an A/B inside one process on an API 34 emulator: a single-player game logs nothing from either LanDiscovery or WifiDirectTransport, while a Host Game started from that same process logs addLocalService succeeded, createGroup succeeded and Registered LAN service.

Signed with the same key as every release since 0.5.0 (b9ae6490…3bafbb), so it installs over a previous one.