| Age | Commit message (Collapse) | Author |
|---|
|
|
|
doxygen can create better documentation
|
|
|
|
the server's IP
|
|
clients joined:
* Clients can't be starved from joining the game
* Clients will see the amount of clients actually waiting in front of them, instead of the amount of waiting clients in total
|
|
allocate it for clients that are there to just get a list of companies. This means that these short lived clients won't be seen by the admin network in their client queries anymore
|
|
ClientSocket
|
|
admin "core" as they send IP addresses to the admin "bots"
|
|
ClientSocket, after all the Socket is the bit that's associated with the network
|
|
ClientID, which later resolves the IP address to ban. This to consolidate the knowledge about resolving IP addresses
|
|
client list at clients
|
|
NetworkClientSocket::GetByClientID
|
|
NetworkClientInfo::GetByClientID
|
|
removed (instead of previously selecting some other client)
|
|
|
|
rather the client would kick itself due to an unexpected packet
|
|
specifically for a particular value
|
|
to do so anyway
|
|
requesting the map
|
|
|
|
when SendPackets closed the connection
|
|
closing the connection as that wants to acquire the mutex again
|
|
reconnecting while the server is still saving the savegame
|
|
many NetworkClientSockets/Infos
|
|
|
|
possible to change the password of other companies (on the server)
|
|
servers, so move it to network_server.* (dihedral)
|
|
changes (dihedral)
|
|
connection is closed (Rubidium)
|
|
and remove some unneeded casts
|
|
|
|
packet for longer company names (in bytes), by truncating the names if needed
|
|
|
|
savegames to send to the client asynchroniously. This will reduce the lag of the other clients to the time it takes to make the memory dump and it will speed up downloading the map as the download starts earlier (possibly with a slightly lower bandwidth due to slow compression). This should also fix the lag message people get when the savegame compression takes more than a few seconds.
|
|
client, don't write it to disk but create the packets immediately
|
|
later in the download process
|
|
|
|
receiving, our frames
|
|
style
|
|
|
|
transferred file are the same file and not different ones
|
|
lagging because of connection trouble or lagging because the client is just slow
|
|
|
|
when receiving some packets and don't send some when the clients aren't ready for them
|
|
|
|
into 3 separate packets
|
|
|
|
player leaving the game
|
|
so they're documented in the "same" place as UDP, content and admin packets (dihedral)
|
|
(dihedral)
|
