You meant "He can't even release WB3 to public". We mods have pretty much stable version alredyQuote:
Originally Posted by hyderascripts
Printable View
You meant "He can't even release WB3 to public". We mods have pretty much stable version alredyQuote:
Originally Posted by hyderascripts
I love reading the denial in this thread. Everyone is so desperately is disbelief that they lie to themselves to calm themselves down. This update will be the end of bots for at least a few or more months. So be ready.
And i love reading people not knowing at all what they're talking about.Quote:
Originally Posted by Funkgary
It is going to be MONTHS before CIP kills of the old client and Tibia 11 will be out of full beta, and by that time we will be ready.
I'd say that, if they started using Tibia 11 today, WindBot wouldn't take more than a week to be updated. Of course, they will do many changes along these betas, but we'll always be there like we were on this first testing. We had access to it, and we probably will have access to it again until it's over.Quote:
Originally Posted by Funkgary
I believe Windbot will remain strong as it's always been.
TibiaCast and XenoBot surely can not afford this changes once they are too connected to the game client - they work like "parts" of the client.
Windbot has the advantage that all its structure seems to be totally out of it, which suggests the internal bot configurations will not need to be changed - the main challenge will be to know where to pick the informations the bot needs from - also known as "information addresses".
The release of Tibia 11 Beta is actually a start point for us to know how this new client works. Although Cipsoft is trying to finish the botting age, it is undeniable that this release is also helping us. As the Beta tests will run though the next few months and we already have its structure in hands, they are actually giving us time to find whatever we need to update our bot.
The total and sudden release of a whole new client without any previous information would be a huge problem, but we all know it is NOT the case.
Good luck to you guys!
Quote:
Originally Posted by RoxZin xD
If the new client is what darkstar said....
That statement whould be false do you guys remember when they swift a bit the client and NG (died),elfbot (died), and then we got neobot and w/e lordofwar pass for a bot.
Well this is going to be pretty much the same case, if the client is diferent everybot will have to do 1 of 2 things :
1.-Work together on a super fast under develop API
2.- Work on their own and obtain all the data that its changed in the client (build an api,lib,w/e)
if darkstar had access to the beta (i didn't see it yet.) and he knows the client changed this much they will have to re/do everything the reason for this is that you can be sure that player.() still exist but then you are not 100% sure that is the way to handle the data, so you have to decode and reverse engine op codes chunks and everything else.
darkstar said something like everybot will die or so, because they will stop working at the very moment the client surface.
This is normal it doesn't ment that the developers will retire or stop working, but im sure some will stop.
programing and reverse engine are not the same task.
////////////////////////////////////////////////////////////////////////////////////
this is pretty much how the bot works
tibia has something named player health thats stored in A40 that its a pointer (the stored number changes) so what you need to do is figure out the pointer and add it to the address and the base adress of tibia
so lets say that the base address right now its 20 the way to obtain that address right now it will be A20+Tibia.exe(20) it will result in A40 (don't do the math i didnt)
now lets say that the aslr and the base address change just this 2 changes may take at least a day 12 hrs of searching address and testing (this 2 addresses are what the bot uses to make it universal it disables your aslr so everyone has the same base address)
this is an example of what im talking about
http://tpforums.org/forum/threads/57...ult)-by-Wesker
Anyways if the client changes expect free respawns for at least a month if they work alone, unlesssssssssssssssssssssssssssssssssssssssssssss somehow ekx helps lucas to obtain them then you can look at a miracle
I think they are gonna release this client maybe next year with tibia 20th aniversary.
Yeah but DarkStar made that announcement before the client was released, I'm saying this now after Lucas worked on it until they shut access to the beta. I bet that if he worked the same amount of time and gathered the same info, he'd be able to update his bot in less than a week as well.Quote:
Originally Posted by Wesker
Okey so xenobot and ggbot and tibiacast is going to shutdown when they implement the new tibia client.
Windbot will still be here obvious as the admin said so, good move (ecomomically wise) :)
Though i wonder what anti-bot measures they have implemented... guess the work will be quite hard.
If there is money there is a way
Quote:
Originally Posted by victorfts
Wise words.
I know 1 thing for sure;
Whoever succeed on building the FIRST bot (not simpler ones like heal only) after the Tibia 11 is released will gain the whole bot market, im sure of that.
Windbot will be done even before Tibia 11 gets released ;)Quote:
Originally Posted by downloadkct
[emrhh]windbot 3.0[/emrhh]Quote:
Originally Posted by SuNe
LoL thats what i like to hear hahaQuote:
Originally Posted by SuNe
now the time has come, lets see
Tibia 10.9* is not dead yet. So there is still time.Quote:
Originally Posted by ikeramos
To be honest, They should stop our premium time in 3 days, becouse for example I got 25 days of licency, and I dont wanna lose it when Lucas wll update bot.I know he need time, but They should stop our premium time in few days.
Why would we pause your time when bot will be updated for 10.98 in a few hours?Quote:
Originally Posted by Jantary
why salty mode now and not in few hours xD?!Quote:
Originally Posted by SuNe
Why would I not ban you now and not in a few hours?!Quote:
Originally Posted by Akiller
Why would u like to upset so many people?!Quote:
Originally Posted by SuNe
Sune, so new bot update will be 2.8.6? Am i right?
https://forums.tibiawindbot.com/show...222#post438222Quote:
Originally Posted by marcosia
Guys I thought that it takes like week or 2 weeks or even month. If this only take few our then its okey. Sorry I just take it wrong and understude this so badly :)
Will the scripts for version 10 work on the 11 client?
Yes.Quote:
Originally Posted by hejje
But it's not Tibia 11 yet, the bot is for 10.98 for now.
Not true. If the bot was programmed correctly most code will be reusable. They will only have to update parts that changed like memory addresses, input, etc.Quote:
Originally Posted by hamiltonx
Do you know if new Tibia 11 client uses the same tibia protocol as before? As far as I know it does. And if so then what's the point of reversing new client from scratch if you can use already reversed tibia protocol to make clientless bots? I think it's 100% possible, am I right? I saw someone connected to OTS using Tibia 11 client so it means that Tibia 11 client still uses the same protocol and therefore you can just simply send packets onto real tibia server to simulate that you are moving/attacking or doing whatever you want.
Yes, but that would also be very easy to find out and delete you for it, the way they banned the people who used elfbot and blackD and other packet based bots..Quote:
Originally Posted by PsychoBoy
There's nothing inherent about packet based bots that make them detectable, at least not compared to mouse/keyboard simulating ones. They're likely harder to implement correctly though.
The problem with packet based bots, is that CIP can change the packet when they feel like it, and having a heyday banning/deleting everyone who uses such, Just as they did when they banned people using blackDproxy and Elfbot when they started with their auto detection toolQuote:
Originally Posted by shAdOwArt
They can only change the client to server packets at client updates. Analyzing the new client for changes in what packets it creates is something you have to do regardless of how you implement your bot as you have to make sure there's no new client sided detection included in the new update. There's some more room to play with when it comes to the server to client packets, as we saw a few weeks ago when all bots lost their ability to loot, but they're still limited to sending packets that the current client is able to comprehend.Quote:
Originally Posted by SuNe
And that is how they banned the people using Elf/blackD.. They sent a "special" packet from the server to the client, and the bots answered the old, but still working packet,that a non bot client did not, and bam banned..Quote:
Originally Posted by shAdOwArt
Anyways, the looting problem had nothing to do with that really, they just changed so that monsters did not stay on the battle list with 0% hp for half a sec like they did before (which the bots used to add the monster as dead and to the loot list), but got removed right away when they died.
Which just means that the creators did a poor job in analyzing the update.Quote:
Originally Posted by SuNe
Maybe they changed that too, but they did change the order of the loot message, and the new corpse packets too (that's what messed with Xeno).Quote:
Anyways, the looting problem had nothing to do with that really, they just changed so that monsters did not stay on the battle list with 0% hp for half a sec like they did before (which the bots used to add the monster as dead and to the loot list), but got removed right away when they died.
It is easy to miss something that is only activated if they recived the special packet, and if they only got the normal packets, it just sent the same was the bot did.Quote:
Originally Posted by shAdOwArt
Tibia havent really been deeply RE since long ago, and non of the bot creators do that for every single update..
Else all of them would have catched that ever since Flash client got released you have been able to iterat your entier backpack without having any BPs open..
So it is easy to miss stuff you're not looking for.
It does not. And it does. It's hard to answer this without understanding exactly what you mean by protocol. The new client adds some network layers such as ProtoBuff which makes it harder to reverse engineer the packet data, but once we've got all the information on it we can store it in a really nice format and use it in some very clever ways. Sadly, though, there are a lot of other changes. They have made more changes just to accommodate what the new client is capable of, so the old client gets different packets from the new one and vice versa.Quote:
Originally Posted by PsychoBoy
Further to the above, though, it is indeed possible to make a clientless bot, and at one time BlackD used to have a clientless option. It was incredibly lightweight and comparatively easy to use, but it did lack some functionality (although BlackD was one of the first bots to have "real" capabilities to refill and stuff since other developers didn't want to use packets). To make a clientless bot today, however would not be as easy as it was back then due to the extra stuff that's been added.
Personally, I believe there is actually something that makes them fundamentally more detectable. The primary goal in bot detection (the way CIP is doing it) is to find a pattern and understand it. An example would be that a script which walks the exact same path every time will get you banned much more quickly in like-for-like environments as a script which uses entirely random paths every time (pseudorandom, at least, as random could result in the same output).Quote:
Originally Posted by shAdOwArt
Further to things like walking paths, there are timings. If your latency is fixed (which it tends to be, in spite of what the HUDs tell you, it doesn't vary nearly that much - see jitter on pingtest.net for more information), and your computer is powerful, you'll find that as soon as the health lost packet arrives, you are shipping out a spell cast packet. The result? 0ms reaction times. Now, it's not possible just from one heal to work out that someone is using a bot, but when it's taking <100ms to send a packet to a client, have a user see the impact of that packet in their client, react to it, then to recognise the key event for the heal, generate a new packet and send it back to the server, and that's happening every time a player takes damage, it's pretty obvious that person is not genuine.
With software such as WindBot, the bot has to go through those extra layers which add time and randomisation to everything. In my opinion, that makes it inherently more risky to create a proxy based bot, since you must account for that delay each time you perform an action. I won't deny that botting with packets can be just as safe as with keyboard and mouse simulation, since obviously you can manually reproduce that delay and everything else that would need randomising, but by its very nature, a proxy bot will be harder to randomise than a simulation bot.
Finally, sorry for the essay, but just to say that it's not only timings such as healing which are effected in this way. I believe when you pathfind in the client (e.g click the minimap), a packet is generated and sent to the server each time you "reach a tile". If you're manually trying to reproduce this it could be very tricky to get the timing right. I might be wrong on this, been a long time since I looked, but if I'm right (I usually am ;)) then this could be more reason not to go with proxy bots. There are other examples, though, too. Attack spells, targeting creatures off screen, casting runes at creatures off screen, etc.
To add to that a bit, the new client now updates somewhat secretively on launch, if you didn't notice an update, they could easily enough ship it out and catch thousands of botters all at once. They could play havoc with proxy based bots if they really wanted to, just by changing their encryption method slightly.Quote:
Originally Posted by SuNe
Oh, I also think more people got banned by not saying exiva pause than by having some secret packet sent lol
Meu Windbot não concecta, esta sempre desconectado, tem alguma solução??? estou falando desse wind beta test
Quote:
Originally Posted by crisdias
da CTRL+G no personagem, ai vai conectar com o bot. Caso isso nao funcionar, fecha tudo, loga no char abre o bot, e reloga no char.