Any Diablo II Xpac Pub Clientless INGAME Bots Out Yet?

[BenOwns]

just wondering if anyone knew of any pub ones or non pub ones that are out?

[Soul Taker]

just wondering if anyone knew of any pub ones or non pub ones that are out?

What's this got to do with bot development?

[iago]

Clientless? I think we went over this with somebody else: a bot IS a client, how can it possibly be clientless?

[Soul Taker]

Clientless? I think we went over this with somebody else: a bot IS a client, how can it possibly be clientless?

Telepathy based bots!  Though, I guess your brain could be considered the client there.   Hm... but with the odds of people asking this stuff having brains.....

[OnlyMeat]

just wondering if anyone knew of any pub ones or non pub ones that are out?

I have written a so called clientless bot ( by this hes referring to terminology used by d2 client hackers which basically means a game client other than the real d2 ).

It is not public yet but i maybe releasing soon ( well a few months ) as i still have some issues to cleanup.

This release will not be source code only binaries, also to note my 'client' uses proxy support so R/D's are no longer a problem and no need to do multi xp runs (which actually just slow you down ).

[iago]

I guess I'll post my warning here again -- Diablo 2 as of 1.10 has hidden anti-bot stuff that they have yet to use.  Whether they will ever use it is a mystery, but checksums and such DO exist in the game's code.  I haven't seen it myself, but I was told by a very trusted friend some time ago.

[OnlyMeat]

I guess I'll post my warning here again -- Diablo 2 as of 1.10 has hidden anti-bot stuff that they have yet to use.  Whether they will ever use it is a mystery, but checksums and such DO exist in the game's code.  I haven't seen it myself, but I was told by a very trusted friend some time ago.

That may well be true for the real client's internal memory checks and such ( anti-hacking  i.e extrawork.dll ) but  i have seen no such activity with regards to server packets directly.

This may of course be that i just have not seen it but iv been working with d2 for quite a while and have not seen anything remotely like you mentioned would you care to elaborate on the details of these anti-botting checks?

[dxoigmn]

That may well be true for the real client's internal memory checks and such ( anti-hacking  i.e extrawork.dll )

Does anyone have any actual proof that ExtraWork.dll can be used to detect hacks within Diablo II?  I would like to see a dll capable of that, as I haven't seen any personally.

[OnlyMeat]

That may well be true for the real client's internal memory checks and such ( anti-hacking  i.e extrawork.dll )

Does anyone have any actual proof that ExtraWork.dll can be used to detect hacks within Diablo II?  I would like to see a dll capable of that, as I haven't seen any personally.

As far as i can tell the d2 client is able to update this dll dynamically so it may not as yet check for any specific hacking but they are able to add ( or download ) a new version of that dll at anytime which means they can start doing hacking checks at anytime that suits them, of course this only applies to bots that use the actual d2 client which is not what we are discussing here, we are talking about an alternative client that supports d2 games.

But to answer your question no it currently does'nt look for hacks by the looks of the assembly, but it can change without a patch coming out so in the future yes it could very well do so <insert warning to botters using hacks> :p

[Kp]

As far as i can tell the d2 client is able to update this dll dynamically so it may not as yet check for any specific hacking but they are able to add ( or download ) a new version of that dll at anytime which means they can start doing hacking checks at anytime that suits them, of course this only applies to bots that use the actual d2 client which is not what we are discussing here, we are talking about an alternative client that supports d2 games.
But to answer your question no it currently does'nt look for hacks by the looks of the assembly, but it can change without a patch coming out so in the future yes it could very well do so <insert warning to botters using hacks> :p

On what do you base the belief that robots are safe from this DLL?  It would be trivially easy to set the banning rules to be that "if the response is missing or wrong, then ban."  Bots would ignore the message and get banned.  Cheaters would process the message, get the checksum wrong, and get banned.  Only true clients could pass the check.

[OnlyMeat]

