ok. tried everything correctly, but when i try to log in, it says "Failed to log in: Unknown Error."
yes i entered the pass and account correctly and it is not banned
...Bone-you...listen to me i will say what i do and say what is wrong,
reinstall co2 to patch 4354-4356 with (crack client) and extract xproxy in co2 file
and make some change in sever.dat and xproxy.cfg sever.dat
Server1=Mercury
Ip1=69.59.142.13
Port1=9958
ServerName1=Mercury
HintWord1=
Pic1=servericon21
and open xproxy then open co2 ,chose Mercury,write id and pass and press enter
is that right?
when i press enter it said faild login:unknown error.
what u think i do then ?...
and i'm going to crazy coz alot of ppl log in old patch and me not..plz help me..
lol i am in the same server as u do! and i did it as instruction bone-you gave, too. but i am having the same problem as u do. "Failed to login: Unknow error."
props, but im wondering considering its using older versions and bots, etc. theres probably a slight increase in chance of setting off botjail, perhaps not much but its slightly incnreased?
as for the proxy...****, simple but lethal
Well yea. Using anything other than the official client has its risks.
sorry, i meant, considering ur usingn older patches it could pose some bug issues not yet found by u leading to a possible greater chance of bot jailing if used with older clients then comparable with bot jail chances with other hacks in general? or am i incorrect? nice program either way, very nice
sorry, i meant, considering ur usingn older patches it could pose some bug issues not yet found by u leading to a possible greater chance of bot jailing if used with older clients then comparable with bot jail chances with other hacks in general? or am i incorrect? nice program either way, very nice
Yea. There's a chance that could happen but as far as I know TQ has not botjailed for sending an outdated packet :P unless it was specific to the bot check packet.
Yea. There's a chance that could happen but as far as I know TQ has not botjailed for sending an outdated packet :P unless it was specific to the bot check packet.
mind elaborating a bit on the bot check packet? ^^
lol i am in the same server as u do! and i did it as instruction bone-you gave, too. but i am having the same problem as u do. "Failed to login: Unknow error."
216.93.164.137 <--put this number on your ip1 and server adress
----------------------------------------------------------------------
AHHH FINALY it works, thx..bone-you!!
Xproxy 4354 running with SV 03/17/2008 - CO2 Guides & Templates - 52 Replies I dont know if i will be banned with this guide, but imma take my chances to help others so as what bone-you did to me in helping to run my 4354 client.
1st. Copy and paste this conquer.exe attached to your 4354 CO folder. (Dont worry, that conquer.exe came from this very website a long time ago.)
2nd. Get bone-you's xproxy running.
3rd. Run your SV as you usually do it.
4rth. Voila! happy Boting!
Thanks to bone-you for providing the utmost help to us with the xproxy he...
AllPurpose Skill Caster + XProxy 01/11/2008 - CO2 Exploits, Hacks & Tools - 0 Replies hello,
This works just like the autostig module that bone-you made for us, When the player jumps it casts the set spell. I added the function "setskill x". you type that in team chat.
In order to find out the skill number:cast the skill while using the proxy and a message will be shown and the skill number can be seen.
forexample: if you wanted to cast magicshield, you would type "setskill 1090" in team chat and then use "add playername" to add people to the targetlist. This would...
XProxy 09/20/2007 - Conquer Online 2 - 5 Replies This is not a release (yet) it is simply to see how many people would try it out or dev for it. First I shall beg for forgiveness for not releasing it sooner like I said I would (crazytao sucked me in). Second, a rundown of what it is.
Not many people used my XProxy due to its lack of "hack" features in it such as speeding and autohunt/loot shit. Then I came up with an idea of a public dev of a proxy that the community could work on. It's pretty much been functional minus the latest patches...