2017-03-27 08:43 CEST

View Issue Details Jump to Notes ]
IDProjectCategoryView StatusLast Update
0000396Cheat Engine(No Category)public2015-07-13 00:41
ReporterHans Henrik 
Assigned ToDark Byte 
PriorityhighSeveritymajorReproducibilityalways
StatusresolvedResolutionfixed 
Summary0000396: no good way to see "conditional complex breakpoint" errors
Descriptionwhen writing conditional complex breakpoints,
if i make a syntax error, or an undefined variable error,
the lua execution will __SILENTLY__ crash, as far as i know, there is no way to see the error, when, where, or why. makes it much harder to debug complex conditional breakpoint scripts; could we fix this somehow?
TagsNo tags attached.
Attached Files

-Relationships
+Relationships

-Notes

~0000829

Dark Byte (developer)

there will now be a messagebox when a lua script fails
+Notes

-Issue History
Date Modified Username Field Change
2015-07-09 12:24 Hans Henrik New Issue
2015-07-10 02:48 Dark Byte Assigned To => Dark Byte
2015-07-10 02:48 Dark Byte Status new => confirmed
2015-07-13 00:41 Dark Byte Note Added: 0000829
2015-07-13 00:41 Dark Byte Status confirmed => resolved
2015-07-13 00:41 Dark Byte Resolution open => fixed
2016-06-05 15:18 Jptnuc Issue cloned: 0000484
+Issue History