Take V

Debugging impossible, but let's at least put on some markers which hopefully tell me more

.NET error

Take IV

Forgotten link

Take III

Build Failure

Take II

Definition errors

And That's what I'm gonna test first right now!

Important note!

The boss fight is skipped for now, as I do first want to test if the True Abyss is actually being unlocked or not

Basis Boss Script

Beyond Infinity

I will NOT start with the True Abyss right away.... That is really something for later!

The True Abyss

up module

A Lua Script (written as a string in the core of BUBBLE) has been adapted to be able to contact this crap

I've done a few adaptions to the core of bubble for configuration purposes...

All is fine now.... But now I need to find a good way to get "The True Abyss" unlocked, and that ain't gonna be easy

Take VIII

Curse error

#144

Blast

Take VII

Loading error

Take VI

ANother... GRRR!

Take V

Time for the next take, but the news comes soon.... Oh crap!

Woof.... I'm full!

Before I continue.... first my dinner

Another Arena Syntax Error

Take IV

Dir error

Take III

Arena Syntax Error

Take II

Missing Arena Link in Map

Take I

Project update due to new graphic contributor

The boss is not yet there.... This comes later if all else works the way it should....

Abyss

Enemies for Abyss set

Alien

U.F.O.

Pinky

Art Pinky

Art Alien

Art UFO

All as well for now....

Take XXXIII should confirm this

With that everything should be in order for the next stage of this place.... Random treasures

Exit floor 10 not working

Dominance conflict

All I can do is run a test, and if I can make it to level 10, I must assume all is fine

This is the kind of bug though of which you never know it's fixed, unless the evidence is shown that it's not

I hope this will prevent the no-exit bug

Take XXXII

Extra data

For some reason it appears possible a level is generated without an exit

Take XXXI

Untagged plasmas

Take XXX

Script Error

Take XXIX

I think?????

The long shows MINUS widths and heights..... Kthura can't understand such things (for obvious reasons)

Take XXVIII

Compile error in NALA discovered and fixed

Take XXVII

Script error

Take XXVI

Operation Tiled Zone

Awake now

And I gotta find some sleep as I am dead tired now

Exits can better be replaced with TiledAreas so I can ZA_Enter them

Take XXV

More detail on debug, so hopefully I can see a few things can may be able to go wrong

However the loose platform bug is as horrible as I feared as it can (and did) cause unreachable exits

That takes care of a few dupe issues

Take XXIV

Duped

BREAK!

Take XXIII

False generations will not lead to extra bottom textures

And a little order movement... perhaps that helps

Forcing tagmap rebuild and let's see if that does add the exit, which didn't pop up in the tag list (for some silly reason).

Exit coordinates not right

There are still some issues though... BIG issues

That seemed to be it... indeed

Take XXII

I do not know if that was the main issue, but it's fixed now, anyway (which had to happen anyway)

No ref to the file yet made

Take XXI

Hopefully this makes a bit clearer, or at least as clear as they can be in this bizarre situation

Spawn error chatcher expanded

And now the log doesn't make sense

Take XX

A debug line must gimme a bit of clarity on a few matteres

The error thrown by .NET is useless as it doesn't give me the right pinpoin data... At least I do know it goes wrong in .NET and thus inside the generator itself (but that was given the situation also not otherwise possible)

Take XIX

Compile and

Linked that to the generator internally

That Also links this to game itself in the process

part done

C# part done

Right!!!! The exit texture had to be configurable

Let's see!

The generator itself has been done.... Well sort of as I have NO IDEA AT ALL if it works.....

The harder part is now to arrive.... The actual generation

Cool! Still a lot to do, but now the stage has been set to actually get into the creation of the generator itself (which will already be pretty hard.... I think)

Take XVII

Forgot the texture attachment

Take XVI

I've added the routine that will add the bottom parts of the platforms.... Since the start plate will be added along with the other plates the generator will add, this should be perfectly safe for the start plate and also later the finish plate

Not there yet.... FAR from it!

An NOW stuff works the way it should in this stage of the project

Take XV

Let's see if Alpha is the evil here

Take XIV

NOTHING in the code justifies what I see, so I need an extra debug line to get more clarity

This was however not the issue, as I could only check layer 001 in game (002 came up when checking in Kthura)....

Bad dominance in layer 002

The blockmap output confirms everything to be right, however I do not see the starting platforms... This could be a visibility error (which I doubt, as I explicity set it) or a dominance issue with the background plasma... The latter is not unlikely

If it goes wrong now.... Extra debug code could be required, I think

Take XIII

Bad Operator

Take XII

Compilation failure for NALA (C# code typo)

Take XI

Bad formula causes bad start position

Take X

Wrong field

Take IX

Start exit spot not tied to starting position of starting plate

Take VIII

Fixed that stupid issue

Haha, I forgot to set the texture for the plates..... What an idiot I am

Take VII NEXT!

Yeah, it was that trivial

Malformed C-string format query

Clearly the system not understand how to generate the layer tag

Forgot to update method to new situation

Take VI

Map Linkups

Take V

Illegal class call in field linker

Take IV

Fixed Tag errors in Kthura map itself

The game starts, but I'm NOT there yet

Take III

Linker code typos

Take II

And that is the first bug fixed

Did that now anyway

Forgot to link the generator to the API list in NALA

Take I

It goes without saying that all tests coming now require a rebuild of NALA, so I won't note that all the time

Connected to Generator

LinkScript for MapScripts

From this point there is no telling if it will work..... I do first need to link the map, though, so let's get onto that....

Link code

Basis of the map generator has been set up... That is, all it does at the present time is generate the start plate.... Nothing more.... And some cosmetic things also need to be done there.... But at least I can now link this to NIL, giving me the possibility to make the first test runs

And it goes without saying that once the gnerator is about to be put to the test, I will have to recompile NALA all the time

I do require some rest before the actual generator will be made

With that the pre-work is most of all done....

Cleaner

Max sizes set

All VERRRRY important, you know

Link code also available

Size config possible now

Textures for top and bottom configured

More config possible now

This is still only to make configuration possible

Part done for the Kthura Map Generator

And from here the actual work can start

The original texture was designed for TeddyBear, and since TeddyBear is a tile based map engine, this was easy..... Kthura being an object based editor, didn't seem like a good idea to me, and hence the way it's been done now

I had to "break" up the original Abyss platform texture....

The automated Plasma reconfiguration has been done

Music Link Up

Empty script... Will very likely remain that way until the boss has been implemented

Again!

Syntax error

Trying to enter the Abyss now WILL crash the game!

Small test

Linking everyhing together

Reading the notes should now unlock the Abyss

Hub to Abyss

The note in which the Abyss is mentioned is put in the secret lab (which you can only enter after the city has been deserted)

Before I can truly start on the Abyss, I first need to work a small thing out in Gagolton

The rest will be done some other time!

I've Attached this to the starting ground of the Abyss (since that part never changes anyway)

And I need to generate a new plasma animation

A black line I don't has been removed, though

A quick check turned out that the basic animation works.... As I expected this turned out too big, but that is another issue, and easy to optimize

As this is memory and diskspace consuming, I may have to go for some data reduction.... This is a later concern though.....

Generating plasma animation... Or at least, that's my intention, as I am not 100% sure

Voiding (not fixing as the bug was never there) this issue....