1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112
17:30FUCKYOU
FUCKYOURebecca WTF is going on here?
17:26FIXED
FIXEDWell At least I fixed that... :-/
17:24FUCKYOU
FUCKYOUCan a forgotten ) really cause an infinite loop crashing many programs?
17:23SITE
SITEAdded tag FUCKYOU
17:19FAILURE
FAILUREWTF is going on here?
17:15TEST
TESTAnd again!
17:14POWERSHELL
POWERSHELLOn da case!
17:14STUPIDITY
STUPIDITYI must (of course) not forget to recompile NALA first
17:13DEBUG
DEBUGTemporarily deactivated the SASKIA script
17:12DEBUG
DEBUGI've also made an in-field command for that.
17:11STATUS
STATUSMy prime target is now #14... The previous entries were to allow me to debug this more easily and check the data before I actually get into doing #14 itself
17:05LINK
LINKWrote the NIL link code
16:18VISUALSTUDIO
VISUALSTUDIOKthura Meta Data manipulation routines written
13:31TODO
TODOGive my brain some rest before I begin on the BoxText routine
13:31CLOSED
13:31REMOVED
REMOVEDAll debug lines from SASKIA as they can spook up when being used in other people's projects
13:27FIXED
FIXEDAccording to the data I now see in the debug log, all SASKIA bugs should be accounted for...
13:20TEST
TESTAnd let's see what we get next!
13:20DEBUG
DEBUGAnd the debug line is now formed accordingly... I hope!
13:20STUDY
STUDYIn order to get well into this debugging, I did a bit of study!
13:08EXPERIMENT
EXPERIMENTWell, let's try this in stead then.... :-/
13:02FAILURE
FAILUREWTF is happening...
13:01MYSTERY
MYSTERYSomething makes NALA take too much memory, but whatever it is that causes it.... Who knows....
12:56TEST
TESTWell let's test this again, to see if stuff works now....
12:09FAILURE
FAILURENow I did get a crash message from GIMP, but I wonder if that was the source of all "evil"
12:09FAILURE
FAILURESomething's wrong here... Everything froze
12:05DEBUG
DEBUGlet's gather some info here... :-/
11:58CONFIRMED
CONFIRMEDThe counter value the debugger returns confirms this!
11:58TECHNO
TECHNOMy hunch appears confirmed... Two sessions get into the memory in stead of one!
11:55DEBUG
DEBUGLet's do this to find out or rule out
11:52SOLVED
SOLVEDAh yeah, the start at position 2 is explained due to the OnLoad chunk containing one "end" instruction so that was at least NOT a bug!
11:51SOLVED
SOLVEDScyndi Indeed, I had to form the call in the boxtext routine differently, so that issue has been resolved....
Doesn't answer why it takes two instructions at once though.....
11:48EXPERIMENT
EXPERIMENTOr maybe.....
11:47MYSTERY
MYSTERYThe clue is, everything works the way it should except for the fact that no results are produced... Can you still follow?
11:41DEBUG
DEBUGMore debugging lines as things do get stranger and stranger....
11:38DONE
DONEA little break, and boy I needed that!
9:49COCKROACH
COCKROACHClearly... NOT!
9:46DEBUG
DEBUGI've added a debug line to the boxtext linker... This line will indicateif the boxtext initiator was called at all!
9:44DEBUG
DEBUGMOAR debug stuff to get to the bottom of this.... Are all commands skipped, or simply never executed?
9:33FIXED
FIXEDArrays in Lua are based on 1 ... not 0
9:32FIXED
FIXEDFixed the SASKIA script... I think....
9:30TEST
TESTLet's test!
9:29FIXED
FIXEDI think I fixed this now....
9:27STUPIDITY
STUPIDITYSTRONT!
9:25DEBUG
DEBUGSome more lines added to get some answers....
9:23ANALYSIS
ANALYSISthe data generate rule out the possibility of this error... Further investigation is required, I guess...
9:17REMOVED
REMOVEDAnd I removed an older no longer needed debug line.
9:17DEBUG
DEBUGLet's see what this extra debug line will do
8:01MYSTERY
MYSTERYAnd now it seems its sees the parameter, but deems it.... empty????
8:00DONE
DONEAsserted added due to another crash
7:55FIXED
FIXEDSession parameter missing
7:53DONE
DONEWhitelines will now be ignored... completely!
7:52COCKROACH
COCKROACHand once again WHITELINES are at evil
7:50DEBUG
DEBUGAn extra debug line's been added in order to investigate that one!
7:50COCKROACH
COCKROACHInstruction is ""?
7:41NOTE
NOTEBut in my defense I must note that I couldn't test SASKIA until the moment it would see action
7:41STUPIDITY
STUPIDITYBrendor BOZO! 'ins' is a class, not a string variable... Add the field .command to it...
7:38STATUS
STATUSGetting somewhere, but it's not yet enough
7:35MYSTERY
MYSTERYis "true" as bugged as "nil"?
7:33SOLVED
SOLVEDI think I found the reason why this is happening!
7:32CONFIRMED
CONFIRMEDYes, the cycle does NOT allow the script to be executed, as I suspected.... The question now is.... WHY!
7:31TODO
7:30DEBUG
DEBUGA temp debug line to investigate #12
- = 30 Jul 2019 = -
23:19ACHIEVEMENT
ACHIEVEMENTGrim Reaper
23:14GITHUB
GITHUBissued as #12
23:11BUG
BUGI cannot yet be sure, but it seems like the SASKIA scripts are being ignored... Also given by the fact the script wanted to unlink to soon.... I need to fully investigate this!
23:08FIXED
FIXEDFunction so ()
23:07DEBUG
DEBUGAdded FLOW command, as I don't trust things at the moment....
23:05CONFIRMED
CONFIRMED
23:04FIXED
FIXEDCase Error?
23:04FIXED
FIXEDFixed the label issue
23:02SOLVED
SOLVEDAh... stupid... I didn't include the start label yet, as I was supposed to add it later, and I forgot its earlier omission
22:46DEBUG
DEBUGMOAR debugging crap!
22:43DEBUG
DEBUGI've added an extra line that should answer a few questions
22:40BUG
BUG
22:32DONE
DONEI've set another thing for a new stack, and I hope that fixes something :-/
22:29FIXED
FIXEDI think I fixed it
22:28BUG
BUGBut the label parser is completely bogus...
22:28BUG
BUGOn-Load label not found
22:21MYSTERY
MYSTERY"Annoy" can NEVER be 'nil' without NIL not crashing on it in translation, however the fact that the eror was thrown means something right, as the infinitely loop is now broken...
22:18FIXED
FIXEDIrravonia I added one, and that should fix things!
22:18SOLVED
SOLVEDNo incrementor?
22:16NOTE
NOTEFor some reason the traceback doesn't show!
22:07FIXED
FIXED
22:07STUPIDITY
STUPIDITYWrong class call
21:41OFFTOPIC
OFFTOPICI know BAD PUN!
21:40FIXED
FIXEDMore missing "self awareness" issues
21:39FIXED
FIXEDA missing "self" issue in the datetime library
21:38CONFIRMED
CONFIRMEDNow that SASKIA requires the datetime library and the game itself does not, I could check if libraries requiring other libraries worked properly, and that it does... so at least this cockroach was good for something!
21:35DEBUG
DEBUGI've put on a few time-out error enforcers to find out where the infinite loop could be
21:32DONE
DONEI've set up a quick datetime routine and a timeout checker... Hopefully this will shine a light on things!
21:17COCKROACH
COCKROACHAnother infinite loop pops up... wtf is this?
21:14FIXED
FIXEDI think I fixed a nil concatenation
20:58FIXED
FIXEDIssue fixed!
20:58CONFIRMED
CONFIRMEDIndeed that's it!
20:57SOLVED
SOLVEDI think I found the issue
20:55DEBUG
DEBUGI've set a Time-Out feature, which may hopefully provide me some answers..... :-/
20:53COCKROACH
COCKROACHNOPE! Nothing happened!
20:52TEST
TESTAnd now to test this "fix"
20:52DONE
DONESome last minute shopping
18:56INVESTIGATION
INVESTIGATIONMy investigation does show the parser is responsible for the infinite loops, though.... And I even think I fixed this....
18:55FAILURE
FAILUREI'd only wish the wasn't an auto-report system to Microsoft.... MicroSoft has nothing to do with this matter, so they'd better butt out!
18:54INVESTIGATION
INVESTIGATIONI'm investigating the cause of the loop
15:48BUG
BUGInfinite loops are always a pretty nasty thing to deal with, as there is no telling what the responsible factor is... So further investigation will need to be done.
15:47FIXED
FIXEDEric That issue's been fixed however somehow an infinite loop now appears....
15:24DEBUG
DEBUGSo I added a temporary line to SASKIA to sort this out, as the claim given by the error is NOT possible!
15:23INVESTIGATION
INVESTIGATIONI really need to get to the bottom of this
12:15FIXED
FIXEDCode typo
12:05NIL
NILhas been expanded with 'full assert' to force traceback, as this is getting on my nerves!
12:04BUG
BUGNil for Trim parameters
11:46FIXED
FIXED#10 should be fixed, but more trouble is on the way now!
11:32FIXED
FIXEDAnd that should fix #10 (I hope).
11:31LINK
LINKThis link has now been established
11:27SASKIA
SASKIAFortunately I already designed SASKIA to be able to read from both JCR and real file system or whatever file system you can think of as long as you write a proper kind of driver for that.
11:27SOLVED
SOLVEDThat solves the mystery
11:27NOTE
NOTEI realize now that I did no tyet properly attach SASKIA to JCR6, so it's now trying to find SASKIA scripts in the real file system....
11:17INVESTIGATION
INVESTIGATIONTime to investigate #10
11:17OFFTOPIC
OFFTOPIC
0:09STATUS
STATUSSee ya later!
0:09BACKUP
BACKUPrunning
0:09STATUS
STATUSNo time for that now
0:08BUG
0:03SOLVED
SOLVEDFOUND IT (I think!)
- = 29 Jul 2019 = -
23:58STUPIDITY
STUPIDITYI read the error message wrong... Still this is not how it should be!
23:52COCKROACH
COCKROACHClass Kthura still 'nil'... for some reason...
23:50SOLVED
SOLVEDI think I solved it... That boolean expression did look faulty...
23:45MYSTERY
MYSTERYThis is the second time a class is declared "nil" without any form of reason...
21:58FIXED
FIXEDForgotten )
21:56SASKIA
SASKIAFired her up, and I expect TONS of bugs!
21:44DONE
DONEAziella Great! I've killed what was beautiful code, and dirty code straight from hell (ruining all rules of programming even my own) seems to work... TERRIBLE!
21:29MYSTERY
MYSTERYIt's getting stranger....
21:28MYSTERY
MYSTERYLet's try a few things.... Whatever is happening here... It should not be possible....
21:22MYSTERY
MYSTERYNow let's see if I get this straight... Class CL_SASKIA is nil, while doing a request from CL_SASKIA is actually running.... WTF is going on here?
21:20LINK
LINKI've linked the SASKIA cycler to the Update callback in the field... Now things can get to work... (I hope).
20:03FONT
FONTCoolvetica 20 has been linked to the BoxText routine as standard font
19:56DONE
DONEA little reorderning of code... Would be very important to do before the BoxText routine kicks in!
17:54STATUS
STATUSAll crashes accounted for!
17:52FIXED
FIXEDFlow error
17:51CONFIRMED
CONFIRMED
17:50FIXED
FIXEDI think I fixed the damn scope error
12:30CLOSED
12:30FIXED
11:42BUG
11:12HUH
HUHlocal local?
11:09FIXED
FIXEDAnd that should take care of all parse error crap
11:06FIXED
FIXEDParse error :(
11:04FIXED
FIXEDI think I fixed this.... (I hope)....
11:01SOLVED
SOLVEDAha... hahaha... I think I got it :P
10:59HUH
HUHA strange error, of which I cannot fully tell if this is another bug or still the same one refusing to be fixed.
10:55FIXED
FIXEDAnd another parse error killed
10:52FIXED
FIXEDThis SHOULD fix it
10:49STUDY
STUDYYup, and NOW I found it... Now I've added an extra parameter in the classes tracker, so it can see that it's a group.... This does not yet fix the issue, but I wanna see if this is being registered!
10:45STUDY
STUDYAnd hopefully I can study this now at last!
10:45FIXED
FIXEDI fixed that now
10:44STUPIDITY
STUPIDITYMerya Ah... dupe vars are the reason behind the nonsensical data
10:38FAILURE
FAILUREHow can I fix this, if Lua refuses me to create data that makes sense?
10:38HUH
HUHNil?
10:35STUDY
STUDYlet's set this out more properly as this is getting more and more vague
10:32STUDY
STUDYSo let's try it again!
10:32FIXED
FIXEDA few issues in setting this study material up
9:49STUDY
STUDYSome more study
9:49FAILURE
FAILUREThat did not shine a light
9:43STUDY
STUDYLet's see what I can do to make sure I can rule groups out here... :-/
9:36SOLVED
SOLVEDAha... Now I see... The parser didn't understand the difference between a group and a class, and as the "." wasn't used, it threw an error... That should be fixable, though...
9:32COCKROACH
COCKROACHAnd now it's just playing dumb on me
9:30FIXED
FIXEDForgotten commas
9:29FIXED
FIXEDSome function misdefinitions
9:27FIXED
FIXEDWell THAT is fixed now
9:26STUPIDITY
STUPIDITYThat syntax would NEVER work, Jeroen! Neither in NIL nor in Lua
9:23DONE
DONEI refuse to call this fixed, but at least this should prevent trouble (for now).
9:23BUG
BUGI see private classes are still bugged (was to be expected, but still)
9:19FAILURE
FAILUREVAGUE error
9:19TEST
TESTA test
- = 28 Jul 2019 = -
23:52STATUS
STATUSBut for now I'm too tired... I cannot think clearly anymore, so it's better if I call it!
23:51LINK
LINKI've set a link to the BoxText library and the game. This has not yet been tested, and it must be very fragile as a result. I will have to set this out properly later
23:15GENERATION
GENERATIONNew Anyway.nil file generated
21:52LINK
LINKAnd a link established to the 'scenario' library, which will only be used in the BoxText routine (at least for now, as a few sub-events may also use this)
21:51NIL
NILSkeleton for BoxText
21:32DONE
DONEI've converted the scenario library into NIL format and I've made it extensible for future engines
20:04TODO
TODODernor Spicing my chicken for my dinner tonight
18:59STATUS
STATUSI'm taking a break now
18:59BACKUP
BACKUPRunning
18:58NOTE
NOTE(Of course since I don't have to set up any scenario any more, except for testing for typos, things are a bit easier on me).
18:57STATUS
STATUSOf course I wasted an entire day on such an imbecile thing, but at least it works now... Next step will be the BoxText script, which will also be one hell of a job....
18:49FIXED
FIXEDGOTCHA!!!! Idiots
18:48TEST
TESTSo here's that test!
18:48STATUS
STATUSThis should now be fixed, but I need to make another test to be 100% sure
18:47FAILURE
FAILURELeave it the guys at MicroSCHOFT (not a typo, just look up the Dutch word "schoft") to make simple actions into a mess!
18:33INVESTIGATION
INVESTIGATIONI did deliberately place Brendor out of the prison walls to see if he'd appear, and he does.... So what is clear is that the objects are (for some reason) drawn in the wrong order... This would imply dominance maps being ignored, somehow
18:31DEBUG
DEBUGHARSH TEST!
18:28INVESTIGATION
INVESTIGATIONThe textures ARE being loaded... The debug round did confirm that one!
18:25DEBUG
DEBUGHopefully this debug line can provide me some answers, as I'm really getting clueless now...
18:23COCKROACH
COCKROACHThe crasher is NOT activated, meaning the textures in question ARE LOADED. But what goes wrong then?
18:20DONE
DONEIn order to make sure I've made sure the game will crash out. I've done this by using delegates to make sure the EDITOR will not crash on things like these.
18:19INVESTIGATION
INVESTIGATIONMy guess is something goes wrong with loading picture bundles
17:51CONFIRMED
CONFIRMEDIndeed, the objects are loaded... Question is why they do not appear... :-/
17:47FIXED
FIXEDI guess I've to eat more fish... If it wasn't so revolting and expensive!
17:46STUPIDITY
STUPIDITYI KNEW that whatever it was, it had to be stupid!
17:44COCKROACH
COCKROACHNIL VALUE!!! Not possible unless faulty script has been produced by the underlying API (which should in turn also not be possible, but let's check)
17:38STATUS
STATUSIf this game ever gets finished it'd be a disaster, eh?
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112