I hope...

Take DCCXIX

I wonder how the tag can be an empty string

Take DCCXVIII

???

Take DCCXVII

Kthura

Take DCCXVI

Kthura calls on an undesirable way

Take DCCXV

A few typos that magically made their way in

Take DCCXIV

I think I voided the issue causing Wendicka, Crystal and Briggs not to move to the transporter pads

Take DCCXIII

MapScript QuickMeta

The source of evil has been found

Take DCCXII

More debug lineup

nil was given for a function referrence. Now THAT's rich!

Take DCCXI

A search for clickables went terribly wrong. I hope I can fix this, otherwise, I'll have to put this into the generator, which I don't want.

Take DCCX

AllowQuitSave will now only throw a debug message, but otherwise be ignored.

Take DCCIX

Prevention caused more than it prevented

Take DCCVIII

Fuck you!

Take DCCVII

Another InterVar link was required for that, though

Take DCCVI

Autoscroll definitions in the old style will only lead to the risk of memory leaks, so a new set up has been done.

Take DCCV

I think I found the source of evil

Take DCCIV

Still not sure what causes this error, but I have set the init routine to do more crap. I hope this will help me a bit

Debugging it twice as hard as writing the code in the first place, as such, when you write your code as cleverly as possible, you are, by default, not clever enough to debug it.

Thanks Kerninghan, for rubbing that one in!

Take DCCIII

It really seems I found the source of all evil now!

Take DCCII

Syntax error

Take DCCI

scope error

Take DCC

More work out to see why the impossible becomes possible

Take DCXCIX

I see that ain't gonna work... sigh

Take DCXCVIII

This is getting really strange as the entire statement is bullcrap. I wonder what the fuck is happening

Take DCXCVII

Hardcore debug

Take DCXCVI

GRRR!

Take DCXCV

I've set CLay to ALWAYS throw an error (and hopefully also dump out a stack trace)

But who know what will happen next?

It appears all compiler issues have been accounted for (for now)

Take DCXCIV

More group bug in Scyndi

Take DCXCIII

FPS -> Sys

Take DCXCII

I guess it turns out that removing the Screen group from my engines was the worst idea I ever had. Tons of code rot is caused by that one, I see.

Take DCXCI

Another gv

Take DCXC

Another void

Take DCLXXXIX

I wonder how much more of those I'll encounter during this quest

gv x2

Group issue

Take DCLXXXVIII

gv

Take DCLXXXVII

GRRR!

Take DCLXXXVI

MCall crap

Take DCLXXXV

State calls

Take DCLXXXIV

More Screen -> Graphics.

Do I have them all covered now?

Take DCLXXXIII

Code typo

Take DCLXXXII

Events

Take DCLXXXI

Screen -> Graphics

Take DCLXXX

JCR7

Take DCLXXIX

Graphics

Take DCLXXVIII

So as long as the compiler won't whine, for the time being, I'm fine!

At the present time this crap only needs to exist, as no actual calls will be done runtime in the upcoming test for the time being.

Once I actually get into the first battles, this code will be important, but no sooner.

Neil -> Scyndi: Combat link up

So after a little break, I guess I'll have to get onto that one.

Request for starting combat done (logical as the Yaqirpa has three scripted battle, including the boss fight), yet the combat linkup module has not yet been converted.

Take DCLXXVII

Loading of Yaqirpa Key

Take DCLXXVI

10x :=

Take DCLXXV

Audio

Take DCLXXIV

Graphics

Take DCLXXIII

Image load

Take DCLXXII

404

Take DCLXXI

RPG2Stat

Take DCLXX

I really need to fix the table type in function definitions. For the short term, let's just void it

Take DCLXIX

Sys

Take DCLXVIII

Neil -> Scyndi: ZA module

Take DCLXVII

Sys

Take DCLXVI

Platform check changed from the way it was done in Apollo from how it's done in SCI

Take DCLXV

InterVar call

Take DCLXIV

Intervar to Yaqirpa Warp

Take DCLXIII

Neil -> Scyndi: Yaqirpa Warp module

Take DCLXII

# -> len

Take DCLXI

I really should make sure compiler directives can be indented in Scyndi, as this is getting annoying!

Take DCLX

There is also a mapscript for the return to the Yaqirpa, but that is a later concern. As long as the player has no access to The Hawk, they can't come back there anyway.

Neil -> Scyndi: Map Script Prologue Yaqirpa

In order to make sure the Kthura bugs I just fixed will not spook up SCI, I had to recompile SCI

That does indeed do the trick, and is safer anyway, as whatever data is now added to Kthura maps, the JQL cheater will always pick it up properly.

Take DCLIX

This definitely needs some checkup, but I think that for the short term I found a better way to cover this

I thought this was merely a stack overflow, but there's more to this. I think stealing files that are part from a block doesn't work well in JQL.

Take DCLVIII

GRRR!

Take DCLVII

Bad config in VS

Take DCLVI

ACS had to be added to the Kitty engine in Jalondi in order to use it again in VisualStudio

Take DCLV

Once again... boom.

Take DCLIV

Jalondi crashed on checking things out, and I don't know why

Let's rebuild this crap, then

Huh?

Take DCLIII

Dir error ???

Take DCLII

Well, let's try this!

Take DCLI

Wait a minute, I think I already got this

A few aliases have been made for the Yaqirpa. When you revisit the place a other mapscript is used, and aliassing the level data (no matter how many files I need to alias) is the safer way to go there.

This will not yet affect the game AT ALL, but the stage in which it will, will come soon enough.

The Map Data Generator will now take the level info from the Kthura file. It'll be faster to parse it that way (and less prone the bugs also).

Well, I'll be. The HEX output's dictionary contains all custom kind names, which heavily implies that this works. Of course, reality can be a bit bothersome here, so let's not cry victory too soon.

Well, let's analyse some HEX output

I made the Kthura compiler run this crap

The music for the Yaqirpa has been completely transferred into the new version of Star Story succesfully.

That produces the right results

I need to re-compile my JCR6_Show tool

The JCR6 resource does show the file... good

Take DCL

The JQL file that should link up all the music should be able to pick this file up now

This technique has, by the way, already been applied in Star Story II and Luna's Father, so it's nothing new, but for Star Story I, it is quite a change

This tune has been copied to this group

The music will be the same as before.... So Opening Theme C by Kevin McLeod (released as public domain) will be the tune for the Yaqirpa. In order to save my disk space, I will group all music together, and link to it with JQL.

As far as I can check now that looks like that's in order

In order to make sure the meta data has been properly transferred (even though it's less needed here) I've retransferred the intro map

Well, a general checkup of the output map is now required, still.

Debug line which is no longer needed

At last!

Take DCXLIX

I see a code typo. I do not know if that was the source of all evil, but it likely was.

Take DCXLVIII

Let's find out more about this fucking fuckshit

The transfer is NOT being completed. Now that's rich!

Take DCXLVII

HARDCORE DEBUG!

Fuck you!

Sigh!

Code typo

And do another transfer

Which will happen by compiling the C++ code

Take DCXLVI

So there WAS an issue in Kthura itself?

Still no good?

First I need to do another transfer of the same map and check if that shows me the data I want to see.

This will, by the way, also require me to set things in order with the Kthura compiler, but that's easy to check.

Ow, wait, it appears to be a bug in the transfer tool. That makes things easier then.

Here things take a stranger turn, as these objects are now saved kindless. That's a clear bug in the Slyvina version of Kthura and requires immediate attention

Now let's see how the objects of strange kinds are doing

The meta data does appear be transferred properly

The Yaqirpa dungeon has been transferred in the process.