Quick swap-up

It sees the scenario tag for a file, in stead of the file.... That's not good, eh?

Take XXI

A few fixes in the BoxText linker

Take XX

Ah yeah, that last word "nil" bug, that I still can't get fixed....

Take XIX

needless comment

Take XVIII

LAURA JCR converted to BUBBLE JCR call

The news came so I had to break this off, but let's resume things now, shall we?

Take XVII

Some calls to harsh system routines that LAURA had, but NALA hasn't and which can only lead to very extremely terrible bugs, so I'm better of without them

Anyway, the main problem is fixed there

Still the computer thought it did.... I must find out why the computer says "out of memory" when the entire notion is out of the question!

That still can't cause an "out of memory" though

I did find a missspelled variable

Still no good....

Added tag MURPHY

And I was hoping to play some more Lands of Lore before the News would begin... Of course, coding NEVER allows such a thing to happen....

Take XVI

I think I found it.... NIL is not yet able to declare and assign a value unless it's constant... Why it came to out of memory in stead of throwing a PROPER error, that's beyond me, though....

Right, it's confirmed the substitutor code is to blame (yet it cannot cause this to happen, so I'm still in the dark here).

Take XV

Ah... This happens during the call to the New Game... Maybe that explains something... yet... this is very very odd

The menu starts, and suddenly I get the "not enough memory" notice.... NOTHING can cause that to happen....

Take XIV

I've no idea what I'm doing... Since the engine refuses to give CORRECT data, I'm completely in the dark here

Take XIII

?

Take XII

Does this do the trick?

Take XI

MOAR parse errors

Take X

Parse error

IX

Linked that to BoxText

New gamevar substitution routine (I forgot about that)

Take VIII

MySplit is not just Split

Take VII

Temporary dummied code I won't need for the time being

Added tag DUMMIED

Take VI

NIL syntax is a bit more restrictive than Lua when it comes to direct table definitions

Take V

I removed a line I though I'd need, but as things went, I realized this line was only faulty.... I only forgot to remove it, this the NIL parser threw an error

Take IV

FOUND IT!

III (although this can't change anything, but actually it can't crash on anything either, so what's happening here?)

For some odd reason a WHITELINE has an unknown identifier.... Odd....

Take II

A forgotten self

Take I

Now I need to put everything to the test, which can be hard as I cannot yet see the text being processed, so I must just guess stuff a little....

And set up a function which should show all this....

Box generation based on the space the text in it needs

I've written a generation script (or rather revived the one I used for TFTREVAMPED and adepted it to NIL, to take full advantage of what NIL can do) that will do the end generation. This is important, as the system cannot know how big the screen is beforehand, so I cannot adept the text to this in my own data files. This script will calculate it all out and make it fully suited with your monitor.
This is not yet fully done, as a few more things need to be done (as some LAURA references may still exist, and since LAURA is no longer being used....)

#21

It's a bit senseless having to re-invent the wheel all the time, so let's see how the TextBoxes are generated in The Fairy Tale REVAMPED!

All's well!

A few mistakes I made when linking this (I was too hasty).

I've now set up an auto-linking feature which allowed the BoxText to always perform the correct background rendering based on the current game situation.

All's well

A quick checkup to make sure everything's right

I've restored the original link to the opening SASKIA script so I can start the opening scenario... The menu screen is not yet relevant, that will come once I get into the actual field gameplay (and when that one comes I'll first get into the savegame routine anyway).

Up-to-date

Running

A bug shown by the screenshot... (the amber box next to the first box) has been fixed

Added tag SCREENSHOT

I REFUSE to call this a "fix"

Well, this is the ugly method, but at least it prevents cosmetic issues

Vertical alignment in text ignored?

Changed the vertical alignment of the points

It WAS the cause of all trouble???? WTF?

Forgotten "end" command... Such a thing should NEVER give an out of memory error under any circumstances... However this means a group is not properly ended... Is that the reason why???

I wonder....

Now I did forget to recompile NALA, and a new feature that's added to TQMG (which NALA uses) is required to make this work... That can however not be reason for an "out of memory" kind of error, but hey, it needs to be done anyway before I can fix anything, so here goes....

That error is NEVER right, but it means that something else went wrong... And what it is.... A needle in a haystack

"Not enough memory"

And used it to display the points

A "DarkText" library created

Some images of Aziëlla are faulty tagged with alternate text "Scyndi".... This will not happen again, but existing occurances cannot be fixed at the present time, and even if I could... It's not worth my time to do so....

Configuration changes to this DevLog!

Although you may initally not see any changes

Well, at least that part works now

A sense of "self"

Illegal object reference

Case error

I see.... I must make sure that NALA crashes out when assets are not found

Comma parse errors that came in this way.

Re-written as small part of code and see what happens

I wonder!

Variable misreference

Code typo

Case error

Easy fix, but still.... It was expected

"tag" unknown... I KNEW it!

I don't know why I'm sure they won't work,though....

I've set up the base model for the combat bars....

Done

