Safe guid memory writes in modern game clients

[swnt]

Hey,

like lots of other ppl I started out creating an out-of-process bot.
While the project gained functionality and now successfully grinds/loots/(farms) and uses a global navigation mesh, I am at a point where I would really like to advance some of the basic actions;

E.g. targeting using tab is usually not a problem but multi-doting over lots of targets can be inefficient.
Same can be said for my (not perfectly working) world2screen calculation when trying to click targets (looting, gathering, ...).

Thats why I started reading up on pitfalls when writing to wow memory. While I found some examples (most of which applicable to injections or hooking), I wasn't able to gather much safety concerns about writing to basic guid addresses like mouse-over-guid or last-target-guid. I get that i'm leaving the strict out-of-process train here but before continuing that route, would anybody with a little more experience be able to comment if writing to these addresses (or the possibility of a broken target history) is of any relevant concern? I get that we never know which checks might be coming in the future but I'd rather be interested in your experience/opinion up to today.

As I said, most of the discussions I found is not relevant or about pretty old game clients (2015 and older).

Thanks!

[charles420]

u fine writing to these no checks as of now this time based off scans and warden loaded this could change any time i can post my scans a lil later biggest thing no public thing profit

[Razzue]

Hey,

like lots of other ppl I started out creating an out-of-process bot.
While the project gained functionality and now successfully grinds/loots/(farms) and uses a global navigation mesh, I am at a point where I would really like to advance some of the basic actions;

E.g. targeting using tab is usually not a problem but multi-doting over lots of targets can be inefficient.
Same can be said for my (not perfectly working) world2screen calculation when trying to click targets (looting, gathering, ...).

Thats why I started reading up on pitfalls when writing to wow memory. While I found some examples (most of which applicable to injections or hooking), I wasn't able to gather much safety concerns about writing to basic guid addresses like mouse-over-guid or last-target-guid. I get that i'm leaving the strict out-of-process train here but before continuing that route, would anybody with a little more experience be able to comment if writing to these addresses (or the possibility of a broken target history) is of any relevant concern? I get that we never know which checks might be coming in the future but I'd rather be interested in your experience/opinion up to today.

As I said, most of the discussions I found is not relevant or about pretty old game clients (2015 and older).

Thanks!

I can't say if scanned or not, someone with a bit more experience would likely have better input.
but my experience over the last few (6 - 8 months for a project i'm playing with, and letting a few buddies use:
- I write to Mouseover GUID for looting, targeting, interacting etc
- I write to last UI message to clear errors (Los, no fish hooked, cant cast etc)
- I write to AutoLoot/Ctm toggles, but I don't like doing this as it only changes 1/3 values that change when you toggle them manually.

I also recently peeked into action bars and writing a spell id to the first action button and spamming that (Yes it does work xD) though idk how i feel about that :P
with no bans strictly because of the project yet. *knock on wood*

[swnt]

Nice, thanks for sharing your personal experience!

I can't say if scanned or not, someone with a bit more experience would likely have better input.
but my experience over the last few (6 - 8 months for a project i'm playing with, and letting a few buddies use:
- I write to Mouseover GUID for looting, targeting, interacting etc
- I write to last UI message to clear errors (Los, no fish hooked, cant cast etc)
- I write to AutoLoot/Ctm toggles, but I don't like doing this as it only changes 1/3 values that change when you toggle them manually.

I also recently peeked into action bars and writing a spell id to the first action button and spamming that (Yes it does work xD) though idk how i feel about that :P
with no bans strictly because of the project yet. *knock on wood*

Another question that comes to mind: do you have any experience with running the game client in background? To me it would seem like an easy detection method, wow being "played" while window is in background for majority of time. It's not really being talked much about, I know on old game versions this has been done, not sure about any modern game clients.

[MrNoble]

I can't say if scanned or not, someone with a bit more experience would likely have better input.
but my experience over the last few (6 - 8 months for a project i'm playing with, and letting a few buddies use:
- I write to Mouseover GUID for looting, targeting, interacting etc
- I write to last UI message to clear errors (Los, no fish hooked, cant cast etc)
- I write to AutoLoot/Ctm toggles, but I don't like doing this as it only changes 1/3 values that change when you toggle them manually.

I also recently peeked into action bars and writing a spell id to the first action button and spamming that (Yes it does work xD) though idk how i feel about that :P
with no bans strictly because of the project yet. *knock on wood*

CTM values have been encrypted for years now, I wouldn't recommend writing to them. Just because they work and you didn't get banned doesn't mean they are safe.
From my observation, there are nearly no public bots and they seem to not care enough to ban players.

[Razzue]

CTM values have been encrypted for years now, I wouldn't recommend writing to them. Just because they work and you didn't get banned doesn't mean they are safe.
From my observation, there are nearly no public bots and they seem to not care enough to ban players.

The toggle is not, and is what I was talking about. You can write 1/0 to enable/disable it just fine using the offset, however, there is also a counter, and an additional value that cycles 1/0 when you toggle it manually in game.