Cheat Engine

[paul44]

some info: [ https://imgur.com/a/clibQqc ]

I started to receive this error pretty early on in dev_stage... As soon as i run the 1st 'Run xxxx' script in the table, it will return this error. However: sofar it does seem to execute everything just fine?! But obviously like to get this removed/solved.
The 2nd image shows the contents of the 1st 'Run xxxx' script, but no matter which script I run (apart from the 'info' & 'param' one), it will "hit" all of them thereafter...

btw: searching for possible remedies, one post mentions a mem_related issue (alloc not properly defined). also tried to pinpoint possible error_location with some prints, but no cigar...

Need more info/details: just ask !

ps:
a. the 'Parametrization' just initializes the proper vars (~ globalalloc's - also tried to replace them with alloc's)
b. the table uses the Lua startup script, containing some "global" routines (+ some stuff to build the gui ~ which does not relate to this error; already got the error prior to "inserting" the gui)

[ParkourPenguin]

I didn't look at your code for that long, might be missing something.

You have a random "test al,al" instruction at the end of the {$lua} block with nothing else defining where it should be written to.

I don't see that {$lua} block return any string, so you should also have "if syntaxcheck then return end" at the start of that {$lua} block. Otherwise it'll be run twice if you fix the previous syntax error of "test al,al"

[paul44]

that was actually the reason: 'test al,al'

where this comes from ?: [ https://forum.cheatengine.org/viewtopic.php?t=606629&sid=a916286c92a67f30f387a6ab1744d544 ]

I never had any problems with it (since only using in Help functions); so did not realize it returned that error (just double-checked a "live" table, and indeed...)

ps: "Otherwise it'll be run twice..." - i assume this happens [b]only[/b] when editing the script, not when 'enabling' it ?!

btw: tried 'error()' suggestion, but this gives me a syntax error...

anyways: topic closed (and sorry for not having noticed this myself)

[ParkourPenguin]

[paul44]

I assume you'd like to know how many times it "reports":

a) press [OK] to finish editing: both return 'true' (with and without test instruction)
b) with test instruct: only 'enabled' giving 'false'
c) with test~alloc(newmem): 'enabled/disabled' return 'false' (and no errors in this case, but no auto-disable either of course)

iow: in both cases, it would run only once per 'click'

that said: either i follow suggestions from other topic (basically use a timer), or stick with what i have now. and since this table is 'Tablemakers only' - and i now know where the error comes from - i leave things until something more elegant falls out of the closet...
cheers