Re: v1.08

Noticed your not posting/updating at the CEF, why so? Did we run you off there?

Re: Cheat Tool Set - A tool like CE

Posted: Tue Oct 16, 2018 9:01 pm

by JohnFK

Estimated scan time is completely off. For example it starts with 50 seconds, counts down to 30 seconds, then counts down and up for a while and ends with -1 and your progress bar never resets making me thought it would still scan. Overall scan duration was 122 seconds. Game was 64-bit and settings were unknown scan 4 bytes.

As you can see, there is great potential for optimizing your memory scanner.

For the debugger why you only support 1 breakpoint at all, whats about the other 3 debug registers? Also I cannot find xmm registers. And how can I add a breakpoint in memory viewer and step through?

//edit: Your VEH debugger does not inject anything into the target game nor does AddVectoredExceptionHandler gets called but DebugActiveProcess and WaitForDebugEvent. What kind of VEH is this? Looks like a normal windows debugger to me

//edit2: Yep, its definitely NOT a veh debugger:
CE:

Attached my test application for verification. But I've also noticed its much easier to figure out you are using windows debugger API by just calling IsDebuggerPresent which returns true for your tool, with a VEH debugger it would return false.

I hope nobody paid you $300 for your source code yet as this goes close to be scam.

Re: Cheat Tool Set - A tool like CE

Posted: Sat Oct 27, 2018 9:56 pm

by H4x0rBattie

Thanks JohnFK for pointing out the issue.

As you can see, there is great potential for optimizing your memory scanner.

Yes and I did. 1.09 dev. version has it fixed. "Unknown initial value" scan "First scan" is now faster than CE. After the first scan has completed for the "Unknown initial value". The first "Next scan" is clearly faster than CE. The more RAM the opened process consumes, the more clearly you will see the difference.

This comparison is not even fair because CE is using on my system 8x threads whilst CTS uses just 4x threads. Also you must have game paused before you do any comparison anyway.

CE's progress (6.8.1) bar is also off. It gives you an illusion that a scan has completed though it is not.

You can re-produce it at any time by doing as follows:

1) Start "Unknown initial value" with game that uses at least 2GB of RAM
2) Wait until progress lets you know that "Next scan" has been "completed". Immediately after that click the "Next scan" button again and below happens:

CE allows you to "Next scan" after there is nothing to write to files. I measured this with a stopwatch and 1.09 dev. version of CTS was clearly faster. I think this is a bug in CE but anyway.

For the debugger why you only support 1 breakpoint at all, whats about the other 3 debug registers? Also I cannot find xmm registers. And how can I add a breakpoint in memory viewer and step through?

It is easy to ask for "Why this and that". Use CE if you need more than one. These features do not happen by clicking on the fingers. Why should I re-invent the wheel? Debugger features are the most difficult ones to implement and I will only add what I need most and I do not discuss beforehand what I need.

I hope nobody paid you $300 for your source code yet as this goes close to be scam.

And now? On other CE forum some claimed (if I remember correctly) that I haven't coded the software ...

The tool is using 4x threads vs CE's 8 and is now (1.09 dev. version) notably faster with "Unknown initial value" scan. Also did not you noticed "Dump process memory to file" option that does not exist in any other current tool for "Unknown initial value" scan.

And why do you even care? It's easy to say because you did not develop the program for a second. The definition of scam is something else therefore; please do not mention my tool and scam in same sentence unless you're here to slander.

Let me ask you another question. Lets say if it was you who worked 4 hours on the tool every day for over a year. How much you would ask for it?

PS.

I do not want to brag but I've seen really a lot of effort into the software. That is why I do not accept these false claims in any form.

Re: Cheat Tool Set - A tool like CE

The definition of scam is something else therefore; please do not mention my tool and scam in same sentence unless you're here to slander.

You wrote your software has a VEH debugger which is not true as I've proven above. Instead its using a windows debugger API. You sell something and advertise it with features it doesn't have and that's what makes it scam and why I hope nobody paid that money to you in expectation of a VEH debugger source code.

That's scam per definition but can easily be solved by just correct your feature list or add a real VEH debugger.

Re: Cheat Tool Set - A tool like CE

...The definition of scam is something else therefore; please do not mention my tool and scam in same sentence unless you're here to slander....

What exactly is this "something else", please define "scam" then.

Your charging money for source code and are saying it has features it doesn't actually have. By definition that's "false advertising", and thus a scam, or swindle if you prefer. And there is clear case law in the US in regards to this, and specifically with software features (you can actually be charged/sued for "false advertising" in the US, without someone even buying the product). And so where you're getting "slander" is beyond me, because again there's clear case law in regards to slander and false advertising; and falsely clamming "slander" is a "slader us actuation" and thus slander in itself (some good meta humor here). And I don't think you can actually "slander" an object, only people or companies (not really sure about this, would have to look at case law).

: to utter slander against : DEFAME
slander noun
Definition of slander (Entry 2 of 2)
1 : the utterance of false charges or misrepresentations which defame and damage another's reputation
2 : a false and defamatory oral statement about a person

So just to be clear, YOUR TOOL APPEARS TO BE A SCAM. But as already said, you can fix this really easily, just make your "documentation" reflect the actual tool and not the planed [future] tool.

EDIT:
Don't get me wrong, it's a neat tool and thanks for sharing the program freely; but your basically looking at CE and then adding the features it already has then just doing it differently and acting as if you invented it. But I guess you could say your a fan of Eddison, he's often credited with things he never did; most people think he invented the lightbulb even though he only patented what a staff member came up with for a working filament.
EDIT:
And you're doing all this on forums centered around CE, just seems like preaching Islam to Catholics; it's not ever going to go well.

Re: Cheat Tool Set - A tool like CE

At the writing time of the code and description I did not quite understand what a "VEH" debugger meant by. I've got a "wisdom" from above ...

I've corrected feature description on the official site. The both versions of the debuggers are using HWBP's for a speed ...

Is not that a little exaggeration to make the whole software a "scam" for such a small case? In the forum where everyone else is hypocritical ...

Don't get me wrong, it's a neat tool and thanks for sharing the program freely; but your basically looking at CE and then adding the features it already has then just doing it differently and acting as if you invented it

I am looking at CE because it missed some features I needed. Have a look at version 1.09 "About" ...

Did you want to see where this program came from? Or did not you understand why it came from? For this I did not released the tutorials in this forum ...

Questions for "wise men":

From whom did the first person in this planet got the "wisdom"?

Does the forest know that it exists? Why do you just read this, you know that you are there?

What makes the tiger do the same as it does?

The time I spent with this unnecessary program made me publish it to you ...