StealthBot.net: Starcraft 1.18 - StealthBot.net

Jump to content

Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

Starcraft 1.18

#1 User is offline   catiski Icon

  • Newbie
  • Pip
  • Group: Members
  • Posts: 2
  • Joined: October-09 12

Posted April 19, 2017 - 02:23 PM

Stealthbot support 1.18?

#2 User is online   Pyro Icon

  • Militant Asshole
  • Icon
  • Group: Administrators
  • Posts: 615
  • Joined: July-31 09

Posted April 19, 2017 - 05:58 PM

Nope.
Pyro
StealthBot Developer
Chieftain of Clan BoT
Host of pyro.no-ip.biz

#3 User is offline   Zergboy Icon

  • Newbie
  • Pip
  • Group: Members
  • Posts: 2
  • Joined: April-19 17

Posted April 19, 2017 - 07:02 PM

Is 1.18 support planned in the future at all?

#4 User is online   Pyro Icon

  • Militant Asshole
  • Icon
  • Group: Administrators
  • Posts: 615
  • Joined: July-31 09

Posted April 20, 2017 - 02:51 AM

Not likely. A lot has changed on the back end.

This post has been edited by Pyro: April 23, 2017 - 03:50 AM
Reason for edit:: Nevermind. See post further down.

Pyro
StealthBot Developer
Chieftain of Clan BoT
Host of pyro.no-ip.biz

#5 User is offline   Zergboy Icon

  • Newbie
  • Pip
  • Group: Members
  • Posts: 2
  • Joined: April-19 17

Posted April 20, 2017 - 02:23 PM

That really sucks. Looks like it'll be a while before BW and SC bots make a come back then.

#6 User is offline   SugarD-x Icon

  • Around Since 2.4...
  • PipPipPip
  • Group: Beta Testers
  • Posts: 176
  • Joined: August-20 09

Posted April 21, 2017 - 10:04 PM

If popularity could build up support for them, I could see it being possible. Unfortunately until that happens, I doubt there will be enough motivation for the SB developers to continue. (Something I have feared for years). SB 3.0, anyone? :P

#7 User is online   Pyro Icon

  • Militant Asshole
  • Icon
  • Group: Administrators
  • Posts: 615
  • Joined: July-31 09

Posted April 23, 2017 - 03:49 AM

I've updated BNLS to support StarCraft 1.18. Use jbls.davnit.net or pyro.no-ip.biz (they are the same) as your BNLS server and you should be good to go.

This post has been edited by Pyro: April 23, 2017 - 09:24 PM
Reason for edit:: See below

Pyro
StealthBot Developer
Chieftain of Clan BoT
Host of pyro.no-ip.biz

#8 User is offline   SugarD-x Icon

  • Around Since 2.4...
  • PipPipPip
  • Group: Beta Testers
  • Posts: 176
  • Joined: August-20 09

Posted April 23, 2017 - 04:36 AM

Just to clarify, does this already account for the new 1.18.1 update that followed right after?

#9 User is online   Pyro Icon

  • Militant Asshole
  • Icon
  • Group: Administrators
  • Posts: 615
  • Joined: July-31 09

Posted April 23, 2017 - 10:27 AM

Yes, though if you use the game files from that update it will not work (reportedly). Only the files from 1.18 work.

This post has been edited by Pyro: April 23, 2017 - 09:25 PM
Reason for edit:: Further down

Pyro
StealthBot Developer
Chieftain of Clan BoT
Host of pyro.no-ip.biz

#10 User is offline   SugarD-x Icon

  • Around Since 2.4...
  • PipPipPip
  • Group: Beta Testers
  • Posts: 176
  • Joined: August-20 09

Posted April 23, 2017 - 05:36 PM

View PostPyro, on April 23, 2017 - 03:27 AM, said:

Yes, though if you use the game files from that update it will not work (reportedly). Only the files from 1.18 work.

That is really...odd. I'll see if I can test this out.

Edit: Seems you are correct. I can't connect with BNLS at all on that version:

 [10:45:05 AM] Connecting your bot...
 [10:45:05 AM] [BNLS] Connecting to the BNLS server at pyro.no-ip.biz...
 [10:45:05 AM] [BNLS] Connected!
 [10:45:05 AM] [BNLS] Authorized!
 [10:45:05 AM] [BNCS] Connecting to the Battle.net server at uswest.battle.net...
 [10:45:05 AM] [BNCS] Connected!
 [10:45:05 AM] [BNCS] Checking version...
 [10:45:06 AM] [BNCS] Version check failed! The version byte for this attempt was 0xD6. Extra Information: SEXP_IX86_1.18.0.1345.mpq
 [10:45:06 AM] [BNCS] BNLS has not been updated yet, or you experienced an error. Try connecting again.
 [10:45:06 AM] All connections closed.


I'll give hashing a try next.

Edit #2: I'm an idiot. Just updated the version byte. Apparently BNLS plays nice, but BNET doesn't. :P

Edit #3: Apparently hashing doesn't appear to be possible in its current form unless I'm missing something. Two of the files, (battle.snp and STAR.bin) don't exist in 1.18.1.

This post has been edited by SugarD-x: April 23, 2017 - 06:32 PM