Before this can be applied a small study is needed... Nothing serious, as the font will work as normal, but I need to check out some things, first.

Well, font is a great word, but the font engine will use it to show the HP, AP and VITALITY (if appliccable)

All bugs accounted for... Or at least... so it seems....

That stupid thing I do not wish to talk about!

OPLETTEN!

Illegal call to NALA API

I think I fixed it... I just made the way tables are interally called in a crappy way that was bound to crash

As far as I can judge now, all stat parsing is now working the way it should.... This has not yet caused me the end of my total suffering, but at least progress was booked

Another test coming up!

I think that the MaxCopy value was null, and maybe that's what caused this error... I've put in an concstructor in the C# code that must make sure that if not set MaxCopy is just an empty string

So I've set a line that must tell me WHY it thinks that AP has a MaxCopy setting (which it hasn't).

There's bullshit going on about MaxCopy....

Another debug line required I'm afraid (I'm getting tired of this).

But what will happen next?

Case conflicts with the SuperGlobal.VarCommunicate property

I think I fixed the issue at hand, yet I cannot be sure, so another test is in order

Fix confirmed, however another bug yet remains, and that is a pretty odd one too

A calculation notation fault in the underlying C# API that caused SUM and AVG scripts to return 0 always unless the last element has a higher value

A no longer needed debug line

Another debug line to be sure....

Hmmm.... closing in... I think

Unfinished string

More debug lines added so I can (hopefully) pin this down a bit better

Let's test this out now

Furthermore, the max of AP is the same for all characters, however determined by level and chosen difficulty setting

AP is not a stat in Dyrt, but determined by level

Well That has also been fixed now!

GRRRR!

The cause of the cyclic error should now also be fixed

that works

Let's find out!

Does, or doesn't it work?

Recompile NALA

Alright, I've set up a proper error throwing system for this, so if this happens again, a proper error should be immediately thrown, so we cannot keep on stacking up until a stack overflow exception is thrown by .NET

Aha... A cyclic infinite loop eventually leading to a stack overflow.... I can fix that, but first let's build in some protection inside NALA to make sure this cannot happen again, and that a proper error message will be thrown.

Let's check this in VS itself, shall we?

Congratulations, NALA crashes completely!

But lets run another test to have THAT ONE confirmed...

Illegal function call and I do think that is also what causes #20 to happen

Let's see how the stat script looks.... (It's there were it appears to go wrong).

Case issues, but that is not what casues #20 to happen

Let's see who this could happen, as I don't understand it anymore... :-/

#19

#20

Another parse error

Forgotten "end"

I've recoded the SubCollecto generator, and this should fix the issue at hand!

A fix is a fix, but is it THE fix for #18.... Another test will tell me

Not sure if this fixed the issue at hand, but at least one reference to a static that is no static has been fixed

Not completely good, but the error has changed, so the fix took effect.... Pity another bug popped up now

Issued as #18

Which is now fixed

That is of course when you declare it at the wrong spot so it resets all the time

What shows is that the variable 'chklevel' is always 0, even though that should NOT be the case...

Another checkup

I've set in some more anti-whitespace-protection

And they replaced that for me... Good

Bringing my scooter to a repairman as the battery was as good as dead

But I'll have to look into that later....

Which despite all that still refuses to work

At least the corect data is now generated for the parser

I forgot to save.... (oh crap!)

All Lua can make out of this table is {1} WTF?????

Written a slower, yet more accurate routine, to read JCR lines.... Hopefully this will help to get things done properly

MOAR debug crap

Well, the debug data shows indeed that the lines could not be parsed... As a matter of fact, I've NEVER seen such bullshit in debuglines as I did see here today.
Further investigation is now required to find out how this bullcrap could come to be...

I really have to do this... A break down debug line

At least it's been confirmed that the level data itself has been read..... 9009 of code could not have been the outcome by that debugline otherwise...

Another line added to find out more, as I get the feeling something funny's going on here

It looks like the level stats are not even read at all... :-/

let's sort out this non-existent stat....

Another issue

I think I fixed the trouble now....

Parse errors

Moar info then?

Nope.....

As the bug was NOT fixed despite my hopes.... :-/

Let's hope this little enhancement will find me answers

And I think I fixed the bug that bugged me before I went to sleep

I've slept like a baby

Code still bugged, but I really must go to bed now... So that will be for tomorrow.

"nil"

I think I'm just getting tired :-/

MOAR stupidity

Bug in built in NALA line splitter

I fixed it now!

You shouldn't type "==" in C# when you mean "is not".... In C# (and all other C variants) that is "!="

That action != clever!

And let's see what it returns

Now I wanna know what that "script" is, so I added that to the traceback shit!

The errors get stranger and stranger

#16

Trust me, if you have coded with either Lua or NIL long enough you surely want to "end" it all (DRUM FILL!)

Forgotten "end"

MOAR fixing... I think....

I think I fixed the issue

And Let's see if that actually fixes stuff

Recompile NALA

A bug inside NALA