Descriptive Problem Summary:
Ping topics (world.Export("byond://[ipPort]?ping")) have become unreliable, possibly due to my network being stressed. Even after establishing a supposedly persistent connection, ping topics will often return null, it does this almost instantly, which would seem to imply that the connection is not timing out, but that something is just failing somewhere in the communication process. Attempting to use this method to contact remote servers almost never returns an actual result. Using this method to determine if servers are "alive" is somewhat detrimental with such unreliable success rates, and if topics aren't getting through at all then this is even worse in a situation where vital information needs to be distributed (haven't been able to test fully test this yet, but topics in general do seem to always register, even ones sent from external sources).
On a semi-related note, it appears that IP and Ports have been removed from the &format=text information available on hubs (if it was ever there to begin with?), and that the provided server "url" is completely worthless for sending data to.
Numbered Steps to Reproduce Problem:
Attempt to acquire a "ping" from a BYOND server using world.Export("byond://[ipPort]?ping")
A ping is always returned if the server is alive and the connection can be made
The ping never has a 100% success rate, even on locally hosted servers (contacted using the external IP), and is almost 0% on remote servers.
Does the problem occur:
Every time? Or how often? Every when hosting on my network
In other games? Yes
In other user accounts? Most Likely
On other computers? Network stress may be relevant, it used to work on my dedicated server
Oct 20 2011, 3:21 pm