Ah!

Of course "TAKE I" as I do not know at all if this even works at all ;)

Once the "New Game" section is fully operational, I can fire the official starting shot as then we can finally get to the game itself

And I've linked that to the "New Game" menu item

Script written that will chain the game to the New Game flow

I've set up the first stage of the New Game script... Please note this stage is nothing more but a welcoming note, but still....

So I made a little API that can at least tell the scripts where the game main package is located, and this way, I just have to make sure that Go application is always located in the same folder

Especially when programs are written in C or C++, one may NEVER assume the directory they are started from, however as I am partly dependent on an external program written in Go, Apollo needs to know the exact location of that program.

Extra icons for this devlog active

"Bye" command

module 255 bug in Neil?

Take V

Syntax error

Take IV

link ending

Egg

Take III

Nope! Nope! Nope! But I got the bugger now!

Take II

I hope I voided this for now

Whatever?

Take I

It's not yet tested, so that will be the next step!

I've set up my debug console interpreter...

Now, to stick with the facts I just rebuild the ARF file

I've linked this now to the Apollo system

Right, deftable has been added

Worked on Neil

Dang!

MUST be... but what is possible and what happens are two different things I see on the background of my screen

Well one strange has should be fixed now

Took me tons of takes to get to the bottom of this and I can't log them all

tons of made up errors

And that concludes THIS part of the story

Right-o

Take XXV

So a bit more was needed

Yet not good enough

better

Take XXIV

More size

Take XXIII

Syntax error

Take XXII

Coordinate fixups

Take XXI

I see now

Take XX

We're getting somewhere now, though

Illegal call

Take XIX

I think?

Non-existent module member?

Take XVIII

I fixed that

Well, it appears that the required parameters did not make it through somehow

Well, the bug is now in the console, but that's another story

And suddenly it works?

Take XVII

Extra data in C++

Things appear to get odd when multiple keys are pressed at once

And compile the entire engine, but hey, maybe we're getting somewhere now? (I hope)

I need to try this

However it reports the stuff like it were keyhits and not keydowns

I undummied the log and now I do see that some progress HAS been made

SIGH!

good

No

STILL

Take XVI

Now, I gotta see then if THIS takes the cake.... :-/

Still no good however

Take XV

Of course, the question is now... Does it work now?

I've dummed the debug line causing the loads of output... If everything works now things should be ok... right?

I've altered the script and I gotta see if this does something

I guess THAT explains.... The names given are completely written out, I see

I've put in some extra debug features to sort that one out!

It appears SDL doesn't understand the keynames I asked about

Take XIV

I need to find out more, so more debug data to the output

NONE of the keys required to activate the console register

Take XIII

I've been adding some extra debug crap to find out what is going on... This will generate a LOT of output, but hopefully it will answer a few questions

Take XII

I'll try to get this done on another way

The system does show we ARE in development mode

Take XI

Behold Crystal McLeen... ;)

Debug features do not appear to work at all (they are ignored)

I need to sort out why

Take X

Font reference?

Take IX

Illegal function definition

Take VIII

I hope

.....

Take VII

Bad loadstate request

Take VI

So there was still one more, eh?

Take V

Unknown identifiers

Take IV

Ah! I found out what cases THAT one!

Illegal instruction?

Take III

That only required me to regenerate a new ARF

Byte was not recognized as type by Neil

Take II

The code compiles....

That issue has been voided, although I have put in a littebit of a not that this should work with GCC as well, as I don't know if Microsoft's alternatives are supported there...

Well I guess it wasa mistake to rely on Microsoft anyway, eh?

and even their own guidelines don't work so it seems....

Another "deprecation" error (read: Microsoft trying to kill C++)

still no good!

Let's compile again to see what happens now

More of those

Forgotten "std::" I hate that namespace

I forgot to check the compiler's error log!

Error: Module Events does not have an element named: KEYBYNAME

Hmm... did I forget to compile or something cheesy like that?

Project file

Oh yeah, I forgot to menton that I also did a quick key recognizer

And I expect tons of trouble

Take I

Main menu linked

It must be noted though that the console is not operational yet..... All it should do is show what's already on it, and allow you to go back by hitting escape

I've set the link to the console

Font transferred from the Bubble MonoGame project... Hey it's a good font, and I don't need to defend myself for the MonoGame crew

Which I will this time entirely write in script

Start to a debug console

Makes transferring stuff also easier

Or at least not my MAIN hard drive....

I simply don't wanna use my harddrive for this....

Preparations for savegames

Unfortunately, due to C++ by far not being as advanced as C#, I cannot support alternate drives, like my C# version of Dirry can

However before I can start on the credentials I'll need 'Dirry' support

The time has come now to prepare for starting a new game... In order to be as compatible as possible with mobile devices, I am not gonna work with keyboard input, so it's all mouse clicks, yes even with entering your Game Jolt Credentials.

It appears to be working now! Yay!

Take II

Several issues

Apparently not

And now to see if it works - Take I

Linked the linksup script to the sub

Made the actual music library

Enabling me to set the music routine up at last

And that should all link it up

Interstate glue code

Intersate APIs

And now i could finally fix some bugs that came in this procoess

The #use directive has been completely configured for use in Apollo

I see that thing go wrong much sooner than that

THe program just ends without a warning... This is a bit terrible as now I do not know what is actually going on

I've tried what will happen when I put the use statement in to get "Anyway" done

I wonder how long the old bug with JCR6 file requirements is gonna haunt me (simply having to recompile stuff, but still annoying)

I've set up the security data generator

But at least I got one notice of an upcoming update

A bit setback now.... NONE of the libraries I tried so far to get http calls done in VS works... One one with the least terrible results produced over 200 error messages. Always funny how unaltered code can work sometimes, eh?

And now it DOES work

Coordinate error

Illegal function call

Did I fix it now?

Guess....

Pretty please!

PLEASE!

Does it work now?

MOAR!

More crap

Another test then....

Yeah, I know I suck

Those were faults in the linkup script

And I even see an error pop up now

None of the menu items WORK yet!

The menu should now appear

why didn't I do so before?

Draw Text API function linked to Neil

And time to get some rest, I reckon

All repositories updated

I cannot completely prevent an FPS loss, but it has become less drastic than it originally was.

AT LAST!

either 1 or 0, even when deliberately set to float

It seems we got ourselves a REAL cockroach here

Moar data required

Well, I guess I gotta sort that out, so I made the scaling and coloring 'var' types, so no manipulation at all can take place

Do numbers only act as integers?

Bug debug (prepare for a VERY low framerate)

That SHOULD be fixed now....

It appears that I made another scoping error?

Wait a minute, I think I solved the mystery

But that line shows the only possible reason happens NOT to be the reason???

The log shows that the entire for-loop is not skipped.... At least, done3 isn't updated... I've added an extra debug line that should be the answer why this happens

more debug needed

NeilProject/Neil#16 -- But that's one to sort out later (should be an easy fix)

I need to know so extra debug lines have been set in place