No ability to set BNCS server port

[Davnit]

Should at the very least make it a config override, if not supporting <hostname>:<port> format for the server field.

Needs to work when connecting via proxy as well.

[dottereldesign]

Does this work on the currnet battle.net?

[carlbennett]

Does this work on the currnet battle.net?

StealthBot has no option for configuring an alternative port than 6112, which is no problem for current Classic Battle.net™ since it presently uses that port officially. This is an issue for third-party research and development servers that are on a different port for some reason, probably related to NAT port forwarding. In these rare cases, StealthBot is simply unable to connect to those development servers on an alternative port due to code limitations that specify the port as 6112.

Users should not concern themselves with this, the games use 6112 officially, the games also are incapable of switching the port, and servers should therefore be listening on that port, which is where StealthBot connects to since it emulates the games at the protocol level.