COPAC - Conquer Online Packet Logger / Editor

hope its got fixed soon cuz we didnt have a good packet logger/sender !!

Does n e 1 know timescales for a fix or an alternative that works?

Quote:

Originally posted by chocoman4k@Jul 2 2005, 12:03 - It only modifies 5 bytes in the client, makes it easy to update when new patches come out.

...

think hes not caring about this

Quote:

Originally posted by MegaXz@May 30 2006, 07:06 I dont get what this do I read the posts on the first page :/

It allows u to listen to information send between Conquer program and the server, u can also record it and send other information.

Alone it does nothing, its a tool to possibly make exploits, requires some hex knoledge and a sharp creative mind to guess what to do with it.

could u make a hack so the server thinks u just drank an xp pot? so u will get more exp?

Quote:

Originally posted by Snipper@Jun 29 2006, 06:22 could u make a hack so the server thinks u just drank an xp pot? so u will get more exp?

GTFO

??? 0.o

4 me it worked after i had expeirmented a bit with my editor.......+k

my clients shut down too

guys i just want to say you guys are genoius even tho i can already hack and i've made hacks of my own off packet editor this could easily turn into something big like a simple program that devises all the packets into a file and it all does it at a push of a button... hopefully it will never come to that

good lord this is great... K+

COPACldr.exe, wut directory is it locatd in?

I get a error message, Couldn't hook the SendMsh()/ReceveMsg() procedure

I think one objective to while using this program would be to find any client side decisions that are made. Most likely there probably arent any because they are probably smarter then that but everyone makes a mistake here and there.

One thing I was thinking about that was brought up in this thread was mining. Someone said they tried to send mineing packets faster then allowed and it shut down conquer. Now the question is, why did conquer shutdown and what made the decision to do that. Its very likely that the server said, "Hey, this character is sending mining commands quicker than I allow him to!" and then sends a packet that tells your client to shutdown.

This is the most likely possibility but what if it wasnt. What if it was actually our client telling us that we can only send the mining packet at a set interval. If there were some way to prove this theory then someone could possibly hex edit one of the files where the decision is made to not send another mining packet until that time interval is up.

Just something that I would throw out there for you guys to think about.

Keep in mind that this situation could happen numerous places other than just mining but if there is such a place where the client makes decisions like this, it will be very hard to find.

^^Just My Two Cents^^