StarCraft 1.18.* support #63
Comments
|
Since the Linux version of this bot uses BNLS exclusively right now, I've labeled this a Windows bug. |
|
question for you. Do any BNLS or JBLS actually support 1.18 starcraft yet? If so which ones would work and what is the verybyte. |
|
Nothing supports it currently... Soon™ |
|
More research into SC 1.18 appears to suggest that hashes may become irrelevant. I'm removing the windows tag from this bug. |
|
have you found a route of being able to connect to the server wtih a starcraft client? |
|
They're working on it lol |
|
Hahaha. At least there is hope haha. |
|
Completely off topic. Is vb.net a language that can be used to make a bot in? If so where would be the best places to look for documentation on how to make a simple bot for bnet. Much apreciated if you can get me this info! |
|
If you're looking to write yourself a Classic Battle.net™ bot, you'll want to start here. You're free to choose whatever programming language you desire. Using Visual Basic, .NET or otherwise, makes you laughable to others. (Not that I have room to talk; BNRBot is written in Real Basic.) |
|
You should be able to connect with StarCraft 1.18 if you use jbls.davnit.net (or pyro.no-ip.biz) as your BNLS server. |
|
I have also updated bnls.bnetdocs.org. |
|
meh most classic bots are coded in vb6 so I don't think any one has any room to talk haha |
|
New development today: Bots using BNLS to connect using SC 1.18 get IP banned from West, East, Asia, and Europe. Still investigating further details and other developments. |
|
Carl I have not seen this to be the case. Ever sense that post about pyro.no-ip.biz I connected a sc bot on mirage and it has not been disconnected sense. I am currently on useast. I am not sure if that is something that is just your bot. Also I only have 3 bots connected on my ip. I have noticed connecting more then that can cause my bots to disconnect for some gay reason. Again I am using Mirage X |
|
(16:20:53) -- BNLS: Client version is too old (SEXP_IX86_1.18.0.1345.mpq)! I got this when connecting trying to reconnect on pyro biz with no cd key. I will update this once i get a fresh proxy to test with a cdkey again |
|
You will get banned if you use this. Stop using StarCraft. It is not working. It will IP ban you. |
|
I promise you'll get banned. Just be careful. Pyro's SC is set to wrong version now on purpose to avoid you getting banned. |
|
I just happen to notice that there was a sc1 update. And it appears that 90% of bots are unable to connect to the bnet servers. when I try connecting wtih a bot now I get this on my mirage bot - (22:22:50) -- BNLS: Connecting (bnls.war-lords.net)... Which honestly is pretty odd. I am also getting the same thing with sc clients. I will take a look into other bots to see if it is just mirage causing this issue Same thing with stealthbot - Getting the same thing with ruthless chat as well |
|
It means you've been IP banned, like the rest of us, like you were warned about. |
|
The log shows you were connecting with D2? I've been connected with D2 on MB for a long time now and no issues. Why is that? |
|
Existing connections are unaffected. Some bots are still connected with the older version of SC even. There's no problems until you reconnect. |
|
So it's just SC that is effected? Been a long time since I've read into this stuff, but how would an SC update effect D2 connections. |
|
(23:36:54) -- BNLS: Connecting (bnls.war-lords.net)... I can still game on the ip i did before. I think it has something to do with the way bots work now days All clients were effected including diablo 1 and starcraft shareware and starcraft japenesse. I have that sneaking feeling that bots are broken after the current update. How ever its something to look into. Every bot I have tried reguardless of the client or proxy i have used result in the same issue basically like the log i have shown above. That proxy in logs was only used to connect via d2xp. Hopefully we can find something to get around the systems that they are putting into place. What they are doing is ruining clans by continuing updates like this. Hopefully the devs behind all this stuff can find a way around all the fuckery they are putting in place. Edit I finally loaded a proxy on my d2xp account. I finally got a d2 bot loaded. How ever the key appears to be voided as previously pointed out. Which doesn't really bother me a ton. So it appears this is souly a starcraft update. How ever what is curious is the fact it does not ban me from playing the game and is only banning my bots from connecting. This is something very interesting. |
|
The starcraft update triggered so that people using bots to try to connect to sc would be tracked and once traced ip banned probably one of the 6 day bans. And all keys that were connected at the time are voided. |
|
If it's a permanent ip ban, I suspect pvpgn will get some new life. |
|
Some fish shit is going down. I loaded bots on a proxy. No starcraft clients were attempted. When I woke this morning they were disconnected. I figured the proxy died. So I changed proxy and turns out my key was voided. A perfectly working key last night was voided this morning. That was with out me connecting a sc client. I am going to do a bit of testing and see if this continues. Both of the bots keys I was using last night were in fact voided. Herm. It may or may not be safe to load any bots atm. I am slightly curious of what you guys think of this thread https://us.battle.net/forums/en/starcraft/topic/20754486138 its reguarding ssltls and tls connections. Idk if that effects bots or not but hey figured I would throw it out there. |
|
I haven't had any issues loading other bots. I am not sure how my other 2 keys got voided but it appears I can not duplicate the experiance |
|
Everyone who was signed in during a specific time frame had the same issue Sunday. No more SC. It is letting them track down people using bots so until we find a workaround. Stay the fuck away. |
|
alright cool thanks for the feed back. My bots are going offline till I hear more from you guys. |
|
W2BN D2DV D2XP and WAR3/W3XP are safe. As long as you don't try to load starcraft at all. The second you load starcraft bot or even try to, it's like your IP and any keys logged on with that IP are dead and Blizzard wants to make you feel pain. |
|
All public JBLS and BNLS see each have been notified and made aware if this and have quickly turned off 1.18 connects. |
|
any news on how long the "ip ban" lasts? I haven't tried to connect again after it happened, |
|
So far 3 days I'd expect 7 if you don't try to connect anything else from that IP. |
|
It lasted around 3 days for me. |
|
Just a heads up 1.18.2 has been released today. So for people who are working on it. That is now a thing. |
|
Yea we gave up for now. Blizzard keeps making changes to the connection protocol. Once we lock down the connection. Working on TLS. |
|
1.18.3 just dropped yesterday |
|
Yea Blizzard also announced a new special bot protocol, given the direction SC 1.18.x is taking, I don't expect bots to be working on it for a very very long time, especially given the crazy IP bans that happened after trying. |
|
Thats super encouraging..... |
|
All non-SC bots still currently work to the best of my knowledge. |
|
They are indeed still working for now |
|
and i just got bot banned for using non sc clients great... |
|
Yep there was just a bnet patch. And WAR3 update. |
|
1.18.4 released today I am more then likely going to work on a chat bot enviorment in vb.net for the new chat api they released |
|
That's pretty much everyone's plan. lol |
|
https://arcticworlds.net/spigot/download/sexy_layout.PNG - HAHAHA. It should work hopefully haha |
|
https://github.com/agentsix1/VB.NET-Classic-Bot-Early-Dev - If you guys are curious here is this |
1.18 was released to day. I have not launched the bot. How ever I do know you have been working a ton on the back end of stuff. All hashes for sc are outdate and am not sure you will be able to get them updated. How ever I would love to see you at least give it a shot
The text was updated successfully, but these errors were encountered: