Does JSTR use 0x1E?

[DeCeP7ioN]

I know you can use 0x1E to login with JSTR, but does the actual client even use 0x1E?

Does anyone have packetlogs from the actual JSTR client?

[GoSuGaMING]

jstr can use 1e or 0x50...

[Lenny]

The actual JSTR client uses 0x1E login.

[DeCeP7ioN]

You cannot login with 0x50 on JSTR.

Also, the packets below work to login with JSTR.

Code Select Expand


[09:17:48 PM] SND &H5
[09:17:48 PM] SND &H12
[09:17:48 PM] SND &H6
[09:17:48 PM] RCV &H5
[09:17:48 PM] RCV &H28
[09:17:48 PM] RCV &H25
[09:17:48 PM] SND &H25
[09:17:48 PM] RCV &H6
[09:17:48 PM] SND &H7
[09:17:48 PM] RCV &H7
[09:17:48 PM] SND &H30
[09:17:48 PM] RCV &H30
[09:17:48 PM] SND &H14
[09:17:48 PM] SND &H29
[09:17:48 PM] RCV &H29
[09:17:48 PM] SND &HA
[09:17:48 PM] SND &HC
[09:17:48 PM] RCV &HA


So how does this work then?

[Dyndrilliac]

Please use search.

http://forum.valhallalegends.com/phpbbs/index.php?board=17;action=display;threadid=6248

[NetNX]

using 0x1E is more practical unless you want to say to battle.net "Im a on a bot will you plz ban me???"

[GoSuGaMING]

using 0x1E is more practical unless you want to say to battle.net "Im a on a bot will you plz ban me???"

Goodjob reviving old posts... Battle.Net does not restrict third party programs... they dont support it... they dont ban accounts because your logged in a bot (unless ur abusing)

[NetNX]

Well lets just say one day they decide... "You know what lets ban all those bot using fuckers..." then what? you used 0x50 instead of 0x1E and wam arent you fucked... just because u didnt go with the easyier protocol

[GoSuGaMING]

Well lets just say one day they decide... "You know what lets ban all those bot using fuckers..." then what? you used 0x50 instead of 0x1E and wam arent you fucked... just because u didnt go with the easyier protocol

eh? you think to much... who cares :X

[Eric]

You can use 0x50 instead of 0x1E, but you won't be able to follow any traditional login sequence because JSTR's CD-Key is sent as-is to Battle.net in it's own packet.

[UserLoser.]

Code Select Expand


.text:19013FF0                 mov     cl, 1Eh         ; SID_CLIENTID2
.text:19013FF2                 add     eax, 14h
.text:19013FF5                 push    eax
.text:19013FF6                 call    SendPacket


Yes

[Dyndrilliac]

Well lets just say one day they decide... "You know what lets ban all those bot using fuckers..." then what? you used 0x50 instead of 0x1E and wam arent you fucked... just because u didnt go with the easyier protocol

That's stupid.

Using a different login sequence shouldn't matter as long as it is valid. I don't think 1) they would waste their time for setting up monitors to check for JSTR Users logging in with 0x50 instead of 0x1E, and 2) There would be no real point to banning all users logging in with 0x50 while the clients use 0x1E. Especially since most if not all of those clients are either no longer sold in most retail stores or very cheap - thus not only possibly losing future customers but also having no real way to get more money from those that they ban.

The entire point of banning is to make the gaming environment for their most popular games more enjoyable while enticing the people banned to buy new products for the keys, so they can play again, restarting the whole cycle.

[dxoigmn]

That's stupid.

Using a different login sequence shouldn't matter as long as it is valid. I don't think 1) they would waste their time for setting up monitors to check for JSTR Users logging in with 0x50 instead of 0x1E, and 2) There would be no real point to banning all users logging in with 0x50 while the clients use 0x1E. Especially since most if not all of those clients are either no longer sold in most retail stores or very cheap - thus not only possibly losing future customers but also having no real way to get more money from those that they ban.

The entire point of banning is to make the gaming environment for their most popular games more enjoyable while enticing the people banned to buy new products for the keys, so they can play again, restarting the whole cycle.

Is the restriction with JSTR only allowing authentication via SID_CDKEY still in effect?  That is a form of what you're describing and Battle.net had (has?) some checks like that IIRC.  Yes it is nice to allow all clients to logon via whatever way they want (e.g. using the legacy protocol or using the newer protocol), however this method is proprietary and Blizzard can do whatever it wants with Battle.net in regards to restricting clients that are emulations.