Riiiiight!

Well?

Another Dupe

Dupe

Let's see now then

Basis script

Autoscroll activation

Let's see

A few project adaptions will be in order I'm afraid

OCAL

Crash, but the crash confirms what I wanted to have confirmed, and that is good!

again (please note scrolling and visibility things have not yet been set, so the output will, even when everything is the way it should be, odd... as a matter of fact, if it shows things the way they should be in the end, we got a bug, actually).

Compiling

I've forced the API to kill the old map before loading the new, as it appears all stuff is merged.... This will not only inevitably lead to Out of Memory errors, but also to conflicts with data with objects going through each other

Now things get even stranger.... The music of the Yaqirpa loads

I need to make another test, but I do expect the same result

and that music will be 'Opening Theme C' by Kevin McLeod

Music has been set

Old script

Some data returned even seems to point to the map already loaded

The logs say the Yaqirpa is being loaded... yet what I see is DEFINITELY NOT the Yaqirpa

Idiot!

Link issue

Yeah, thanks to the NON-call back structure this cosmetic thing that DOES make the game better was possible

"Loading"

"LOADING!"

The scheduler should now be able to take it

To make #8 possible I've made the link command refer to the scheduler, however the scheduling engine will if I test now throw an error

#8

However that will be done later, I'm afraid!

The next stop here will be the actual appearance in the Yaqirpa

And NOW it works

Take XXXVIII

Did or did I not forget to run barf?

Take XXXVII

I fixed that

API linked to wrong function

Take XXXVI

A few small edges?

Take XXXV

Static/non-static conflict

Kill (Take XXXIV)

Kill Link code

Kill (Take XXXIII)

Kill compile

Kill

Kill

Kill

Ah, there is no Kill link yet.... That will have to be taken care of

Take XXXII

Code typo

Take XXXI

I think I fixed the "Kill" crash, but I cannot be sure

Illegal function call

Take XXX

So I added an extra debug line that must explain why this still happens

Analysis shows this should NOT be possible with this configuration

Keeps going in reverse

Take XXIX

For the short term I can better void it

I really need to sort out the optional parameters, as it appears to be completely bugged

It works now, but backwards, and I need to find out why

Forgot to compile in my hurry

Take XXVIII

That was an error in my C++ code, which must btw also be present in my C# code, but since I never needed that functionality in Dyrt (and especially not in the editor) I guess it never surfaced

I think I tackled that little bugger

Setting ignored

Take XXVII

Well just to make sure then

Was the barf not run?

Take XXVI

Code Typo

Take XXV

But that could be is because I forgot to modify "NotMovingThan0" prior to beaming

They do turn into the "beam" sprite, however they don't animate

Take XXIV

These fixes should fix the "beam" visual effect being ignored

That only fixes the crash I got, but there's more not in order!

Link typo

WORTHLESS!

Take XXIII

Two more of those

Take XXII

A static cannot call non-static without calling an instance

Game still crashes, though

The transporter sound starts, and that is an important marker

Take XXI

Windows was doing something, blocking the C++ linker

Hold the show... C++ Whines

Take XX

Recompiling

Just copied the definition in the C++ API

This is REALLY getting annoying

Take XIX

.....

Take XVIII

I hope!

Cockroaches.... fresh cockroaches.... over here!

Take XVII

Does that make it work?

WTF?

Take XVI

I don't wanna talk about it

Take XV

Idiocy

Take XIV

Extension error

At least it's now whining about the mapscript

Some things are to be done... No matter how much ya don't want it.

Take XIII

This is getting on my nerves

Take XII (again, as the take announced before never took place, at all)

Real life stuff got in my way

Take XII

Okay now?

CODE REMOVAL IGNORED!!!!

Take XI

Something is definitely wrong here!

Take X

USE YOUR EYES! DORK!

Fix ignored

Take IX

I hope I did it right, this time!

If you fix something do it right! Dork!

Take VIII

Core Arf

Take VII

Another syntax error

Take VI

Syntax error

Void

Take V

Can I void that?

Lies

Take IV

Code order

Take III

Another

Take II

Declaration Syntax Error

And then we can commence test take I

That is the most important action every single day, folks!

Making coffee

And now I'm first gonna take a quick shower

A few last minute errors

That should do it!

And the linker has been written

Next step, the link-up code

The mapscript has no access to it yet though... Well strictly speaking it has, but it's quite a hassle to work with.

The class to handle all this has been set up

That covers the C++ part

API adapted

Now for Apollo

Now this might be one of the few times (if not the only time) you see multiple targets beam out in once, still I think making the beaming script a bit dynamic could still be a good idea.

This is important! Otherwise Kthura would automatically always set the frames to 0 automatically, killing the beam effect

Yeah, NotInMotionThen0 can also be read... ;)

NotInMotionThen0 in actors can now be set

Now in order to make the transporter thing possible I think I may need to dive a bit more into the core of Kthura

I've converted the teleport into a jpbf

No crashes so I must assume it to be working

All I can test now is if the game starts up at all...

And scripted it to load the beam sound

Audio included in start-up loader

I will put this as a standard sound effect in the main loader... This sound is gonna be used many many times in the game after all.

The "beam" sound

Since the beaming effect is gonna take place a lot... wel technically in all dungeons, I think it's best if I script that in the main field flow... I am still a bit wondering about the best method

The feature would be added soon afterward anyway ;)

I see I did work with one useless texture in order to ensure a few blocked spaces. The objects in question were supposed to be invisible anyway. I must really laugh about this now, as it makes me realize how primitive Kthura was back then. Don't get me wrong, it was already hard work to make Kthura able to do what it did back then. Zones were back then not supported

Layered Yaqirpa

Yaqirpa textures

Running

Up-to-date ... i think

Like I said, transporting will be a later thing

That work snow

Take XIV (take XII and XIII were not mentioned due to the confusion I got myself in)

Is it fixed now?

What happened now is beyond me

At least I hope so!

And now this issue should be fixed

Still a crash, but the error message at least confirms the issue I was going for is fixed...

Take XI

Forcefully voiding an issue... I really need to sort out why optional parameters randomly refuse to work

Take X

GRRR!

Take IX

Adapted

I think I voided this issue

Case solved and this one is not very easy to get fixed

Take VIII

Expanded info a bit

And I now need to find out why

The scheduled actions are however not being executed

I can at least confirm at the request to perform that script is scheduled, or at least the scheduling function has been called

Take VII

Moar debug lines will have to confirm that the scheduler is working

Extra line to make sure the transport function is being called

The logs show that the waiting for moving actors is not to blame... that turns off as soon as all three actors arrive at their destinations

Take VI