If you have ever been to this website before, you should have noticed the BNLS Server Status panel on the right, along with the Battle.net Server Status panel. These two panels contain servers that you can use with your Battle.net bots.
Now what most people probably knew, these servers do not get updated periodically, so servers would appear online when they are truly offline, and vice versa. This is no more.
I have created a simple program that connects to any MySQL server, retrieves the table full of servers, connects to each server individually, and then updates its online/offline status. I also enabled a timer that I can set to any interval I want (I can make it every 30 seconds, or even once every day if I want).
So basically all I am saying is that these server panels are now periodically checked for uptime status and will be updated accordingly. Right now I have that interval set to every 5 minutes, but I may variate it occasionally for my own reasons without notice. I would also like to stress that these servers are checked from my computer using my internet, this means that if I cannot connect to them or an error occurs while connecting, the server will be marked offline, even if you are able to successfully connect. If such a case occurs however, to where my internet does not function properly, then I probably would not be able to update the servers anyway, so you shouldn't worry about this.
- Fixed an issue preventing some players from accessing offline play from the login screen.
I had taken notice that all (most, anyway) the BNLS packets were still on the Raw-setting, meaning they were new and documentation for them was changing often.
I have since then updated all of them to the Normal-setting, which means they are documented and nothing is changing anytime soon; they are considered final and any revisions will be made in a new packet id. While I was doing this, I had also noticed that the format of most of the packets were not formatted conveniently and the related links were not given or were wrong, so I also updated the formats so they display conveniently and I added the proper related links.
I also added a new BNLS packet that is not really part of the official documentation, but was necessary to add since it can be received on some servers running BNLSWarden. The packet id is
0xFF, which indicates that your IP has been restricted. All BNLS-enabled clients will operate normally without recognition of this packet, but if a client wishes to support it, they are more than welcome to. It will never be received unless the server sends it to you after you connect. More information about the packet can be found in its remarks section.
Along with that new packet, I also added the BNLS_WARDEN packets, but I did a poor job. Anyone with editor access: feel free to revise it.
- Fixed an issue where campaign mission victories would not always trigger properly.
- Fixed an issue where some players were unable to access single-player features.
For those who live under rocks and have not come out recently: StarCraft 2 has been released and has been out for sale since July 27th.
StarCraft II: Wings of Liberty - Patch 1.0.1
To get the latest news and interact with the community, visit our brand new StarCraft II website (http://us.battle.net/sc2/en/). Be sure to check out our Game Guide for an in-depth look at StarCraft II gameplay. We wish you all the best on your journeys through the embattled Koprulu Sector!
-Campaign saves have been optimized. -Fixed an issue with sound not playing on some 7.1 systems.