As far as i can tell the d2 client is able to update this dll dynamically so it may not as yet check for any specific hacking but they are able to add ( or download ) a new version of that dll at anytime which means they can start doing hacking checks at anytime that suits them, of course this only applies to bots that use the actual d2 client which is not what we are discussing here, we are talking about an alternative client that supports d2 games.
But to answer your question no it currently does'nt look for hacks by the looks of the assembly, but it can change without a patch coming out so in the future yes it could very well do so <insert warning to botters using hacks> :p

On what do you base the belief that robots are safe from this DLL?  It would be trivially easy to set the banning rules to be that "if the response is missing or wrong, then ban."  Bots would ignore the message and get banned.  Cheaters would process the message, get the checksum wrong, and get banned.  Only true clients could pass the check.

I cant say for certain, i dont think anyone can in truth but i  do believe in my personal opinion  that extrawork.dll is designed to check the memory space of the real client, otherwise they would just simply send another kinda of authentication challenge packet if they intended it to check for clients other than d2 ( which they still might do ) but as of yet i have not seen any packet based challenge.

This appears to be a pure client side memory integrity check, also the fact that 99% of botting is performed by client side hacks could be the driving force behind this.

I have yet to see any public 'clientless' bots which are active so i can only assume they are trying to rid the realms of these elements first, this is a purely logical assumption which you may disagree with but everyone is entitled to their own opinion and thats mine

[BenOwns]

as he said yes.
for diablo II clientless INGAME bot.
Meaning a bot that does not use the diablo II game ( client ) is able to enter games make actions and so forth.

[Sorc.Polgara]

these kind of programs and all that botting shit is what makes people quit D2.

Ruins the trading economy, ruins the fun, ruins the online experience, period.

bleh.

[BaDDBLooD]

these kind of programs and all that botting shit is what makes people quit D2.

Ruins the trading economy, ruins the fun, ruins the online experience, period.

bleh.

Not to mention it inspires people to create better and better programs, making it harder and harder for blizzard to patch each generation of Diablo2 Game Bots.

[Zakath]

As far as i can tell the d2 client is able to update this dll dynamically so it may not as yet check for any specific hacking but they are able to add ( or download ) a new version of that dll at anytime which means they can start doing hacking checks at anytime that suits them, of course this only applies to bots that use the actual d2 client which is not what we are discussing here, we are talking about an alternative client that supports d2 games.
But to answer your question no it currently does'nt look for hacks by the looks of the assembly, but it can change without a patch coming out so in the future yes it could very well do so <insert warning to botters using hacks> :p

On what do you base the belief that robots are safe from this DLL?  It would be trivially easy to set the banning rules to be that "if the response is missing or wrong, then ban."  Bots would ignore the message and get banned.  Cheaters would process the message, get the checksum wrong, and get banned.  Only true clients could pass the check.

I cant say for certain, i dont think anyone can in truth but i  do believe in my personal opinion  that extrawork.dll is designed to check the memory space of the real client, otherwise they would just simply send another kinda of authentication challenge packet if they intended it to check for clients other than d2 ( which they still might do ) but as of yet i have not seen any packet based challenge.

This appears to be a pure client side memory integrity check, also the fact that 99% of botting is performed by client side hacks could be the driving force behind this.

I have yet to see any public 'clientless' bots which are active so i can only assume they are trying to rid the realms of these elements first, this is a purely logical assumption which you may disagree with but everyone is entitled to their own opinion and thats mine

*Groan*

Are people STILL not aware of the purpose of IX86ExtraWork.dll?! Skywing analyzed it in detail, and iirc even provided a utility to see what it was doing. ExtraWork carries the functions that are called to "send your system information to Blizzard" (i.e., processor type and speed, video ram, etc...). It is not, and never has been, an anti-hacking measure. Now, you can certainly say that it could be in the future, but that's absurd logic. By the same token, I could say that in the future Blizzard might modify CheckRevision to start randomly IP-banning people whose computer network name starts with the letter 'P.'