I will for now test the south exit.... The west exit is a later concern

All should be linked from the start

Xenor Bushes

Both cities will only appear on the worldmap when unlocked, but trying to enter them will crash the game... for now

Xenor

Frendor

The Crossroads have been set up

Well, let's first set up the Crossroads shall we?

Converting Xenor in particular might be a hard job, but I've been in worse situations....

Good morning

Well time to get to work again.... Like I said, the CrossRoads was likely to be the first to be taken care of, so let's go for that...
Now the Cross Roads connects to both Frendor, Xenor, The Xenor Bushes (all three versions) and the Exam ruins.... I will get to those first, and after that the optional dungeon the MadHouse, which will for chapter 2 also be the gateway to the GJ exclusive bonus dungeon..... So let's go!

And so far for today.... The Cross-Roads is likely to be the next location to take care of.....

Yup.... The two locations only appear due to them being unlocked by the Red Dragon... Good!

Take IX will help me here... I hope

Well, the new locations do appear on the world map, yes, but, I need to check one more thing

Take VIII

SASKIA syntax error

Language referrence error

Take VII

Prefix error in map referrence

Take VI then, and let's see what will happen

And I forgot to activate the Red Dragon skill

Illegal script referrence in post boss script

And onto take V

And I voided more stuff later in the script

And that fixes another crash in the process

NEG

That voiding is indeed what it took.... Hmmmm.

Take IV

It does seem that the stuff does NOT work the way it should, at all.....

Take III

Syntax error in API enhancement

Take II

The Script will now unlock these two new locations, providing you defeat the Red Dragon first

Oh welll

I guess I didn't make it, but it was to be expected

Yeah, forgot those too, eh?

Cross Roads

Iskarderiu Forest

Of course it won't work, since I forgot to link the SASKIA script to the map.... Moron!

Take I, and let's see if I can get this fully working this year....

Well 8 minutes before 2020 starts, but I've got something better to do, than to waste my time on that, so....

Ruby

Red Dragon Big Art

I can now define an entire party in one go.... Saves me a lot of trouble

However as soon as the fight begins, the game will crash

Meeting with Red Dragon Scripted

Scenario looks alright!

Now for the grand scenario, peeps!

All's well!

Well.... Let's check

Other spots appear to be doing fine

One more broken exit spot, so it appears

And let's go again!

I manually fixed the map that got broken in the process

No worries now

Oh, wait a minute.... The debug asset library is outdated.... I suppose I need to replace that....

It appears that the "Wind" settings are not right

And that is now to find out! ;)

Area 014 is where the dragon resides, though you can already see it, it won't activate yet and just ignore you.... The scripting of the dragon comes later when the map itself works or is confirmed to work

Area 014

Area 013

Area 012

Time for a little break

That appears to work

Take III

I've lowered the boss' defenses, as this was ridiculous for a mantadory boss fight

Take II

Boss picture name

Take I

This SHOULD all work now... WISH ME LUCK!!!!

Area referrence in SASKIA script

This is nothing more but the "receive room"... A few more rooms will be there before you meet the dragon itself

Area 011

Red Guardian

Boss

That brings us to the last leg of this puzzle.... Linking the solution to the boss enemy and the SASKIA script lines that come next....

WORKS!

Take XIII

Turn around! Bright eyes!

Take XII

Cancel the puzzle

Take XI

Detection Y for mouse pointer was invalid

Take X

Turn around (bright eyes)

Almost there, but not yet quite

Take IX

DA FUUUUUUUUUUUUUUUUCK!

Take VIII

Lost track of things, but A LOT has been fixed

Take VII

Modulo error

Value editing

Take VI

Callback error

Take V

Party bar

Coordinate fine tuning

I've now set the arrows which will be the clicking areas to put the values up and doen

Take VI

Don't laugh!

Draw command without coords...

Take V

Illegal class call

LUL!

Take IV

General fixes

Visual Studio Upgrade

Take III

Case error

The error at least confirmed that the link itself worked! ;)

And another one!

"self" required

Time to put this to the test

And the map itself has now been linked to this SASKIA label

Puzzle link script written

Puzzle access debug console (I'm gonna NEED it)

The rest will have to come later as I am dead tired now

I've set up the basis for the script that will be used so the player can give up the result of the puzzle

No frames here

Illegal function call

Illegal field/method usage

I've linked all items and spells that use the "Sparkle" effect to this SpellAni.... Not sure if it all works the way it is intended, though, so a test is in order

I think this is obvious "SpellAni" means "Spell Animation".... In my earlier RPG only used for spells, but later also for different kind of actions, but the name remained

Sparkle

Added tag SPELLANI

No "Undead" status on Fire Ghost

Crash when Scyndi learns "Cure Disease"

Let's see now!

Several issues

Lack of Self!

Gotta test it all then, I suppose

Config for red dragon cave textures

Template for caves done

Real life business was in my way today

Fire Ghoul, Fire Ghost and Ignis

Since they all live in the lair of the fire dragon, it's easy to guess they'll all absorb fire and be fatally wounded when struck with ice, which you don't have at this point of the game, hahahaha! >:)

Frost Wand

FireBlast

Once again, a lot of time was wasted on debugging so I could not work on the way I wanted to, but at least the main dungeon is done, so I can work on the next step which will be the random encounters, and I am planning to get the healing animation done

NOW all looks good

Well....

The auto-clickable detector has now been set to ignore NPC tags that are suffixed with SPOT, as they are only assistor spots and not clickable ones

Okay, that is also a nice one!

Again!

Old habits die hard (especially when they only go for one dungeon... at least for now!)

And let's test this again!

recompiling

Error in the quicklink NIL library for Kthura in NALA API linkage

Stil I can test if they activate properly (and crash the game, yes) and if the links between the panel room and the main dungeon works well....

The panels should be clickable now, but doing show would crash the game as they have not yet been scripted... And before I will I got other stuff to take care off, such as the encounters

Area 010

All okay now?

Barrier didn't get removed on the Travel Emblem

Case error?

Activated the travel emblem (as this is a disappearing dungeon, I had to do this manually, this time)

All chains work

And Another test bites the dust

Chain Error 007 to 004

And Another test is in order!

Link 001 to 008 not working at all

Dominance issue

Let's see if it all works..... :-/

Area 009

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)