Take MMMCCCLXXIX

Yeah, you can't fix what ain't broken!

I hope!

Take MMMCCCLXXVIII

Sys

Take MMMCCCLXXVII

Crash on ace of space. The reason is non-existent. How do I know? Because if there was only the tiniest sliver of truth in there, the other suits would have crashed the game as well.

Take MMMCCCLXXVI

I guess something more was required

Take MMMCCCLXXV

Confusion will be marked on the fighters, however no actual effect will take place. That comes later!

Stuff compiles... And that has to do (for now).

Take MMMCCCLXXIV

Scope error

Take MMMCCCLXXIII

This WILL not be possible to test right away, except for the question if it compiles or not. Once it does, I can prepare for the test step later.

Confusion AI

Take MMMCCCLXXII

Taken care of some business, that I need to take care of!

Taken a shower

Take MMMCCCLXXI

Good Morning!

Take MMMCCCLXX

I am up to the point of reaching the Hawk when it comes to testing the Hard Mode. I always hate testing that, but as I do want to please the no life games (as far as they can be pleased) as well, I need to go on.

Dinner. Eating is also part of the job.

Take MMMCCCLXIX

Taken care of other business I had to take care of!

Take MMMCCCLXVIII

Configration error in the boss fight in the Dark Caves Of Shillington

Take MMMCCCLXVII

In the mean time I have to keep testing and fixing

First alpha build

AT LAST!!

Take MMMCCCLXVI

The savegame analysis now give me the correct data

Take MMMCCCLXV

Wait a minute I think I found the source of evil

Take MMMCCCLXIV

Let's force things a little, then

Savegame analysis also explicity state the boolean that had to block this out is "False"

A line that will have to log whether I'm stepping off the transpad

I needed two takes in order to invalidate the bug earlier.

Not effective, eh?

Take MMMCCCLXIII

Take MMMCCCLXII

Older savegames on a transpad will still suffer on loading, but as the issues "fixes itself" after a faulty instance, these savegames are completely safe and shouldn't affect any later transportations.

Take MMMCCCLXI

Let's throw in a small test

Take MMMCCCLX

Now I accidentally turned it to the Dutch localisation. Oh well, since I speak Dutch, I guess it will work on me,anyway.

Suddenly it appears to be working

Take MMMCCCLIX

Only the first goes well... I don't know why it stops from there.

Take MMMCCCLVIII

Audio.Stop -> Audio.StopChannel

Take MMMCCCLVII

Now I'll cheat my way through the Hard Mode. All that matters to me is that it works. All else is the player's concern.

If it's a hard game you want, a hard game you'll get!

Done!

Now it *is* time to get onto the test of the hard mode, but before I get onto that... Let's make sure the vocals for John Lovejoy are transferred (I waited with that in order NOT to annoy myself).

It appears to be working!

Take MMMCCCLVI

One last typo

Take MMMCCCLV

Code done!

I guess now the less fun part comes! Cleaning up.

Yes! I got it to work! (I only tested the title screen, but that is for now, good enough!)

Take MMMCCCLIV

Several fixes.

Let's use AppImage's bug against it, so the image ends up in the correct dir by default

Take MMMCCCLIII

AppImage sees fit to dump its output in the current directory and worse, it doesn't seem to have an alternate output switch

Wrong exe called

+x

Nope, but that was not entirely unexpected. This will really take time to sort out.

BUT... does it work?

Well, I'll be... An AppImage *is* created...

Take MMMCCCLII

Ah, that was a mistake in the project, and had nothing to do with the builder itself.

Take MMMCCCLI

Why isn't the icon copied?

Take MMMCCCL

No "Type" in the .desktop file

Take MMMCCCXLIX

Now for the actual go!

It.... compiles ...

Take MMMCCCXLVIII

Illegal C function call

Take MMMCCCXLVII

Syntax error

Take MMMCCCXLVI

The Actual AppImage Creation

Will the test is running I'll look up where the AppImage builder is... I don't remember were I put it! Silly, huh?

Take MMMCCCXLV

Generator for AppRun

Take MMMCCCXLIV

There was even a compile error... sheesh!

Take MMMCCCXLIII

Why does the old work pop up while stuff was fixed?

Take MMMCCCXLII

And x attribute wasn't added

Copied in the Windows exe in stead of the Linux exe

Take MMMCCCXLI

Take MMMCCCXL

Bad mounting

