Skip to main content

GameConqueror 0.09 -- Linux Game Hacking Tool

If you are a game hacker
If you've been looking for a `CheatEngine for Linux`

Then you can't miss this.

==============================================


GameConqueror is a game hacking tool for linux, it's written in PyGTK and uses scanmem as its backend.

It's supposed to be with most useful features of CheatEngine for Linux.

Currently, I've implemented almost everything about scanning, involving variant data types and scan types:

Data Types: int{8/16/32/64}, float{32/64}, unknown type(int or float) and unknown width(will try each of them), byte array and string
Scan Types: equal, greater, less, changed, unchanged, increased(by), decreased(by)

This should be enough for most cases, so I decided to release it at the current status.

=============================================

Here's how you can get it

PPA (for Ubuntu users)
https://launchpad.net/~coolwanglu/+archive/scanmem
(I've not test it in 32bit environments or Jaunty, do please inform me if it doesn't work)

SVN
svn checkout http://scanmem.googlecode.com/svn/trunk/ scanmem

Homepage:
http://code.google.com/p/scanmem/
make sure you selected the correct version `0.09`

You'll need python and python-gtk to run it, and to build it from source code, you'll need libreadline (this should have been installed for most of you)

=============================================

NOTE THAT GAMECONQUEROR MAY CRASH YOUR PROGRAM DUE TO BUGS OR IMPROPERLY USAGE, DO BACKUP YOUR PROGRESS BEFOREHAND.

To use it, actually I've created a menu item, which could be found in the 'Games' category, or you can run it by executing `gameconqueror`, and please do this in a terminal (see below)

Read the tooltip of the label 'Value' to get familiar with the syntax

About the annoying terminal window, now this is the only place where you can see the progress of scanning, and the error message if something goes wrong. This terrible thing is basically because I've mainly focused on the features of scanmem so far, and I'll fix this in the next version.

=============================================

What will be added in the next (or maybe future) version:

- better ui (progress bar, error message, user interaction, etc...)
- search for pointers
- optional float rounding method
- memory viewer/editor


and what will not be added
- speed hack (I've no idea about how to implement this in Linux, can anyone tell me plz?)
- disassembler
- many other `too powerful` features in CheatEngine


any feedbacks will be appreciated.


Comments

Popular posts from this blog

A Rocky Migration: Moving from docker-compose to Podman and gVisor

I've been running a few containers for several years. They were all running under rootless Docker with a single user. Initially, I planned to  migrate the containers to VMs , but I couldn't get a stable workflow after about two months of effort. Later,  gVisor caught my attention , and I decided to migrate to Podman with gVisor instead. The new plan is to run each container with  --userns=auto  and use Quadlet for systemd integration. This approach provides better isolation and makes writing firewall rules easier. I'm now close to migrating all my containers. Here are a couple of rough edges I'd like to share. Network Layout I compared  various networking options  and spent a few hours trying the one-interface-per-group approach before giving up. I settled on a single macvlan network and decided to use static IP addresses for my containers. To prevent a randomly assigned IP address from conflicting with a predefined one, I allocated a large IP range for my ...

Fix Google Security Code

Google Security Code (http://g.co/sc) is one type of 2-step verification. This is particularly useful when security keys and passkeys are not available. I have been using it in my LXC containers, until today I found out that it stopped working. It just kept saying "The code is invalid". It is easy to rule out some factors: The code works on other browsers on my laptop. The code works on other devices that are directly connected to the router. So it appears that Google also checks IP addresses besides the security code. Recently I have IPv6 enabled, so most devices that are directly connected to the router have both IPv4 and IPv6 addresses. But  I only enabled IPv4 for my LXC containers. So I guess when a code is generated by device A and used by device B, Google should be able to check that device A and device B are closely located. But in my case, IPv6 address appears on device A but not on device B, which may look suspicious. To fix the problem, I just needed to disable IPv...