[CHROME] The EPIC Proxy/Bot - (Multiclient & Client Manager FREE!!)

03/29/2013 11:59 ZaXpired#1741
Ok i did it all .. now bot active ... but telling me " Welcome *** click to subscribe !!!
so its free one or payment one ...
When i try to Start Connecting it keeps telling me wait 5 secs. and no connect.
Thanks in advance.
03/29/2013 12:46 Captivate#1742
Quote:
Originally Posted by ZaXpired View Post
Ok i did it all .. now bot active ... but telling me " Welcome *** click to subscribe !!!
so its free one or payment one ...
When i try to Start Connecting it keeps telling me wait 5 secs. and no connect.
Thanks in advance.
It's pay-to-use
03/29/2013 13:08 ZaXpired#1743
Quote:
(Multiclient & Client Manager FREE!!)
Topic title <<
confused (:
03/29/2013 13:38 ocio19#1744
Quote:
Originally Posted by Captivate View Post
It's pay-to-use
Can u make it a 30 minutes free-use on day or smth like that? I want to buy a bot, but i want to test it before buying..
03/29/2013 14:06 Captivate#1745
Quote:
Originally Posted by ocio19 View Post
Can u make it a 30 minutes free-use on day or smth like that? I want to buy a bot, but i want to test it before buying..
We had that for a while, but we removed it due abusing faggots. We make no exceptions any longer, if you don't trust it then that's too bad unfortunately.
03/29/2013 16:14 Giggle`#1746
restrictions back ..
03/29/2013 16:24 Captivate#1747
Quote:
Originally Posted by Giggle` View Post
restrictions back ..
Use our forum for support.

Edit: After analyzing the data of my restricted accounts (3 out of 120) I've come to the conclusion that TQ fucked something up most likely. We'll see how things go, for the time being please enable your individual logs via the 'Tools -> Configuration' tab.

Edit2: Yup it was a TQ-fuckup. Try relaunching your accounts and you'll see that they're no longer restricted.
03/29/2013 19:34 simeman#1748
Hi!

Im an old Chrome user that decided to start play CO again but im unable to see the chat and i get a constant AUTH OK message in the log. Any help would be appreciated.

Regards jolleman
03/29/2013 21:07 Captivate#1749
Quote:
Originally Posted by simeman View Post
Hi!

Im an old Chrome user that decided to start play CO again but im unable to see the chat and i get a constant AUTH OK message in the log. Any help would be appreciated.

Regards jolleman
Have you got an active subscription?
03/29/2013 21:08 donn#1750
Quote:
Originally Posted by simeman View Post
Hi!

Im an old Chrome user that decided to start play CO again but im unable to see the chat and i get a constant AUTH OK message in the log. Any help would be appreciated.

Regards jolleman
You need to buy a sub to use it.
03/30/2013 05:39 Geraman#1751
does this work on private servers? and wat patch would this work on?
03/30/2013 07:21 donn#1752
Quote:
Originally Posted by Geraman View Post
does this work on private servers? and wat patch would this work on?
Only official Conquer.
03/30/2013 09:27 waltergwaps#1753
i have a question in this step:

Step 3:
Place the CHROME Installer that you downloaded in Step 1 in this folder and run it as administrator. Select the Conquer Path (Usually in C:\Program Files (x86)\NetDragon\Conquer Online 2.0) and install CHROME.


since my conquer online and chrome will be somehow connected... will there be a chance of getting banned to my characters who i usually log-in in that conquer? even if i haven't used chrome yet?
03/30/2013 13:32 xx6886_6886xx#1754
acc bot restrict again. I do that(Edit2: Yup it was a TQ-fuckup. Try relaunching your accounts and you'll see that they're no longer restricted.) but i still see acc restric and now. my chrome not connected server ( unable to connect to the update server 29833)
03/30/2013 14:45 Captivate#1755
Quote:
Originally Posted by xx6886_6886xx View Post
acc bot restrict again. I do that(Edit2: Yup it was a TQ-fuckup. Try relaunching your accounts and you'll see that they're no longer restricted.) but i still see acc restric and now. my chrome not connected server ( unable to connect to the update server 29833)
That was yesterday, TQ was probably testing their new anti-bot that day. We're currently working on the issue.