Warden Updates

"Basically the new change in the page check for Warden requests a particular value which was always a static value of 0x00 in the past. Several developers assumed it would continue to be a static value, but in this case 0xE9, 0xE7, or any other value as determined by the modules.

Using static values (as set in the INI file posted in this thread) will most likely allow the Warden checks to be handled to allow a bot to stay connected. The issue here occurs when the value changes. If the wrong value is sent, the account will be silently flagged and will most likely (as far as we know) be terminated during Blizzard's next culling.

Simply put, the values in the posted INI should keep bots connected, but will likely result in a ban later down the road.


I'm currently unaware that any BNLS servers have been updated to handle the updated check. I heard of one being updated a day or two ago, but it was mentioned shortly after that the response value changed and the new functionality would no longer work safely. "