CO2M8-Account/Session Manager, MultiFunction Trainer

Version 1.34 of CO2m8 is now available!!!

Found a couple of flaws in the DMA patching triggers in version 1.33,
so recommend you all update to this version asap.

Whats New
Bug fixes.
If you select character and then press the client shortcut it does a smoother login that works on all PCs.
Auto answer do trade/join guild/join team questions,
beware its one setting for all so I don't recommend auto OK for general usage.

Yes this version does do HP/MP and Mining functions for v4356 of the game client, click the "Use DMA Defeat" checkbox before you start any clients.

I like ;) the co2m8-q&a.txt you include now.
Hope it helps people out with figuring things out.

1.34 looks good, keep up the good work!

Thank you! :cool:

Quote:

Originally Posted by joek Version 1.34 of CO2m8 is now available!!! Found a couple of flaws in the DMA patching triggers in version 1.33, so recommend you all update to this version asap. Whats New Bug fixes. If you select character and then press the client shortcut it does a smoother login that works on all PCs. Auto answer do trade/join guild/join team questions, beware its one setting for all so I don't recommend auto OK for general usage. Yes this version does do HP/MP and Mining functions for v4356 of the game client, click the "Use DMA Defeat" checkbox before you start any clients.

im unable to use the 4356.r1-DMAc for the memory addresses as it causes my clients to crash, when loading the client, and when enabling that memory table while running the client, 4355.r1-DMAc works fine, but the minning settings dont work (they are enabled they just dont do anything), i know this will be because im using the incorrect memory table for my client verison,

any idea what i can do to resolve the 4356.r1-DMAc issue?

yes my client is at version 4356.

yes both the program settings and char settings use 4356.r1

Quote:

Originally Posted by Korvacs im unable to use the 4356.r1-DMAc for the memory addresses as it causes my clients to crash, when loading the client, and when enabling that memory table while running the client, 4355.r1-DMAc works fine, but the minning settings dont work (they are enabled they just dont do anything), i know this will be because im using the incorrect memory table for my client verison, any idea what i can do to resolve the 4356.r1-DMAc issue? yes my client is at version 4356. yes both the program settings and char settings use 4356.r1

If its crashing yes its incorrect DMA patching, the values I'm using for 4356 are based on an english client thats had nothing done to it, have you patched it in anyway or unpacked it.
Could also be other tools or bots that may injecting something that clashes.
Has anyone else got this working with 4356?

Quote:

Originally Posted by joek If its crashing yes its incorrect DMA patching, the values I'm using for 4356 are based on an english client thats had nothing done to it, have you patched it in anyway or unpacked it. Could also be other tools or bots that may injecting something that clashes. Has anyone else got this working with 4356?

the mining function works well for me

Quote:

Originally Posted by joek If its crashing yes its incorrect DMA patching, the values I'm using for 4356 are based on an english client thats had nothing done to it, have you patched it in anyway or unpacked it. Could also be other tools or bots that may injecting something that clashes. Has anyone else got this working with 4356?

only thing ive done is modifiy conquer.exe for multiclient, i dont use any other tools or bots,

-shrugs- changing a E -> C in hex cant throw everything off surely =/

Quote:

Originally Posted by Korvacs only thing ive done is modifiy conquer.exe for multiclient, i dont use any other tools or bots, -shrugs- changing a E -> C in hex cant throw everything off surely =/

Try doing it manually, login a character without the DMA checkbox enabled, then under the char options(S screen) select the memory options button.
Set the correct memory table and enable DMA in this screen then press reset, if it doesn't crash press refresh and you should be able to see the correct HP in the table.
If it still crashes double check the co version by looking at the version file in the co folder, could also mean theres more than one 4356 co exe around, I got mine right at the beginning.
Perhaps a re-patch of the 4356 client may help.

As I said more than once, now I play CO once every month, maybe, but I never fail to check epvp nor especially this thread... and couldn't miss the opportunity to test the new version, which actually works with HP (just tested that one with war in BI). Only once it trigger the pot too soon, when I was at 1800 maybe while the limit was 1100. I'm almost sorry not to play CO anymore because of co2m8... now that it's become so cool a tool, I don't need it anymore :D
Autotrade is cool, you may want to add both an auto-ok for open trade window and another auto-ok for accepting the trade, so one could sit a noob in TC-market and use it as a 40 slots wh without even needing to touch it, in a way similar to how sacob did. Just my two cents :P

Quote:

Originally Posted by ephe As I said more than once, now I play CO once every month, maybe, but I never fail to check epvp nor especially this thread... and couldn't miss the opportunity to test the new version, which actually works with HP (just tested that one with war in BI). Only once it trigger the pot too soon, when I was at 1800 maybe while the limit was 1100. I'm almost sorry not to play CO anymore because of co2m8... now that it's become so cool a tool, I don't need it anymore :D Autotrade is cool, you may want to add both an auto-ok for open trade window and another auto-ok for accepting the trade, so one could sit a noob in TC-market and use it as a 40 slots wh without even needing to touch it, in a way similar to how sacob did. Just my two cents :P

Hi ephe, alway glad to have your constructive criticisms and suggestions.

Yup HP in memory is being polluted by TQ since version 4355.
I'm working on scrubbers for the next version of M8.

I do like the auto accept trade idea I will play with it :)

Hi joek.
The value for "Current mana"/"current hp" never change. Both values always show "0". Do you have any ideas how this could be solved?

co client: 4356
mem-table: 4356.r1 (dma-defeat: on)

I still dont like the interface of this - joek, its a lil 'busy' with the colours, you gonna do a version with the traditional look and feel of windows? (button-grey and blue) XD

Vert~

Quote:

Originally Posted by gta74 Hi joek. The value for "Current mana"/"current hp" never change. Both values always show "0". Do you have any ideas how this could be solved? co client: 4356 mem-table: 4356.r1 (dma-defeat: on)

It only changes in the setup screen when you first open the screen, use the memory options screen and the refresh button if you want to watch the numbers.

Quote:

Originally Posted by Vert1go I still dont like the interface of this - joek, its a lil 'busy' with the colours, you gonna do a version with the traditional look and feel of windows? (button-grey and blue) XD Vert~

Well your the only one that ever mentioned they don't like colour, so no probably not. You could alway change your video setup to monochrome that way you will never get bothered by all those pesky colours ;)

Hi again.
If I enter the mem-options all values show "0" (except: Exp-Count, ClientZoom and messagecount). Pressing refresh does not help at all. The hp/mana values dont change at all.

Quote:

Originally Posted by gta74 Hi again. If I enter the mem-options all values show "0" (except: Exp-Count, ClientZoom and messagecount). Pressing refresh does not help at all. The hp/mana values dont change at all.

On that screen, what happens when you enable "dma defeats" checkbox(check table version also) and then press the reset button under "all items" heading(saying OK to the question), followed by a few clicks of the reset button.

I enter the MemOptions (VolatileMemoryConfiguration)
- mem-table= v4356.1-dma
- use dma-defeats = checked

When I press reset, a popup appears, saying: "Updated Information from //path//ma-global.inf Version:4356 Rev:1".

Pressing ok leads to another popup: "client xxxxx already DMA patched, do it again?". If a patch again, the problem keeps the same --> The memory locatio list shows "0" for mana/hp. Even if refresh is pressed.