Cheat Engine

tikiking1 · How do I cheat? Reputation: 0 Joined: 23 Jun 2014 Posts: 1

CEServer refuses to work. I'm using the newest downloads off the front page.

Linux system is running:

Dark Byte · Posted: Mon Jun 23, 2014 6:25 pm Post subject:

Thanks, i'll check it out. Perhaps the formatting of /proc is slightly different

vityav · Newbie cheater Reputation: 0 Joined: 24 Oct 2014 Posts: 15

I have the same exact problem in both Fedora 17 and Arch linux, both attempted with the client in Wine and in a virtual machine, and both with the newest (only listed) ceserver, and Cheat Engine 6.4.

With all the steam games now starting to support linux (specifically for steamos), I really hope a linux Cheat Engine can be worked out. CE is miles ahead of any other linux memory scanning/hacking tools.

efjay · Newbie cheater Reputation: 0 Joined: 17 Apr 2014 Posts: 12

Also having the same issue, built it from source for fun and it connects, but it hangs and the client doesn't get the process list.

Dark Byte · Posted: Sun Oct 26, 2014 6:04 pm Post subject:

Which linux distro? Kernel version?
I tested with mint 14 (might be a bit outdated now)

my guess is that the /proc folder structure isn't fully what ceserver expects it to be

vityav · Newbie cheater Reputation: 0 Joined: 24 Oct 2014 Posts: 15

I'm on kernel Linux v 3.16.4-1-ARCH. Not quite sure how to compile it (lots of 'undefined reference' errors when I try), but looking through the code, all the files it seems to be looking for in /proc seem to be there. Any suggestions on what in particular to look for?

Dark Byte · Posted: Mon Oct 27, 2014 3:54 pm Post subject:

Perhaps you have a process running where the path of the exe is longer than 255 bytes

api.c line 2595 contains a bug but not sure if that is it. Try adding some debug messages to see where it goes wrong

efjay · Newbie cheater Reputation: 0 Joined: 17 Apr 2014 Posts: 12

Ah yes, I believe the issue is that 255 byte limit. :/.

efjay · Newbie cheater Reputation: 0 Joined: 17 Apr 2014 Posts: 12

I played around with the source and limited the size of the strings on the server, now it doesn't send strings too big for the client and it seems to be working fine.

Woo!

edit: thought I'd add my patch, it's very rough, and done on the fly, probably lots of errors and what not. I just kept tinkering until it did not hang.
apparently I can not attach it so here it is.

-- when I go to memory view, it is filled with ??, no values are coming up .
-- this might be related to any green address showing up as ("[heap]" + hex), which point to garbage ??.

Dark Byte · Posted: Tue Oct 28, 2014 3:28 pm Post subject:

Thanks. I doubt those sprintf's with only %d are the issue though

efjay · Newbie cheater Reputation: 0 Joined: 17 Apr 2014 Posts: 12

Dark Byte · Posted: Tue Oct 28, 2014 3:33 pm Post subject:

yeah, the symbolhandler is messing up. Probably because the symbol starts with [ (interpret first bytes as pointer) and heap shouldn't be an official symbol used for statics anyhow (too random)

efjay · Newbie cheater Reputation: 0 Joined: 17 Apr 2014 Posts: 12

vityav · Newbie cheater Reputation: 0 Joined: 24 Oct 2014 Posts: 15

I can confirm efjay's patch works wonderfully. Thanks!

To continue hijacking this thread: is it possible to adapt a cheat table made for windows to this? Or are the structures/offsets too different? E.g. running the game FTL (for something easy that I know works and is on both windows and linux), I can manually find the value of scrap at 1A8A2040. The windows cheat table for it suggests it should be at "FTL"+0039BA90, but that works out to be 0079BA90, which is just question marks in the memory viewer. Am I missing some method of adaptation, or is it a lost cause?

Dark Byte · Posted: Wed Oct 29, 2014 6:05 pm Post subject:

the difference in specific addresses is likely the same if they belong to the same object

e.g health and armor are often stored close together and it's likely that the distance between them is the same in the linux version.
So if you find health, you know where armor is.

As for static addresses like FTL+xxxx that's most likely a lost cause as they are different versions. (see it like a patched version, there the old address won't work either)