Take MMMCCCXXXIX

Sigh!

Take MMMCCCXXXVIII

Path issues

Take MMMCCCXXXVII

Mount point not created

Take MMMCCCXXXVI

Several

Take MMMCCCXXXV

;

Take MMMCCCXXXIV

Illegal function call

Take MMMCCCXXXIII

Declaration syntax error

Take MMMCCCXXXII

"Tr"

Take MMMCCCXXXI

;

Take MMMCCCXXX

Case sensitivity. One of the big reasons why I hate C and nearly all of its variants

Take MMMCCCXXIX

This WILL force me to unmout a lot of crap or my RAM won't be able to take it all.. Ow well!

Well, actual copying has started.

Take MMMCCCXXVIII

Manifest category (mostly "game" given the prime purpose of SCI, but hey, ya never know, eh?)

Take MMMCCCXXVII

Will ask for Icon

Right.... Well the first thing I'll need the builder to be able to is to write a manifest. The content of this manifest can differ per project, so come extra configuration is in order.

Take MMMCCCXXVI

Did I (once again) forget to recompile my C++ code?

Made "Basic Linux" optional (it's pretty useless actually and once .AppImages work, you can consider that feature "deprecated").

Stuff appears to work now!

Take MMMCCCXXV

What is that?

Take MMMCCCXXIV

I think

Take MMMCCCXXIII

Why does it try to use the target name as the original?

Take MMMCCCXXII

Debug line placed wrong

Take MMMCCCXXI

Take MMMCCCXX

;

Take MMMCCCXIX

404

Take MMMCCCXVIII

More crap

Take MMMCCCXVII

Whine!

Take MMMCCCXVI

Huh, it compiled all the time and suddenly a syntax error pops up

Take MMMCCCXV

More precise debug

Skipping code

Take MMMCCCXIV

Alias fuck

Take MMMCCCXIII

Why the debug translations of the Scyndi Scripts?

Take MMMCCCXII

?

Asking for a folder that doesn't exist without any proper reason, either!

Take MMMCCCXI

False fuck

Take MMMCCCX

Ah.... Separate JCR6 files -> segfault! Let's ignore that for now.

While I'm at it, I might as well configure the release anyway, eh?

While I have to wait for the current operation I've already cleaned up my release folder. I will keep the latest Apollo version for awhile (ya never know), but I need to have the SCI version in its own folder to make sure no conflicts arise.

Although I must be 100% sure that all Kthura Maps are properly compiled in release versions of the game, I will for now dummy the line that does so, for obvious reasons. (Compiling Kthura levels is a slow process and I cannot wait for that at every test).

I removed .git from the backup

Although I did not yet compile I had to see if at least my OLD stuff will at least run the builder the way it should. Well, it LOOKS like that's the case!

Take MMMCCCIX

A quick shell script to get things on the move!

Now all the builder can do as far as .AppImage is concerned as ask a few important configuration questions.

Downside is that the .git folder gets backed up as well, but that's easy to get rid of!

Quick backup before starting. This should not be that dangerous, but I need to be 100% sure!

Oh yeah, did I note that setting up a VM allowing me to make Windows compilations failed. The trouble is that SCI has evolved during the production of Star Story and needs features the current Windows version of SCI doesn't support. If worst comes to works I may need to compile them on a different PC, but I hope it won't ever come to THAT point.

Once the automated created of .AppImage works, I think it will be best if I still focus on the test of the Hard Mode first.

And I fear FlatPak won't be any better in THAT regard.

Now things are a bit complicated here, since I create my games on an ExFAT device, and ExFAT does not support SymLinks and .appimage requires those. Of course, I can still rely on RAM drives, so I guess I have to use those.

Why not flatpak? Well, because I have not yet been successful figuring flatpak out. I hope I can support flatpak as well.

Now before I move on, I'm going to set up things that will make the SCI builder able to create .APPIMAGE files of games.

Take MMMCCCVIII

I had a little break

Take MMMCCCVII

Now I wonder how that floor got there in the first place. Oh well, I removed it and that should solve the problem!

Kthura managed to do this... but then again.... Kthura maps build prior to fixing, were only bound to show this behavior... but still.

isn't it frustrating how fixing one bug creates another.

Take MMMCCCVI

In the meantime I can test some more. Long live alarm clocks, eh?

Boiling two eggs now

BETTER!

Take MMMCCCV

Conflict on status resistantance percentages