That explains

Case error....

Oh no???

Another test is in order, of course!

Referrence to GALE (which wasn't used here) removed

Syntax Error

And another emergency ride to the restroom, I'm afraid (I hate it when that happens on a moment like this! Well, I hate it anyway, but ESPECIALLY on a moment like this!)

This will also allow me to see if the XDraw method works properly, but it should as Kthura heavily relies on the same code as on which the underlying API was written

That is the "arrows", or whatever you call these things as they are a bit oddly shaped.... The icons used for identification and such are not yet drawn

The pointers should appear at their respective positions....

I've set up the position calculator of the gauge pointers

Linked pointers into the time gauge code (not used yet, though)....

Yeah, that was the work of haste, and haste makes waste... or so they say....

Foe pointer loaded twice... hero pointer not loaded at all

As far as I can judge right now, everything appears to be in order now....

Well.... Let's see what'll happen now!

Nou ja.... poep gebeurt, zullen we maar zeggen!

Then let's run my compilation script AGAIN!

Well, I guess recompilation is in order then.... if you want it so badly.....

I though I DID recompile NALA.... But NALA itself appears to have a different opinion.... Oh odd

HMMMMMM!

And I must go to the restroom.... emergency.... :(

I first need to make a quick test to see if XDraw does its job PROPERLY

And I've studied my old code... The code itself is not usable, however, the mathemetical formulas used in it are, so that SHOULD be fairly easy.... (But what should and what is, are two different things, actually).

I've set a few things up to get this show on the road

time for some coffee

Had my breakfast

My baguette's ready, so time to eat!

Well I'll be.... I see the YouTube videos I posted before, which were wrongly linked now show the correct linkups.... So the guys at Google did fix this....

Wait until its ready!

My baguette is in the oven now

So, Jeroen, what are you still doing here! Get your ass moving into the kitchen, you lazy dork!

Yes, English folks, for a Dutch that is already a very extended breakfast.... Loads of people even skip it completely, you know!

And eat

And then I can put on cheese and ham on that

Put in my baguette in my oven so I can have breakfast soon....

neither alpha nor beta are useful now, although alpha might be mentioned a few times already, but at least their config is in order now ;)

Will have to do

Dummy

Test new icon and config

Icon added :P

#2

Sleeping is important too, you know.... When I sleep I can save up energy for a new coding session :-P

Well that's it.... for now... If you don't mind... Aside from developing games, I also PLAY games, so I'm gonna waste some of my time on Septerra Core :)

That tag will not be used for the time being, but I guess I had to make it exist, eh?

Added tag BETA

At this moment no alpha testers are planned and based on my current experiences with alpha testing... It's likely not gonna happen this time

Added tag ALPHA

Secret download updated

Oh, alright!

I guess I must add an icon for bitbucket

Updated

Added tag BITBUCKET

Updated

Running

This will likely be for tomorrow though, as I'm getting tired and I'm getting more and more trouble to focus

Like I said I now must study my old code in order not to reinvent the wheel.... What I need to sort out is how I did the coordinates on the time gauge...

And the debug bar shows the data I wanted to see

All parse errors accounted for

Take IV

Invalid definition

Take III

Function call typo

Take II

Invalid declaration

Take I

For now all I can test is if no crashes occur and if the debug console shows the data I want to see.... Since I'm dealing with random values this is not entirely easy, but overall this should work

As I've no visual effect yet, I did add some debug lines here

I've set up the routine that will determine the start positions on the gauge

I guess I've come to a point that I must NOT re-invent the wheel... So some study of the original game will be required now... But I now realize I did also forgot to set the base positions on the gauge, so that must come first....

Not that you'll see anything (yet)

Hotspot Point Hero

Hotspot Point Foe

This Does of course require me to rebuild NALA

Not much of an issue now (as the builder is still bugged on this point), but later on this can be VITAL

Foldering error

I've linked XDraw into Bubble in order to make sure I can do some stuff that comes with the gauge more properly

Well it doesn't really matter, does it?

Once again YouTube screwed it, as that was ONCE AGAIN NOT the video I linked to... This one is

It APPEARS to be working now.... Damn... that took some sweet time

Take V

(told you so!)

Conflict due to lacking self

Take IV

Voided the NIL issue about negative numbers

(I just KNEW it would take more takes... I already said it, you'd be surprised what can all go wrong in such a process!)

Take III

Accept request done

Take II (GRRR!)

Cleaned that up!

BULLSHIT!

Well, I gotta test if this work... The gauge only appears.... The fighters do NOT yet appear on it.... But you'd be surprised how much can go wrong in this process... Take I and hopefully the only take!

Damn... I feel terrible

I've linked that to the main draw routine

A base for the gauge draw function

I know I did not as much as I should have today, but allow me some rest... I've been working hard enough yesterday and the combat engine is already hard enough the way it is....

WTF... Paint threw me an error, while I did never even start that program up.... Ghosts!

I guess YouTube is a bit bugged today, as that was NOT the video I was linking to... Oh well

So let's run my little scrippie

I guess I did not recompile this

I've the coordinates it has to move to

Yes, this will cause it to be invisible for being out of the screen borders, and was deliberate so I can make it "scroll in"

I've set the Gauge at Y -500

Trouble is that it's impossible to test at the present time if this all works

I've updated the TQMG library for automated hotspot support.... The time gauge can really benefit from this

Extra backup is running now

Nothing odd here.... With the way VS works, pluse how much my VS frameworks are still in development with the complete engines, this was only bound to happen, and then you gotta update everything someday

TQMG repository

And I really need to find time to continue development on NJCR... By the time this project is finished I probably won't be needing it anymore XD

Tricky Units

I know it won't compile, don't even try it! This doesn't have priority right now!

Bubble/MonoGame

Okay That is jpbubble/Bubble_CLI#1 -- My bad!

jpbubble/CLI#1

Bubble Build Respository

Bubble Lib Repository

StripExt (I needed that)

Okay, everything appears to be working

Take II

I was too quick

Idiot!

I need to see now if the game still starts up... if it does... everything is most likely fine!

I've set the intro routine to load the gauge icons as well... It was just easier to do

Let's enjoy a good song also, eh?

And today I hope I can make a start on getting the time gauge to work, which may not be easy, but ya never know... I've done this before, so I hope I still remember how I did it before :P

making myself some baguettes with cheese and ham for breakfast....

So far... Gonna call it... mesa tired

Oh yeah, I made a secret alias... but that will come down to spoilers :P

Hey, they had to be done anyway, and this way I can't forget about them anymore... XD

Gauge Icon Shanda

Gauge Icon Scyndi

Gauge Icon Rebecca

Gauge Icon Merya

Gauge Icon Dernor

Gauge Icon Brendor

Gauge Icon Aziëlla

Gauge Icon Eric

Although the order of speed has been determined, this says NOTHING about the starting positions on the start bar, which can be over the entire startbar... of course, when in pre-emptive strike all heroes will have a huge advantage over the enemies (and always have a big head start then) and in ambush the enemy will have this advantage.

How the battle goes on after that will be the same in all situations.

Enrollments for pre-emptive strkes and ambushes.... Please note that in the easy mode you'll never get ambushed, and in the hard mode you'll never get a pre-emptive strike....

There is still a chance factor deciding on how high your travel level is compared to the dungeon's travel level. If yours is higher than the levels, then the chance for ambushes decreases and for pre-emptive strikes will increase (if applicable for the chosen difficulty).

They too will be added to the pre-menu loader, for the same reasons

Time Pointers

As the combat gauge will be one of the most used assets, even though it's only in battle I did place it in the pre-main menu loading sequence in order to shorten the loading times later in the game

Time gauge itself

Irravonia's combat gauge icons

Yeah, I had that luck...XD

BETTER!

I need the luck that 2 enemies appear though

Let's see how that looks

Adepted the calculation

When there are multiple enemies they are needlessly close to each other, so I need to do some recalculating here

It works!

Take XI

I think....

Take X

Let's see....

Extra fuck!

Take IX

CRAP!

Take VIII

More information, as the impossible was claimed

Take VII to see what will happen now...

Ah... just a mistake in the error message

Type 0?

Take VI

Or rather return

Illegal property call

Take V

Lacking sense of self

An onto take IV

Fixing a crash in the process

Regenerated ANYWAY

Take III

Malformed #accept line

Take II

Knudde!

Take I

Calculator linked to combat start up

Aha... I see that Godot is not offering C# support.... That could be nice to give it a try, but not for the short term, but hey, I know they support it, and that's cool ;)

Gauge speed calculator.... Contrary to the first version of the game, this will just base itself on who is quickest and who is slowest, making an order, and not a direct agility to setup as the original game had.

RPG Data linked in Hero Compiler

Wow... It works... IN ONE GO!

OF course, what SHOULD BE and what IS, are two different things, so let's get rocking

Take I

Foes SHOULD now be drawn

various

Linked those spots to the ingame Foe End Compiler

Spot generator did work when it came to the calculation of coordinates, but did not create the actual spots

#66

I've added the call to my FoeCompiler in my building script

Time for a break, though!

Shouldn't be too hard, but I've seen simpler things causing cockroaches

The next step will be to make sure the enemies actually appear

It appears that NIL takes all "ground scopes" of the main script and all scripts in imports through "#use" as one big scope, and that was how the false "dupe identifier" errors were thrown.... Not sure what I can do about it, but it's good to know nonetheless...

It appears I'm correct

Take XVI to see if I'm correct

I wonder....

Anyway as far as I can judge at this specific moment everything looks like it's in order...