Hello everyone,
Shortly after the Battle.net server maintenance on January 4th 2019, a new version check system was applied to Diablo 2 on the server side. We are looking into this but there is no ETA on a fix. This leaves only WarCraft 2 and Diablo 1 working on official Battle.net servers. This would affect all bots and not just StealthBot, and affects both BNLS and local hashing.
This is for the following errors:
and
There may be some bots that connected quickly enough after the reset, before the changes were applied, that are still online. They got lucky for now but will likely be kicked off soon during the nightly refreshes.
In-game bots use a different system and I do not know how they might be affected by this. We don't support them here.
If you still need a bot in your clan or op channel, and you do not have a WarCraft 2 CD key, your only remaining option is the chat API. This is the system that Blizzard has for chat bots moving forward. It provides a very limited set of features and won't work for everyone's needs but it's the only thing left right now.
StealthBot is not directly compatible with the chat API but I have made a program that allows StealthBot to interface with it, which you can download on GitHub, where I have full instructions for the process: https://github.com/Davnit/capidaptor
Shortly after the Battle.net server maintenance on January 4th 2019, a new version check system was applied to Diablo 2 on the server side. We are looking into this but there is no ETA on a fix. This leaves only WarCraft 2 and Diablo 1 working on official Battle.net servers. This would affect all bots and not just StealthBot, and affects both BNLS and local hashing.
This is for the following errors:
[BNLS] Error! BNLS failed CheckRevision. Please check the settings of your bot and try again.
and
[BNCS] Warden.dll does not support checkrevision for CheckRevision.mpq 1/4/2019 11:41:42 [BNCS] Make sure you have the latest Warden.dll from http://www.stealthbot.net/sb/warden/ [BNCS] Local hashing failed.
There may be some bots that connected quickly enough after the reset, before the changes were applied, that are still online. They got lucky for now but will likely be kicked off soon during the nightly refreshes.
In-game bots use a different system and I do not know how they might be affected by this. We don't support them here.
If you still need a bot in your clan or op channel, and you do not have a WarCraft 2 CD key, your only remaining option is the chat API. This is the system that Blizzard has for chat bots moving forward. It provides a very limited set of features and won't work for everyone's needs but it's the only thing left right now.
StealthBot is not directly compatible with the chat API but I have made a program that allows StealthBot to interface with it, which you can download on GitHub, where I have full instructions for the process: https://github.com/Davnit/capidaptor