License

Lost Ark

AquaGoblin

Gobling pictures present

Well my Star Story contribution is done for today, and no more details required here

NeilProject/Neil#15

Issue in Neil causing type names in strings to trigger Neil, while they shouldn't

This is the pace where the save spot is located... That being said do I now have a good marking from where the random encounters can be put into place

Area 006 done

The "Star Story" Revising project has not yet begun, but as too much related to that project more than this project appears on this Devlog (where it doesn't belong), I can now say that the Star Story stuff can be found HERE from now on! Good!

Some transfer works for Star Story has begun, so I should really start up a new DevLog now, I suppose!

The basis set up for the Apollo Builder

Please note that the boss will (for now) ignore you!

Neg

Ocean Goblin - Art

Aqua Goblin - Art

Entry points forgotten

I promised myself I do at least one new room to the lost ark, and I fulfilled that promise

the placeholder routines work... The actual true action will now have to be implemented

Compile wise it all works, now for the run-time

More work on Kthura compatibility

My Apollo Engine is now able to handle Kthura's data.... Drawing stuff has not yet been implemented

Oh, in case you care... I got Dijkstra to work in C++, and yeah, it was a challenge to make that happen properly

Today I was most of all transferring Kthura to C++. This took me off my work on Dyrt.... I will soon resume that though... It's just that my C++ work is now taking more of my time, as now stuff gets complicated.

gamejolt/issue-tracker#1414 (Not mine to fix, though

Nala will have to be recompiled as a result

Of course I brought this fix over to the C++ version as well... (duh!)

And in the process I found out why the streched areas were not being animated....

Is being translated to C++ now

Area 003 Lost Ark

She's pretty good!

Apollo is now in a workable state.... My biggest challenges there now are attaching Kthura and Dijkstra to them... Dijkstra most of all I'm concerned about, to be honest, due to the heavily node based nature of Dijkstra, but perhaps I can deal with that... :-/

Yes, I do know it says "FATAL ERROR" but that error is only the result of things not yet being done completely, but as the "Hello World!" message was written in Lua, it could not appear if contact with Lua wasn't established and that shows that stuff is actually working now!

Before I mess any further with Lua though I need to have a few things in order!

For Apollo it's almost time to get Lua on the roll (and then the (Apollo version of the) Blue Screen of Death will also no longer show).

Lua 32/64bit conflict in Apollo

Linkup error

Let's first run a test on the new area in the Lost Ark, though

Well, some preparational work has been done... Wish me luck, as the documentation of Lua is on the C-side of the language still a bit vague

Unbelievable

I've Linked the Lua engine to Apollo.... It doesn't make any calls to Lua yet, but at least I can see that in basics it works... good!

First of all copied the dll into the project... PUC-Rio strongly advices that road, so let's follow suit, eh?

In the Apollo engine the time has now come to get Lua to work... I've never attached Lua to a C++ project, and the other projects I've done this in made it ridiculously easy. Now I have tried this before in a Go remake of Lua, and there it looked a bit awkward, yes, but not that hard.... We'll see....

I'll test them later!

ANother area of the Lost Ark

Extra work for Apollo done

Oh, they fixed MonoGame/ MonoGame#7317

By the time I alreadys set up the most important basis for my own engine, on the point that I'm close to including Lua....

Oh, well...

Well this didn't go the way I wanted it, but at least I GOT something to put text on screen now, and it obviously also appears to be pretty fast too....

If this is the reason why MonoGame has no font support (MonoGame appears to use SDL as well) then it appears the error is 100% SDL not properly set up... That could really put a damper on things, so I hope not!

TTF crashes my game engine in SDL....
No proper error message nor any useful information from the front for C++ error thrower.

Now I had font trouble before in SDL when I tried the Go variant, and the community was about as usefuly (and polite) as the usefull of the information VS2019 provides me...

I've completed my study over font usage for Apollo... This *WILL* make my life significantly better, I tell ya!

And if you thought you'd seen it all

The next step would be allowing fonts... Something NALA couldn't do because of MonoGame being a half-assed product

It all works! YAY!

A big operation in Apollo was done. This was needed as otherwise things would really have gone messy on me in the future....

And a coordinate issue

Some label issues

Area 002 - Lost Ark

All linkups work

A quick is required now... Not that I expect much trouble, but hey, always test, eh?

Link script set up

Zone implemented in Xenor Bushes North to which I can link the entrance script

Base script

I already got this piece, so I only had to hook it up

"The Snow Queen" by Kevin McLeod will be used for this place (just as in the original game).

Entrance done for "The Lost Ark"

Running

Of course, before all else, I'm gonna focus on that dungeon first... Well, as far as my work on Apollo allows it as that is going through the more complicated stage now, but as long as I can combine it.... When the complex part of Apollo is done I should priortize this game a bit more, but I must also mind my own health as things are slowly getting the better of me

I've worked everything out until reaching Xenor Bushes North -- This will be the place were the entrance to the 1st New Game+ only dungeon will be, and I can confirm that the barrier has indeed disappeared, which is wonderful!

Well?

Triple case error

AT LAST!

Let's see now!

Anymore trouble?

Fixed that!

Code order issue

Let's see now then...

Not to mention that I also gave a little bit of a resistance bonus in the New Game+

That'll do

In the New Game+ Eric had to start with all his magic groups activated... That does not happen

And let's go again!

Syntax error

Scope Error

And another take!

Lack of "self"

Let's see...

The first extra dungeon that should open due to this is in Xenor Bushes North and it'll be awhile before I get there....

Hard to check out fully now, but at least I can make sure no bugs occur.

Bonus points due to New Game Plus

Of course, I only have access now to Irravonia's prologue mission, but I can already see if I can set a few things up

Both bugs appear fixed now!

Hopefully!

Should now be fixed

Request to register the failure was set on the wrong spot in the code

Log confirms that the failre is NOT registered.... Why?

Let's see!

I think I tacked the first one completely

An extra debug check on the latter one

And the GJ security blockout also appears to be persistent!

NG+ bonus on travel bonus not right

Again!

Such things NEVER go right in one go, though!

I've put in a temporary "gjfail" variable.... This variable will not be saved, so when GJ fails now, your game will still be valid for GJ in general

I see that when GJ fails to login achievement cause security errors....

A small test will need to be done

That will be Game Jolt's task to fix.... It' very likely a conflict between my system and theirs as a result to their long maintenance, yesterday

That's been taken care of!

I see the travel emblems do not yet respond properly to being NG+

I've done some work on Apollo.... Loads of work and not a single pixel will appear on screen for that YET... But the work was important nonetheless...

I did however make progress in my C++ work, so it's not all that bad!

Was in maintenance today, and due to my reliance on the GJ API, that stops the game development for today....

Confirmed #249 fix

Although i was working on other stuff, but I had to take care of that one quickly (unfortunately).

I think I fixed it!

#249

This looks good

Well, let's see.... :-/

The Script notification I made earlier will help me there

For now, all I can do is start a game up and make sure the system marks this as a New Game+

I've temporarily moved my True Abyss savegames to a different folder... This is to make sure no crazy things will happen to them, as I may need them for more tests later!

And when it comes to Dyrt, I am right now focussing on getting the New Game+ started... Where the test gets hard is is the fact that the game will then start with a lot of scenario, and it *is* potentially hard to test if stuff all works... Of course, this is no excuse not to get things to work, but it will make things harder....

Well other than that I got JCR6 to work in VisualStudio... Due to Microsoft's stunt without any form of compression yet, but that doesn't matter... Compression wasn't my most crucial point anyway, and my experiments for lzma are only planned for the future in C++ already, and if lzma can be set to work then I wouldn't have aimed for zlib anyway

MICROSOFT!!! YOU BLUNDERING IDIOTS!

"Deprecating standard C features"

I've set the field to show you you are in a New Game+ if you are are actually doing so!

I've set up GINIE to work in C++

True Abyss Test Complete

Successfully build myself a Lua library for C++... I should not be happy too early, but with Lua successfully built and some tests in SDL going well, things are going well on the road... That was quite unexpected... C++ and I have NEVER been good friends... so.... I wonder when things go terribly wrong beyond my control...

A lot of reconfiguration has to be done here

Running

None of the open issues in the game though are really suitable to fix in the True Abyss, added with that I also must note, that the (for now) final tests of the Abyss draw near... I think I can better focus on that test first when it comes to this game

So a redo in C++ is becoming realistic now... I guess...

Added tag C++

It appears the Apollo project has failed in C#, this most of all due to that fucking MonoGame not functioning the way it should and its developers not yet responding to my outcry for help...

Now don't question my patience... I got a very very big project on the line because of this, and I must move on... On this moment I'm digging through documentation written by LazyFoo about SDL2 for C++ in VisualStudio and so far I like what I'm reading... If implementing Lua will go just as easy, as well as implementing my JCR6 library (which I already have), that I got good hope that translating Kthura to C++ won't tax me at all... C++ seems to provide most I need to make Kthura run smoothly except for a garbage collector, but even that can be taken care of smoothly, as I already got a few ideas to make that happen... I just need to make a few steps back here...

Why did VS2019 only allow up to .NET 3.1 while I did ask up to 4.8?

I THINK I fixed it though....

Even more huh, the screenshot got out of my clipboard, so all data I need is lost!

Crash upon using a banana

#35

IT WORKS!

Let's see now!

">" != "<"

Cancelling itself works, but there are issues with the coordinates

II

Case error

Let's see....

The button has been scripted

If you get how much trouble that one just to get an "X" on the screen, it's downright depressing!

IT'S THERE!

Take IV

Reference issue

Take III

Siiiiiiiiiiiiiigh!

Code typo

Take II

Fixed that

Class config error

I've set the script to show the icon.... Clicking it won't do any good yet, though

Some real life stuff in my way

GOOD IDEA!!!! NOT!!!

Close Icon for #35

Well, I've checked if NALA (based on the old MonoGame templates that I no longer seem to be able to use for some silly reason) DOES work in VS2019... If worst comes to worst I can still take NALA as my basis, strip it completely to all Bubble references and sources and use that as my basis for the Apollo Basic Game Engine and RPG engine.... It's not the road I wish to travel though, but it's better than nothing.... I always wonder why stuff like this always happens... It wastes tons of my valuable time... It does show however why I rely so much on my own engines as much as possible... Then I got all trouble in my own hands... 3rd party stuff is always a disaster for some reason.... (But unfortunately something we cannot do without).... :-/

Okay, let's make the guys at MonoGame themselves sort this out as I'm out of clues now: MonoGame/ MonoGame#7317

Whatever I try MonoGame keeps failing

A lot is going wrong though.... But then again.... Stuff never went right on me in this stage of things.... Needless complication is an issue, I suppose

The NALA engine was completely developed with VisualStudio 2017. I've now installed VS2019, and for now I'll focus on that when it comes to the development of Apollo... The CLI version of Apollo is nearly completed, and appears to work well in VS2019... MonoGame is acting up on me, so I had to re-install it and was even forced to move to VS2019 that way...

The script can access that now properly

I've taken care of the ID process... Important

Is the void fixed now?

I thought I did

I dunno what happened but I voided it

Take VII

I had a few other things to take care of before I could resume the action

Which reminds me it was for good reasons I made another run here

Blockmap issue floor 65

Lightning works now! Whooohooo!

Take VI

infinite loop

Take V

Pure idiocy

Take IV

Syntax Error

Take III

Identifier trouble

Take II

Linked the spellani to the abilities in question

HOLD THE SHOW! I forgot something important!

And I'll take a few extra True Abyss Levels in the process...

Needs to be tested first of course

Lightning

A few mirror effects

Yeah, those updates can be really terrible sometimes

Paint.net outdated

(About time too)

Jukebox was outdated.... So I regenerated that

Audio Thunder Clap

Expanding some file support

Now since the Star Story redo may be the first game that will be developed with the Apollo engine, I guess I should start that Devlog already.... hahahaha!

I'm working now on a new engine called Apollo.... Yes... Unfortunately it will replace NALA and the underlying Bubble system... It was to be expected that Dyrt would expose some nasty things requiring me to start anew... Oh well....

Added tag APOLLO