Daniel Roschka 274500eb37 Always use STUN for hosting games using the lobby ... This makes using STUN mandatory for games hosted using the multiplayer lobby. The motivation for that is a reduction in complexity, because right now if STUN is disabled we use a home-grown STUN-like logic, which got implemented before Pyrogenesis got STUN support. That home-grown logic relies on a custom ejabberd module (mod_ipstamp), which inserts the external IP-address of a host in the response messages when a host registers a game. Originally mod_ipstamp was also used to inform all potential players of a hosts IP-address, however that has already been removed to let hosts to only share their IP-address with players actually joining their game. Removing the home-grown logic and instead always relying on STUN removes complexity in Pyrogenesis and the lobby server and also eases hosting games for players, as they don't have to figure out anymore whether they need to enable STUN or not. These changes shouldn't negatively impact the ability of Pyrogenesis to handle different types of NAT or broken networks. There is one difference though: While the custom logic using mod_ipstamp utilized TCP as transport protocol, the STUN implementation in Pyrogenesis currently uses UDP. That doesn't allow hosts with UDP-connectivity issues to resolve their external IP-address anymore, however without UDP-connectivity they aren't able to successfully host games anyway, as the actual game updates are transferred using UDP as well.		2025-01-20 06:52:14 +01:00
..
JSInterface_Network.cpp	Always use STUN for hosting games using the lobby	2025-01-20 06:52:14 +01:00
JSInterface_Network.h	Revert non-ASCII characters from source and configuration files introduced in 157c6af18e.	2023-12-03 00:30:12 +00:00