Don't ask!

Take CMLVII

Link up code... Far from beautiful, but IT WORKS (at least, it should) and that's all that should matter!

compiling

StopWalking API

Take CMLVI

Syntax error x2

Take CMLV

The first required #use clause caused an error due to being missing

Take CMLIV

NewEnemy property

Très bien! That's what I wanted to see

Take CMLIII

Whatever

Take CMLII

Another. How did I manage to do that?

Take CMLI

Wrong operator

Take CML

Other approach

Take CMXLIX

Fuck it

Take CMXLVIII

added some required fields

There was nothing wrong... Silly me

Take CMXLVII

In order to not spook this up any more than I have to let's do this with a different approach

Now I am a bit flabbergasted by the claim that the function I created would not exist

Take CMXLVI

Set up start function (big moment in which little happens, but what happens is vital)

Take CMXLV

Well, in order to resume I need a take to get my persoanl update ... Nothing serious! Just a memory refreshment. Don we all need that sometimes?

FINALLY the error message I wanted to see

Take CMXLIV

Got it?

Take CMXLIII

More lies covered?

Take CMXLII

Syntax error

Take CMXLI

Ah, yeah, that way

Take CMXL

An impossible error message. I need to figure out why this happens. A few more debug lines must guide me here

Take CMXXXIX

C-string format error

Take CMXXXVIII

Missing definition

Take CMXXXVII

Problem voided and I'm very pissed about having to do this

It appears to go wrong sooner than I could possibly imagine

My debug log should tell me more about what's happening now

Take CMXXXVI

The error I get makes no sense... at all!

Take CMXXXV

