someone know a good bot for co?"

Yeah and that's why the majority is at cog, because chrome is a "professional" bot.

Clientless this, clientless that. To straighten out, we haven't had clientless for the last 1 YEAR, not 6 months etc etc, and that is our way of botting and works great. Have absolutely no plan on adding back clientless, completely pointless feature and haven't had a single complaint about cliented for those who actually tested/used it.

Exactly, chrome had in maybe 60-70% of the cases regarding larger anti bots the fastest fix. Note that had is the keyword here. Since we went the cliented route, 1 year ago, CoG has been up and running most of the time without any issues and WE are the ones who have been in 95% of the cases the fastest to be up and running again. We have barley been touched by any of the patches and even when TQ went personally out after us TON of times, it didn't take much to fix.

Almost ALL of our users go and run above 15 chars, without proxies. It's cheap and they aren't getting the kind of issues a chrome user would get if they try to bot without proxies.

Best wishes, Dean.

When I said that Chrome release a fixed faster then any other bot in 90% of the cases, I was in fact referring at those last 6 months. When CoG fixes cliented only, while Chrome releases a clientless fix too.

The majority is at CoG because egys like when they buts are kissed by your mods. Sorry, but brainless botters aren't tolerated at Chrome (so they are ignored, silenced from chat if they get noisy and don't show any intention to browse and read the guides posted on Chrome forum). And Chrome is proud with that.

Now explain your happy users which don't need proxies to bot why they're getting restrictions even when logging on a clean CO client, with CoG closed, after they used CoG for a few hours. Maybe because their IP and computers were tagged and saved in TQ database as botters, and they can't play CO at all now? Some of them (a lot of them) even reinstalled the complete OS + clean CO install and no change, they're still getting restrictions after 7-8 minutes online.

Quote:

Originally Posted by Trigorio Yeah and that's why the majority is at cog, because chrome is a "professional" bot.

You're a funny, funny man.

I do not count egy's and beggars as mattering so there goes 90 percent of your 'happy users' most of which I see complaining day and night about their restrictions.

They are getting restrictions because they used Chrome. Simple as that.
And thank you gabi for confirming the "professionalism" that exists over at the chrome community.

@pro4never, maybe egys and "beggars" wouldn't complain over at chrome over restrictions if the bot actually worked lol.

Quote:

Originally Posted by Trigorio @pro4never, maybe egys and "beggars" wouldn't complain over at chrome over restrictions if the bot actually worked lol.

According to your own definition of 'working', chrome is working perfectly ;)

If you want to make the claim that cliented is not necessary then you should apply that same standard to all bots then. Yes, chrome (and all clientless bots) have had some issues. Their cliented works perfectly right now and was fixed before CoG so yahhh double standards much?


I have zero interest in any of the paid bots (or conquer in general) but listening to you contradict yourself and rage at everyone is rather entertaining <3

Quote:

Originally Posted by pro4never Their cliented works perfectly right now and was fixed before CoG so yahhh double standards much?

I'd like to make a small note on this: cliented on Chrome wasn't fixed, it just kept running despite TQ updates. Cool, aint?

Quote:

Originally Posted by donn I'd like to make a small note on this: cliented on Chrome wasn't fixed, it just kept running despite TQ updates. Cool, aint?

Sorry, either way my point remains that it still has cliented functionality (which I, and their admins count as partial functionality) and yet he's trying to make the claim that it's completely down... when his own bot doesn't even pretend to offer clientless functionality.