Any way to fix BJX?

u guys think we could fix bjx from sending us to jail? let us brain storm on maybe how to stop this whole jail thing....


ideas?

I dont think so. ;(

I've never used BJX so don't flame me if I'm wrong but I assume that they see when you move in the same coordinates over and over again.
so my solution woul be to make the coords random or make the bot a lot long and complicated.

or as the example shown on my pictre
same could be done with any other coordinates

Does anyone know how the BJX bot is actually getting caught? It was rumored in another thread that it couldnt respond to the f2 03 type bc packet. Did this every get remedied or does it just log when it sees one?

Quote:

Originally posted by t3hn00bz0r@Oct 10 2005, 08:22 Does anyone know how the BJX bot is actually getting caught? It was rumored in another thread that it couldnt respond to the f2 03 type bc packet. Did this every get remedied or does it just log when it sees one?

ill look into the bjx packets to see if they respond correctly to the packets

after that ill report to you guys

Whats this thread about?

Changing BJX co,ords to avoid getting caught?

Quote:

Originally posted by ultimatedestroyer@Oct 10 2005, 12:30 Whats this thread about? Changing BJX co,ords to avoid getting caught?

doing anything to avoid getting caught lol :p

well i had a script were i didnt get caught up until the 15th hour of using it but dont use ti anymore because i dont want my tao in jail forever. and i tried with my archer but it got jailed like after a few jumps and it happened twice. and i'll never try it with my main so i need another tao which i dont feel like plvling it. but if you guys wants the script, here it is:

[begin]
returntotown,ApeMountain
moveto,538,531
moveto,562,534
moveto,563,540
moveto,561,542
moveto,556,543
moveto,565,545
moveto,572,546
autostore
moveto,580,543
moveto,579,546
moveto,575,545
moveto,570,545
moveto,564,544
moveto,557,544
moveto,554,548
autosell
autobuy
moveto,799,687
moveto,610,874
passvortex
moveto,312,372
radius,100
fight

Quote:

Originally posted by anticlownn+Oct 10 2005, 15:05--></span><table border='0' align='center' width='95%' cellpadding='3' cellspacing='1'><tr><td>QUOTE (anticlownn @ Oct 10 2005, 15:05)</td></tr><tr><td id='QUOTE'> <!--QuoteBegin--ultimatedestroyer@Oct 10 2005, 12:30 Whats this thread about? Changing BJX co,ords to avoid getting caught?

doing anything to avoid getting caught lol :p [/b][/quote]
correct... lol


P.S an ultima thx for helpin.... if u catch anything unusual, lets us know, maybe we could get a side program to respond to those packets or inject somethin into bjx so we wont get caught... lol this bot is so usefull, we cant let it go to waste

chaging coords did not work. i wrote a small program in C that makes the scripts for bjx. that program works in the background and can map any valid coordinate in the map using a random function, however the chars still got caught, so its not a problem about coords.
and i think it will be HARD to fix that bot without the source, maybe some1 with more time and knowledge than me can fix it, but i doubt it.

salu2

well, all the work for a stand-alone client is done.... an its rite there in front of us... would be a waste to let it just die like this..... but if we could be able to get the source code.... but then again how would we do that?

*BUMP*

Could write a packet sniffer that watches for the packet bjx cant respond to, and responds to it. Not that hard if I knew :

1- What packet it cant respond to.
2- What It needs to respond WITH.

i hope we can fix it.... this bot is very usefull!!!

I logged onto a newbie character recently and let him run for about two hours, and afterwards I got arrested twice in a row (about 10 minutes apart). Here's the funny part: I was standing completely still and not running any scripts at all.

I was simultaneously logging packets using COPAC on another character (using normal client). I picked up no strange packets being sent whatsoever. No special "arrest" packets - nothing.

I've noticed F2 03 packets being sent every once in a while, but somehow the bot can respond to them normally, so I'm not sure that those are the problem.

I was arrested around 11:10am MST.

My theory: It's very easy to spot the bot because of how it sends the packets, but you will not get arrested unless a GM is on to confirm your arrest. With this way, they can thwart smart programmers from figuring out how the server arrests people.

Hopefully I'm wrong though... it would be much easier for us if it were really a special "arrest" packet or perhaps just the bot sometimes messing up the F2 03 packet.