404 (well the errors don't have numbers here, but you know what I mean) XD

Take CMXXXIV

What I am going to do now may make perfect sense to fellow coders, but if you ain't it won't. I'm deliberately gonna cause errors, but the error messages will tell me if some underlying setups are corect. Yeah, you follow?

A few data errors in this devlog after some saved data was lost due to a reasonless Blue Screen Of Death

All compilation error accounted for... (for now)

Take CMXXXIII

Not gonna mention this

Take CMXXXII

Faulty definition

Take CMXXXI

Syntax error

Take CMXXX

Ah yeah, just copy in all #use clauses, I don't care. It's clear I'm gonna need them all anyway

Take CMXXIX

All I care about now in tests if it this all compiles

Not much I can do today, but a small template has been set up (as I could just copy and adept the template for the field flow. So far the easy part)

Today I have no time at all to work on the game. And especially since the combat engine is the most complicated part of the game which I do NOT want to mess up, I guess it's wiser to leave that for either tomorrow or perhaps tonight, but no sooner than that.

FINALLY the error I wanted to see (namely the error indicating the combat flow scripts do not yet exist), but that is no more concern for today. I'm tired and I need rest now. See ya another time!

Take CMXXVIII

Syntax error

Take CMXXVII

Conflict

Take CMXXVI

Oh well

Take CMXXV

Interfacing case error (luckily these interfacings are part of the core and once they work, they work)

Take CMXXIV

Da fuck?

Take CMXXIII

GRRR!

Take CMXXII

Big fonts

Take CMXXI

Link up code typo

Take CMXX

Now the game should give the combat intro screen, but it should surely crash as soon as the combat itself is to be loaded. For multiple reasons. For starters the combat code itself does not yet exist, duh! Yet another should should do it.

All direct compilation errors accounted for

Take CMXIX

Hmmm

Take CMXVIII

Anything but the kitchen sink

Take CMXVII

Effect for encounter (will be the same as TFT. Is less resource and memory consuming than what I originally had in mind. And perhaps better looking too).

Boss intro tune (although not yet needed, it would be safer to have it present already)

A bug in the encounter editor giving odd values

Link to worlmap works! Good!

Take CMXVI

Fuck it!

Take CMXV

Exit didn't work

Template for combat link up

FINALLY the system tries to call the not yet existent combat routine giving me the error message I wanted to see.

Take CMXIV

I think I must do things differently. I guess Lua had it's original "len" function removed.

Take CMXIII

When interfeacing directly with Lua, case sensitivity is always an issue

I see... what I wanted to see. Good!

Take CMXII

Let's have a look at this

Line! Good one. Well, perhaps, I can do something better than a line

Take CMXI

I think I fixed that

Just as I though.... MaxEnc contains value zero. Now the question is why

Take CMX

Let's find out why the guage bar doesn't appear

At least I've put the gauge a bit higher

Static locals. I really must see to it that that feature gets to work properly, as this is driving me NUTS!

Devlog tool crashed

As I do see a crash caused by the combat starter (not quite the error I expected) I guess the encounters themselves will fire up.

I also need to sort out if that means if the encounters don't start at all

Well the gauge appears... I do need to put it a bit higher on screen but that's only a minor issue. The major issue is why the gauge is empty

Take CMIX

Did I fix the hotspot of the guage?

Well, that void did the trick

Take CMVIII

Tag?

Something happens

Take CMVII

I don't know if this does anything, but I gotta try

Take CMVI

Fucking fuck fuck!

Take CMV

let's fuck up things even further!

How could that happen?

In stead of the countless lines I should see in my debug log, none appear, which means that the routines in question are not called at all.

Take CMIV

Let's fuck in some more logs, shall we?

It's absolutely clear to me that the RENC routine is for some reason still thinking no encounters should take place.... But why?

Nothing appears to happen. Or is that my imagination?

Take CMIII

And that should make the linking complete

The update part has now also been linked

The draw part has been linked now, but that's only part of the work

The debug code has been dummied, as I no longer need it.

Added tag DUMMIED

I do see that the number of foes is properly loaded, but a few things are not in order.... But that was PURE STUPIDITY... I forgot to link the Renc routines to the main flow.

Take CMII

Got it now?

Still no fucking good?

Take CMI

I think I found the little critter

Take CM

More work out here!

Well, the GINIE does at least report 0 for the list of foes. No idea why, so that needs to be sorted out

Take DCCCXCIX

A little check I need to do in the GINIE link up code

Hmm, still no data in the log, which indicates that the foes are not being processed AT ALL.

Now we got ourselves a serious case to solve, my dear Watson.

Take DCCCXCVIII

I've put in an extra line that should tell me how this could happen

Right, just as I thought! The enemies are not properly taken into account, leading to no enemies tied to the map, and thus the rest of the Renc does what it's supposed to do, declaring the entire area enemy-free.

Take DCCCXCVII

Another debug line that should give me more clarity

 Layer FRENDORBUSHES has 35 encounters
Layer __BASE has no encounters!

That's at least the result I wanted to see, but that makes things only more mysterious. But wait there's more to check.

Take DCCCXCVI

Let's first figure out if the number of encounters is loaded properly

A little issue with this devlog

The question is of course WHY

WTF! After all this work NOTHING HAPPENS AT ALL!

Take DCCCXCV

Code typo

Take DCCCXCIV

Property definition error

Take DCCCXCIII

Time now to put to the test wether or not the random encounter routine will respond at all (yes, it will crash... at least when it works the way it's supposed to work it WILL crash!)

All compilation errors accounted for (at last).
Well I only expected this to take time.

Take DCCCXCII

I really need to implement += and -= into Scyndi

Take DCCCXCI

Mistake in varname

Take DCCCXC

Code typo

Take DCCCLXXXIX

Haste makes waste

Take DCCCLXXXVIII

Well let's implement it then

Did I really forget the SUFFIXED function in the Scyndi Core?

Take DCCCLXXXVII

Keyword "and" is not existent in Scyndi (it was in NIL and Neil)

Take DCCCLXXXVI

But more testing for compilation crap is still required

This will at least disable to compiler to generated any errors for non-existent combat linkups. When a combat starts, the game will now DEFINITELY crash due to non-existent content, but for now that's fine... actually even the desired behavior.

A (for now) empty script created for combat linkups

And now we come to the error I was waiting for. The missing of the Combat linkup code

Take DCCCLXXXV

I wonder how many more #use clauses I'll need that Neil never needed XD