Cheat Engine

[peddroelm]

[ParkourPenguin]

It tells you the line number in the error message. "10:", "413:", "17:"

Indenting your code might help you track down errors.

[peddroelm]

Thank you for the many times I've read helpful bits of info from your posts on these forums over the years ParkourPenguin !

> " It tells you the line number in the error message. "10:", "413:", "17:" "

Don't know what 'Im doing wrong (comments / empty lines) by in my experience the line number it provides never matches the line in the code editor .. If its a syntax error I copy/paste the function into an online lua compiler like https://www.tutorialspoint.com/execute_lua_online.php and that will put the finger on the right error line .. Can't do that for runtime errors ..


> "this is bad !"
readInteger(readInteger(addr))

readPointer ... (as per Wiki) uses readInteger for x32 application which this is .
What is the advantage ? Code readability ?

Is it capable of handing multiple level pointers without need to manually check for nil at ever offset ? Will just gracefully provide nil at the end which one can check for once at the end ?

What about something like this :
return

[ParkourPenguin]

[peddroelm]

[ParkourPenguin]

You can't add an integer to nil.

Offsets are a problem. I think I'd make my own function to handle that gracefully:

[peddroelm]

So for non critical errors I might want just silently return

check for readPointerPath( ..) for nil

In the cases we need to crash the script .. assert seems like a good call but the extra strings you return aren't helping (by themselves)

Hey an Assert( readPointerPath( ..) )
failed .. I'm only calling it from a bazillion places..

The assert error text must have function name and assert index in that function ..

This , right here officer , .. the 4th assert in the "blabla" function brought us down !

local var = readPointerPath (base + offset list )
assert(var, " Script name(would be nice if lua had a function for it otherwise type by hand every time) + again by hand index of assert in function xx ")


error :: Log_EmpircalTell_DiceRoll 5


debug.getinfo might gimme function name ?


The following function illustrates the use of debug.getinfo. It prints a primitive traceback of the active stack:

https://www.lua.org/pil/23.1.html

function traceback ()
local level = 1
while true do
local info = debug.getinfo(level, "Sl")
if not info then break end
if info.what == "C" then -- is a C function?
print(level, "C function")
else -- a Lua function
print(string.format("[%s]:%d",
info.short_src, info.currentline))
end
level = level + 1
end
end
It is not difficult to improve this function, including more data from getinfo. Actually, the debug library offers such an improved version, debug.traceback. Unlike our version, debug.traceback does not print its result; instead, it returns a string.


Ha