Although not entirely recovered it looks like things are slowly getting better on me.

Linux total fuck up!

Illness struck me! I was unable to work, today!

Although Rosetta is far from perfect this way, at least I can finish the game's scenario now!

Which is worth a lot at this point!

Take MMMMDCLXXI

fix

Take MMMMDCLXX

Checkup fuckup

Take MMMMDCLXIX

Whine

Take MMMMDCLXVIII

Illegal GINIE call

Take MMMMDCLXVII

return error

Take MMMMDCLXVI

Page addition

Almost there

Quick fixup

Take MMMMDCLXV

Oops! I forgot to link this as a callback

Take MMMMDCLXIV

GRRR!

Take MMMMDCLXIII

Not a very elegant solution, but it should work

Tag in listbox

Take MMMMDCLXII

using

Take MMMMDCLXI

?

Take MMMMDCLX

Namespace

Take MMMMDCLIX

Code typo

Take MMMMDCLVIII

Syntax error

Take MMMMDCLVII

Crap!

Take MMMMDCLVI

Tag creation should now work, and this can be tested

GINIE expansion

Entry creation should now work. I cannot yet test it (as it would affect the game), but I don't think THIS can go wrong (but less likely things have gone wrong today as my log shows).

It works

Take MMMMDCLV

I'm tired

Take MMMMDCLIV

Again!

Take MMMMDCLIII

I'm getting tired! That much is clear!

Take MMMMDCLII

Add Tag requres input plus a selected entry

Take MMMMDCLI

Wrong variable!

Take MMMMDCL

Not . but ->

Take MMMMDCXLIX

Entry requires input

Take MMMMDCXLVIII

A bit lower to have no collision with the mascot

Take MMMMDCXLVII

; x2

Take MMMMDCXLVI

Code typo

Take MMMMDCXLV

Syntax error

Take MMMMDCXLIV

They cannot yet be used. They only exist and will take their set up shapes.

Gadgets added

Pointers created I'll need for the required UI gadgets

Now before I can resume the game development, I do need to add an entry adder and tag adder.

Both should not be that hard to do, but I do still need to work that out.

It *is* possible some scenario files will be empty now, however the slightest modification should fix that automatically now.

Take MMMMDCXLIII

;

Take MMMMDCXLII

Case mismatch

Take MMMMDCXLI

Pic Specific modifications ignored

Take MMMMDCXL

Paging issue?

Take MMMMDCXXXIX

Still a lot not well

Take MMMMDCXXXVIII

Linux config lost with the backup recovery

Doh!

Backup (some things did not go the way they should after all, and some data does appear destroyed)

Take MMMMDCXXXVII

All crap accounted for

Take MMMMDCXXXVI

Another

Take MMMMDCXXXV

Transfer rot

Take MMMMDCXXXIV

Actual data output

The temporary crap that was put in the export (to void any other non-existent SegFaults) does also show in the export files the way it should. Good!

All non-existent fuckups accounted for.

Take MMMMDCXXXIII

No console, so I gotta test in bash too

Take MMMMDCXXXII

Sigh!

Take MMMMDCXXXI

Order of code

Take MMMMDCXXX

More fuckups

Take MMMMDCXXIX

Sigh!

Take MMMMDCXXVIII

Rename

Take MMMMDCXXVII

Well, what will happen next?

Take MMMMDCXXVI

Narrowing down

And not to address the actual issue as car as the read-out of data is concerned.

Here too the clean methods fuck up, so the dirty methods must suffice.

At least the exporter will now just be called and no fuckups for no reason on just calling a function which existed all along.

Take MMMMDCXXV

And once again the REAL DEAL

Take MMMMDCXXIV

Checkup that became obsolete due to the dirty fuck

Take MMMMDCXXIII

At last!

Take MMMMDCXXII

Non-existent errors

Take MMMMDCXXI

Non-existent error

Take MMMMDCXX

When the clean methods than can only work under all circumstances don't work, then the dirty methods that should NEVER be used under any circumstances will have to do.

Take MMMMDCXIX

Well....

Take MMMMDCXVIII

....

Take MMMMDCXVII

Now also a crash on English... I really don't understand anymore (as there's nothing to understand in the first place. It just has to work).

Take MMMMDCXVI

Dummy fault

I need to find out why this fucking fucking happens.

Take MMMMDCXV

Search performed in wrong console tab

English exports, but Dutch gets the claim the exporter doesn't exist (which is impossible. Either they work both, or neither work, so this is odd).

And Linux complains about BUS errors.
The latter is also strange as that too either works on both languages or not at all.

So why this happens is a complete mystery!

Take MMMMDCXIV

Code::Blocks should also save if I prefer "debug" or "release" builds, so system crashes don't get me this much trouble

Take MMMMDCXIII

Well, back to business

failure Thanks to the crash the earlier search has failed as well... I'll try to set that one right later.

More fuckshit!

Take MMMMDCXII

Code::Blocks should SAVE THE FUCKING PROJECT PRIOR TO COMPILING!

Saves me loads of trouble with this high-load of crashes.

Take MMMMDCXI

As a result I do have to recompile the code that I just adapted.

And the system crashed. I should have known.

That's why all times of the past few posts appears the same. (They all got posted after a delay as a result)

And everything slows down for some silly reason

Old debug info that blurs the stuff I need, so I can dummy that.

More code that crash stuff ?????

Stuff in Rosetta appear to get stranger,though.

That was just a cleanup, though.

Tons of needless backslashes from Tutorial scenario

Take MMMMDCX

Now for the REAL take

That was only to see if stuff compiles

Take MMMMDCIX

Outputdir was not properly defined

A few things are slowly getting clear, although, some more workout will be needed.

Take MMMMDCVIII

What I am going to do is DRASTIC. It might actually destroy the compiled scenario data, but never fear, that stuff has been backed up. But if this stops the Segmentation Faults, I do at least know where to go on.

Take MMMMDCVII

I hope this ends the INI.ini issuue

Take MMMMDCVI

Illegal files

Take MMMMDCV

Trying to narrow it down even more

Take MMMMDCIV

Last take again then

I was right, there was nothing wrong! Compiling again proved that.

Take MMMMDCIII

Compiler failure for no reason at all

Take MMMMDCII

Syntax error

Take MMMMDCI

MOAR!

Take MMMMDC

A few null detectors put in

I guess there's a segmentation fault

Take MMMMDXCIX

WTF?

Take MMMMDXCVIII

Nope!

Take MMMMDXCVII

#include

Take MMMMDXCVI

Well?

Take MMMMDXCV

Still no good?

Take MMMMDXCIV

Checking the results

Take MMMMDXCIII

Case issues

Why?

Nothing appears to have happened

Take MMMMDXCII

Now I gotta check the results

Take MMMMDXCI

Now for the true test!