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:30 | FUCKYOU | WTF is going on here? |
17:26 | FIXED | Well At least I fixed that... :-/ |
17:24 | FUCKYOU | Can a forgotten ) really cause an infinite loop crashing many programs? |
17:23 | SITE | Added tag FUCKYOU |
17:19 | FAILURE | WTF is going on here? |
17:15 | TEST | And again! |
17:14 | POWERSHELL | On da case! |
17:14 | STUPIDITY | I must (of course) not forget to recompile NALA first |
17:13 | DEBUG | Temporarily deactivated the SASKIA script |
17:12 | DEBUG | I've also made an in-field command for that. |
17:11 | STATUS | My 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:05 | LINK | Wrote the NIL link code |
16:18 | VISUALSTUDIO | Kthura Meta Data manipulation routines written |
13:31 | TODO | Give my brain some rest before I begin on the BoxText routine |
13:31 | CLOSED | |
13:31 | REMOVED | All debug lines from SASKIA as they can spook up when being used in other people's projects |
13:27 | FIXED | According to the data I now see in the debug log, all SASKIA bugs should be accounted for... |
13:20 | TEST | And let's see what we get next! |
13:20 | DEBUG | And the debug line is now formed accordingly... I hope! |
13:20 | STUDY | In order to get well into this debugging, I did a bit of study! |
13:08 | EXPERIMENT | Well, let's try this in stead then.... :-/ |
13:02 | FAILURE | WTF is happening... |
13:01 | MYSTERY | Something makes NALA take too much memory, but whatever it is that causes it.... Who knows.... |
12:56 | TEST | Well let's test this again, to see if stuff works now.... |
12:09 | FAILURE | Now I did get a crash message from GIMP, but I wonder if that was the source of all "evil" |
12:09 | FAILURE | Something's wrong here... Everything froze |
12:05 | DEBUG | let's gather some info here... :-/ |
11:58 | CONFIRMED | The counter value the debugger returns confirms this! |
11:58 | TECHNO | My hunch appears confirmed... Two sessions get into the memory in stead of one! |
11:55 | DEBUG | Let's do this to find out or rule out |
11:52 | SOLVED | Ah 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:51 | SOLVED | 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:48 | EXPERIMENT | Or maybe..... |
11:47 | MYSTERY | The clue is, everything works the way it should except for the fact that no results are produced... Can you still follow? |
11:41 | DEBUG | More debugging lines as things do get stranger and stranger.... |
11:38 | DONE | A little break, and boy I needed that! |
9:49 | COCKROACH | Clearly... NOT! |
9:46 | DEBUG | I've added a debug line to the boxtext linker... This line will indicateif the boxtext initiator was called at all! |
9:44 | DEBUG | MOAR debug stuff to get to the bottom of this.... Are all commands skipped, or simply never executed? |
9:33 | FIXED | Arrays in Lua are based on 1 ... not 0 |
9:32 | FIXED | Fixed the SASKIA script... I think.... |
9:30 | TEST | Let's test! |
9:29 | FIXED | I think I fixed this now.... |
9:27 | STUPIDITY | STRONT! |
9:25 | DEBUG | Some more lines added to get some answers.... |
9:23 | ANALYSIS | the data generate rule out the possibility of this error... Further investigation is required, I guess... |
9:17 | REMOVED | And I removed an older no longer needed debug line. |
9:17 | DEBUG | Let's see what this extra debug line will do |
8:01 | MYSTERY | And now it seems its sees the parameter, but deems it.... empty???? |
8:00 | DONE | Asserted added due to another crash |
7:55 | FIXED | Session parameter missing |
7:53 | DONE | Whitelines will now be ignored... completely! |
7:52 | COCKROACH | and once again WHITELINES are at evil |
7:50 | DEBUG | An extra debug line's been added in order to investigate that one! |
7:50 | COCKROACH | Instruction is ""? |
7:41 | NOTE | But in my defense I must note that I couldn't test SASKIA until the moment it would see action |
7:41 | STUPIDITY | BOZO! 'ins' is a class, not a string variable... Add the field .command to it... |
7:38 | STATUS | Getting somewhere, but it's not yet enough |
7:35 | MYSTERY | is "true" as bugged as "nil"? |
7:33 | SOLVED | I think I found the reason why this is happening! |
7:32 | CONFIRMED | Yes, the cycle does NOT allow the script to be executed, as I suspected.... The question now is.... WHY! |
7:31 | TODO | |
7:30 | DEBUG | A temp debug line to investigate #12 |
- = 30 Jul 2019 = - | ||
23:19 | ACHIEVEMENT | Grim Reaper |
23:14 | GITHUB | issued as #12 |
23:11 | BUG | I 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:08 | FIXED | Function so () |
23:07 | DEBUG | Added FLOW command, as I don't trust things at the moment.... |
23:05 | CONFIRMED | |
23:04 | FIXED | Case Error? |
23:04 | FIXED | Fixed the label issue |
23:02 | SOLVED | Ah... stupid... I didn't include the start label yet, as I was supposed to add it later, and I forgot its earlier omission |
22:46 | DEBUG | MOAR debugging crap! |
22:43 | DEBUG | I've added an extra line that should answer a few questions |
22:40 | BUG | |
22:32 | DONE | I've set another thing for a new stack, and I hope that fixes something :-/ |
22:29 | FIXED | I think I fixed it |
22:28 | BUG | But the label parser is completely bogus... |
22:28 | BUG | On-Load label not found |
22:21 | 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:18 | FIXED | I added one, and that should fix things! |
22:18 | SOLVED | No incrementor? |
22:16 | NOTE | For some reason the traceback doesn't show! |
22:07 | FIXED | |
22:07 | STUPIDITY | Wrong class call |
21:41 | OFFTOPIC | I know BAD PUN! |
21:40 | FIXED | More missing "self awareness" issues |
21:39 | FIXED | A missing "self" issue in the datetime library |
21:38 | CONFIRMED | Now 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:35 | DEBUG | I've put on a few time-out error enforcers to find out where the infinite loop could be |
21:32 | DONE | I've set up a quick datetime routine and a timeout checker... Hopefully this will shine a light on things! |
21:17 | COCKROACH | Another infinite loop pops up... wtf is this? |
21:14 | FIXED | I think I fixed a nil concatenation |
20:58 | FIXED | Issue fixed! |
20:58 | CONFIRMED | Indeed that's it! |
20:57 | SOLVED | I think I found the issue |
20:55 | DEBUG | I've set a Time-Out feature, which may hopefully provide me some answers..... :-/ |
20:53 | COCKROACH | NOPE! Nothing happened! |
20:52 | TEST | And now to test this "fix" |
20:52 | DONE | Some last minute shopping |
18:56 | INVESTIGATION | My investigation does show the parser is responsible for the infinite loops, though.... And I even think I fixed this.... |
18:55 | FAILURE | I'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:54 | INVESTIGATION | I'm investigating the cause of the loop |
15:48 | BUG | Infinite 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:47 | FIXED | That issue's been fixed however somehow an infinite loop now appears.... |
15:24 | DEBUG | So I added a temporary line to SASKIA to sort this out, as the claim given by the error is NOT possible! |
15:23 | INVESTIGATION | I really need to get to the bottom of this |
12:15 | FIXED | Code typo |
12:05 | NIL | has been expanded with 'full assert' to force traceback, as this is getting on my nerves! |
12:04 | BUG | Nil for Trim parameters |
11:46 | FIXED | #10 should be fixed, but more trouble is on the way now! |
11:32 | FIXED | And that should fix #10 (I hope). |
11:31 | LINK | This link has now been established |
11:27 | SASKIA | Fortunately 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:27 | SOLVED | That solves the mystery |
11:27 | NOTE | I 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:17 | INVESTIGATION | Time to investigate #10 |
11:17 | OFFTOPIC | |
0:09 | STATUS | See ya later! |
0:09 | BACKUP | running |
0:09 | STATUS | No time for that now |
0:08 | BUG | |
0:03 | SOLVED | FOUND IT (I think!) |
- = 29 Jul 2019 = - | ||
23:58 | STUPIDITY | I read the error message wrong... Still this is not how it should be! |
23:52 | COCKROACH | Class Kthura still 'nil'... for some reason... |
23:50 | SOLVED | I think I solved it... That boolean expression did look faulty... |
23:45 | MYSTERY | This is the second time a class is declared "nil" without any form of reason... |
21:58 | FIXED | Forgotten ) |
21:56 | SASKIA | Fired her up, and I expect TONS of bugs! |
21:44 | DONE | 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:29 | MYSTERY | It's getting stranger.... |
21:28 | MYSTERY | Let's try a few things.... Whatever is happening here... It should not be possible.... |
21:22 | MYSTERY | Now 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:20 | LINK | I've linked the SASKIA cycler to the Update callback in the field... Now things can get to work... (I hope). |
20:03 | FONT | Coolvetica 20 has been linked to the BoxText routine as standard font |
19:56 | DONE | A little reorderning of code... Would be very important to do before the BoxText routine kicks in! |
17:54 | STATUS | All crashes accounted for! |
17:52 | FIXED | Flow error |
17:51 | CONFIRMED | |
17:50 | FIXED | I think I fixed the damn scope error |
12:30 | CLOSED | |
12:30 | FIXED | |
11:42 | BUG | |
11:12 | HUH | local local? |
11:09 | FIXED | And that should take care of all parse error crap |
11:06 | FIXED | Parse error :( |
11:04 | FIXED | I think I fixed this.... (I hope).... |
11:01 | SOLVED | Aha... hahaha... I think I got it :P |
10:59 | HUH | A strange error, of which I cannot fully tell if this is another bug or still the same one refusing to be fixed. |
10:55 | FIXED | And another parse error killed |
10:52 | FIXED | This SHOULD fix it |
10:49 | STUDY | Yup, 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:45 | STUDY | And hopefully I can study this now at last! |
10:45 | FIXED | I fixed that now |
10:44 | STUPIDITY | Ah... dupe vars are the reason behind the nonsensical data |
10:38 | FAILURE | How can I fix this, if Lua refuses me to create data that makes sense? |
10:38 | HUH | Nil? |
10:35 | STUDY | let's set this out more properly as this is getting more and more vague |
10:32 | STUDY | So let's try it again! |
10:32 | FIXED | A few issues in setting this study material up |
9:49 | STUDY | Some more study |
9:49 | FAILURE | That did not shine a light |
9:43 | STUDY | Let's see what I can do to make sure I can rule groups out here... :-/ |
9:36 | SOLVED | Aha... 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:32 | COCKROACH | And now it's just playing dumb on me |
9:30 | FIXED | Forgotten commas |
9:29 | FIXED | Some function misdefinitions |
9:27 | FIXED | Well THAT is fixed now |
9:26 | STUPIDITY | That syntax would NEVER work, Jeroen! Neither in NIL nor in Lua |
9:23 | DONE | I refuse to call this fixed, but at least this should prevent trouble (for now). |
9:23 | BUG | I see private classes are still bugged (was to be expected, but still) |
9:19 | FAILURE | VAGUE error |
9:19 | TEST | A test |
- = 28 Jul 2019 = - | ||
23:52 | STATUS | But for now I'm too tired... I cannot think clearly anymore, so it's better if I call it! |
23:51 | LINK | I'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:15 | GENERATION | New Anyway.nil file generated |
21:52 | LINK | And 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:51 | NIL | Skeleton for BoxText |
21:32 | DONE | I've converted the scenario library into NIL format and I've made it extensible for future engines |
20:04 | TODO | Spicing my chicken for my dinner tonight |
18:59 | STATUS | I'm taking a break now |
18:59 | BACKUP | Running |
18:58 | 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:57 | STATUS | Of 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:49 | FIXED | GOTCHA!!!! Idiots |
18:48 | TEST | So here's that test! |
18:48 | STATUS | This should now be fixed, but I need to make another test to be 100% sure |
18:47 | FAILURE | Leave it the guys at MicroSCHOFT (not a typo, just look up the Dutch word "schoft") to make simple actions into a mess! |
18:33 | INVESTIGATION | I 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:31 | DEBUG | HARSH TEST! |
18:28 | INVESTIGATION | The textures ARE being loaded... The debug round did confirm that one! |
18:25 | DEBUG | Hopefully this debug line can provide me some answers, as I'm really getting clueless now... |
18:23 | COCKROACH | The crasher is NOT activated, meaning the textures in question ARE LOADED. But what goes wrong then? |
18:20 | DONE | In 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:19 | INVESTIGATION | My guess is something goes wrong with loading picture bundles |
17:51 | CONFIRMED | Indeed, the objects are loaded... Question is why they do not appear... :-/ |
17:47 | FIXED | I guess I've to eat more fish... If it wasn't so revolting and expensive! |
17:46 | STUPIDITY | I KNEW that whatever it was, it had to be stupid! |
17:44 | COCKROACH | NIL 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:38 | STATUS | If 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 |