Removed an instance of a bad practice (letting the clients pass their
own rpc caller id to the server and having the server trust it), as
well as making the server the only one able to unpause the game.
The first of the two is a fairly harmful habit to teach, especially
in a first introduction.
Also made the bomber demo way more explicit (and verbose) by avoiding
as many ambiguous pronouns as possible, instead being quite explicit
about which nodes or methods are being referred to at any time, and
also some intermingled motivations/reminders for why these steps are
being taken.
This also documents how to build dedicated server binaries.
The part about compiling will need to be updated for Godot 4.0
once the server platform is usable again.
This also removes prompts before commands so that they can be
copy-pasted by triple-clicking without selecting the prompt.
We used to broadcast player info on connect and have the server relay it
to other clients.
With this approach, each peer (including server) sends its own info once
to other peers as soon as they connects.
When a new player connects, it is notified of all the already connected
peers by the `network_peer_connected` signal.
Any already connected peer is also notified of the newly connected peer
by the same signal.
4-space is our convention for indented blocks and should be used consistently.
The only exception is for C++ code which is tab-indented, as the engine code.