#11 User is online   Pyro Icon

  • Militant Asshole
  • Icon
  • Group: Administrators
  • Posts: 615
  • Joined: July-31 09

Posted April 23, 2017 - 09:24 PM

You don't need either of them, like with D2. STAR.bin isn't used normally, and battle.snp can be set to "NULL" in your CheckRevision.ini.

Either way something changed since last night and its not working anymore. Trying to connect with StarCraft gets me version check failed and an IP ban. We'll have to see where this goes.
Pyro
StealthBot Developer
Chieftain of Clan BoT
Host of pyro.no-ip.biz

#12 User is offline   SugarD-x Icon

  • Around Since 2.4...
  • PipPipPip
  • Group: Beta Testers
  • Posts: 176
  • Joined: August-20 09

Posted April 23, 2017 - 09:42 PM

View PostPyro, on April 23, 2017 - 02:24 PM, said:

You don't need either of them, like with D2. STAR.bin isn't used normally, and battle.snp can be set to "NULL" in your CheckRevision.ini.

Either way something changed since last night and its not working anymore. Trying to connect with StarCraft gets me version check failed and an IP ban. We'll have to see where this goes.

Ah, roger.

Ya, I've been getting the same. First it was a version check failure, but after I updated the version bytes, (which I assumed were just for hashing only), it just started silently IP-banning me upon connection instead. I've yet to connect once since running a fresh bot install.

Seeing how SC/BW are now free, and the latest patch literally reinstalls the game, any chance the lack of a required CD-key could have any effect on the connection?

Edit: Not sure if this is related or not, but I received an odd error after trying to reconnect via a proxy:
 [02:46:28 PM] Error: The front of the buffer is not a valid packet!



Edit #2: Via hashing through the same proxy:
 [02:50:09 PM] [BNCS] The seed value string was malformed: A=0 [02:50:09 PM] [BNCS] Make sure you have the latest Warden.dll from http://www.stealthbot.net/sb/warden/
 [02:50:09 PM] [BNCS] Local Hashing Failed
 [02:50:09 PM] All connections closed.



(Needless to say, I do have the March 2016 version of Warden in the bot's folder already)

This post has been edited by SugarD-x: April 23, 2017 - 09:52 PM


#13 User is online   Pyro Icon

  • Militant Asshole
  • Icon
  • Group: Administrators
  • Posts: 615
  • Joined: July-31 09

Posted April 23, 2017 - 11:35 PM

Warden.dll without the latest beta commits doesn't support seed strings that you get when needing an update. You're probably using the wrong version byte. I would be wary about using the correct one though (it's D6). The IP ban also came with having all of the CD keys voided for any account I had connected.
Pyro
StealthBot Developer
Chieftain of Clan BoT
Host of pyro.no-ip.biz

#14 User is offline   l2k-Spec-Ops_X Icon

  • Newbie
  • Pip
  • Group: Members
  • Posts: 2
  • Joined: February-02 15

Posted April 24, 2017 - 12:22 AM

Quote

The IP ban also came with having all of the CD keys voided for any account I had connected.


Ouch!

Earlier today, I was able to use my D2 and War3 keys to connect. But mid-day they got disconnected and I'm unable to reconnect. Perhaps IP-ban has something to do with it. (Although, if memory serves me right, I tried connecting with SC Key only before connecting with D2 and War3... so either the IP-ban was latent in enforcement, or maybe I did try to connect another SC bot afterwards and just forgot.)

But I can still connect via full SC 1.18x client (non-bot).

This post has been edited by l2k-Spec-Ops_X: April 24, 2017 - 12:23 AM


#15 User is offline   l2k-Spec-Ops_X Icon

  • Newbie
  • Pip
  • Group: Members
  • Posts: 2
  • Joined: February-02 15

Posted April 25, 2017 - 02:00 AM

Update - the keys were voided. :(

#16 User is offline   SugarD-x Icon

  • Around Since 2.4...
  • PipPipPip
  • Group: Beta Testers
  • Posts: 176
  • Joined: August-20 09

Posted May 01, 2017 - 02:32 AM

Considering that the game is free now, it makes me wonder if the new version has an internal key built in, or if it uses some other method to authorize now, (if any). The new installer for the 1.18+ patches doesn't ask for a key when it reinstalls the entire game, unlike the past digital copies online. Keys may not be even necessary anymore on Battle.Net's end. If it sees the game as valid and has a key, it could be set to automatically ban it to prevent a connection since it shouldn't be using that authorization method. (This is just a guess, however). I could see Blizzard doing this to prevent bots and hacks from being used. I believe they set up a new anti-cheat system too, so this could be part of it to prevent unauthorized connections.

Edit: Also after my above attempts, my actual game still connects fine and is not IP-banned. It has even since updated to 1.18.2. I haven't tried logging in with the same username yet, but seeing how the connection never made it that far, I'm willing to bet that Battle.Net doesn't care about the accounts when it issues the bans.

This post has been edited by SugarD-x: May 01, 2017 - 02:35 AM


Page 1 of 1
  • You cannot start a new topic
  • You cannot reply to this topic

1 User(s) are reading this topic
0 members, 1 guests, 0 anonymous users