Area 008

Let's put it to the test!

Area 007

Area 006

Yup, that all works now!

Only one way to find out if that's true...

Done! So it should work now! I hope

I guess I didn't link everything

I gotta see what will happen now!

Area 005

Area 004

Dinner was tasty.... I have a bit liftover in the fride.... Microwave ovens are sooo handy

All is well

Test Again!

Forgot chain zones

Quick Test

Area 003

All issues accounted for!

Take XIX

Wind error (this confirms the bug before is fixed as this is a different unrelated kind of error, but it only only be triggerred whe the previous bug was fixed.... Does that make sense?)

Taek XVIII will have to confirm I'm right.... So let's see!

Indeed, the exit spot was too close to a transfer zone on the map, this has been fixed, and that means that the KettingKaart library was already acting the way it should

Elementary my dear, Watson... The logs show TWO layer transfer requests, meaning there's a conflict with the exit spot and the transfer layer

Take XVII

More specification

Take XVI

Fixed it, but I wonder what happened there

How odd... I copy and paste GoToLayer, but it magically turns into SpawnPlayer, skipping the main route, is that the source of all evil?

Now that's rich.... It claims the GoToLayer command wasn't done, yet the error is thrown by the SpawnPlayer function which is in turn called by ... tadaa... the GoToLayer instruction....

Take XV

Let's see what request is being sent (probably one I didn't ask for)

the error message does NOT make sense!

Take XIV

hmmmmmm?

Take XIII

CODE TYPO!!!

Take XII

I've added some quotations to make the debug data more clear and less open for multiple interpretations....

This is getting more and more complex, but I need to dig a little big furhter, as I feel that I am closing in on the solution....

Take XI -- Well, I guess i gotta run this test anyway....

Now this cannot fix all the trouble since the engine had to throw an error on that mistake, and not just ignore stuff, so I wonder......

Data order

Take X

Hopefully This extra debug line can enlighten me

But the error before proves something was happening, so what is going wrong here?

And what happens is... NOTHING!

Take IX

Another one

Take VIII

Illegal function call

Take VII

Fixed that

Request put in wrong Map Script source file....

Ah

Take VI

Syntax error

Let's try this

I first need to do a few real life things, and then I'm gonna investigate why

But the actual chain I created is being ignored....

Take V

Well, dirty code straight from hell should do it then....

SEE ARE AYE PEA!

Take IV

Case error

Take III

Lack of self in library

Take II

Really another #use needed?

Time to start Take I

Meaning that everything is at the ready to start testing stuff now, but this is gonna take some time to get fully right I fear.... Or will complex things take less time than easy things (don't remind me of that nightmare yesterday, night... It still haunts me).....

And I've called this link from the constructor of the Red Dragon Cave's MapScript

The link code has been written, which allows me to link KettingKaart to the mapscript in which I need it

The library itself has been written, but not yet been tested

And that works the way it was intended

All it has is a constructor now, but hey, gotta start somewhere

Field flow must now be able to import this skeleton module

Extra config to my Bubble Builder configuration

I worked this out differently from what I normally do, so I need to test things out more thoroughly and I need to write additional scripting... I gotta note also that I am also obligated to write an extra library for this... I chose to do that, in stead of a mapscript so I can more easily recycle this script in other games as well, even in other duneons....

Area 002 Red Dragon Cave

Well! Catch ya later, folks! I'm tired... Tomorrow is another day, eh?

FINALLY!!!!

Final test.... please?

Missing start characters

All crashes voided

And I am dead tired of these stupid errors now! (the number of reasons why so many tests are needed is ZERO! The fact that I had to use so many tests is really beyond me).

You can't fix what ain't broken, but you can void it

Engine giving me nonsensical errors

.........

Base script for Red Dragon's cave (sigh!)

HOW MUCH MORE FOR A SILLY THING LIKE THIS???

SIGH!

Again!

Forgotten group

Let's roll 'em, boys!

Start room red dragon cave

Respawn re-initiate

Dragon cave tiles (for all four dragons)

I've set the copier to void that

Errors on deleted stuff in original

All the pre-new-map stuff appears to be working

Take II

SASKIA syntax error

But I can test up to that moment, so let's go!

I can put this to the test a little, although the game will crash upon loading the red dragon cave, since that dungeon does not yet exist (how obvious)

Scripted it all out

To Dragon Cave

Sub Hub Dragon Crack Forest

Crack

Ah, white line bug in my way.... If I could only get that fixed..... (GRRRR!)

Syntax error

I've configured Eric's fire spells, since the first dungeon will allow him to unlock those....

Well, ready to go to the next stage

Take IV

Flame Wand didn't work the way it should

Rebecca's scare works

Take III

Illegal class usage

Take II

Bug

Well, as I go into testing area 003, I can test Rebecca's action in the process (I hope)

Personal Actions

I've activated Rebecca's personal action

Rebecca's Personal action button

Sword tier 2 had issues

Let's put things to the test.... (And this may take awhile due to an earlier mistake of mine... Nothing in the programming, rather a gameplay issue during the test play, hahaha!)

That will be the last "official" floor, as the "final" floor will only be a scenario hub to get you into the red dragon cave

Area 003 Dragon Crack Forest

With this, I can move on to the next leg of the game's production

YUP! ALL IS WORKING NOW!!!! WHOOHOOO!

Take X can now really begin!

So I'm ready now....

And I had my dinner... A delicious Asian spring roll

Okay, that was that

And engage into test X... well that is... if if wasn't around 6 and time for the news....

Recompiling NALA

I fixed that

The evil lies in the way the data was generated by the underlying NALA API

Take IX

An extra line must tell me if the reset is completely ignored or not, as it seems very much like it!

Take VIII

Wrong var

Take VII

Let's see what happens if.....

If I can still get some around this time... :-/ (But I hate molded bread)

Before I'm going to take a look why that is, I first need to refill my break stock

The stat isn't properly reset

Almost there... No more crashes, but....

Take VI

Syntax error

take V

Recalc definition error

And into take IV

I voided that

And move on to test II

So I gotta compile this shit all over again

Yup, gotta compile the entire shit all over again as the linking script is embedded in the NALA engine (to save me time)

Code typo in the NIL link code

Take I

I mean it!

I'm gonna need it... I'm afraid!

Time to wish me luck

Older savegames will NOT take effect in this.... Too much trouble to get it right and only asking for bugs

This should recalculate all stats ever re-equipping

So my script can run, as I won't get to full test work anyway

must be recompiled as a result of course

So that should link all together now

NIL link code

API for RPG read out now has a stat iterator for foreach kind of requests

Irravonia not noted as somebody who could equip the Flame Wand

Flame Wand is NOT a consumable, but a weapon!

And I've replaced the light bulp in the hallway of my appartment... Was about time too

It works

And AGAAAAAAAAAAIN!

C-string-format error

And Agaaaaaaaaaaain! (yawn)

Syntax errors bij de vleet

And again!

Another syntax error

Again!

Syntax error

Taken a shower, prior to the test

Let's first see if this works

The stats will NOT yet be recalculated, though.... That will be the next step!

I've made it posible to change equipment now

Yup! That does it! ;)

And NOW I'll go into take III

Case Error!

I found the issue

HOLD IT! HOLD THE SHOW!!!!

Take III

And I added an extra help line hoping it can tell me why

Who can equip stuff is being ignored

Jewels not properly marked

Take II (can you believe that?)

One comma.... ONE FUCKING COMMA!

Let's put that to the test!