| Age | Commit message (Collapse) | Author |
|---|
|
|
|
doxygen can create better documentation
|
|
closed" before having passed the remaining buffer which causes OpenTTD to think all connections are "incorrectly" terminated, i.e. without the "I'm leaving" packet from the client. So let the client wait a tiny bit after sending the "I'm leaving" packet and before gracefully closing the connection
|
|
client list at clients
|
|
NetworkClientInfo::GetByClientID
|
|
rather the client would kick itself due to an unexpected packet
|
|
client to spectators, causing issues in bankruptcy (Rubidium)
|
|
client is actually fully connected
|
|
|
|
|
|
|
|
possible to change the password of other companies (on the server)
|
|
|
|
NetworkClientSetCompanyPassword (dihedral)
|
|
(dihedral)
|
|
and remove some unneeded casts
|
|
|
|
HashCurrentCompanyPassword(), make it static
|
|
deterministically when/if the value of NETWORK_SERVER_ID_LENGTH is changed
|
|
|
|
|
|
seconds locally, don't see that as lag of the server. Also increase the client side's lag thresholds a bit
|
|
just keep it in memory instead of writing it to a file
|
|
load), and add support for (safe) loading with a LoadFilter
|
|
later in the download process
|
|
receiving, our frames
|
|
style
|
|
transferred file are the same file and not different ones
|
|
connection was lost
|
|
at a given moment
|
|
into 3 separate packets
|
|
downloaded savegame wouldn't be closed, and validity of the handled wasn't checked in all cases
|
|
company; in coop games that does not spread clients at all, and most companies have a low number causing it not to be spread out either. Use the ClientID instead. Based on a patch by dihedral.
|
|
so they're documented in the "same" place as UDP, content and admin packets (dihedral)
|
|
search restrictions.
|
|
network_client.cpp
|
|
|
|
sensible name
|
|
like UDP/content packet handling
|
|
NetworkClientSocket for server and client side
|
|
|
|
(from clients and the server)
|
|
|
|
|
|
|
|
static const variables
|
|
with company ID > 0 would be shown as if they were a spectator
|
|
to spectators
|
|
while joining, e.g. when entering a company's password. This caused the client to be in the wrong company (according to the rest of the clients) and the client being kicked on the first command
|
|
|
