Code typo

Take XXVIII

I've done a different approach, but I got alternative features ready. I will need to see what happens next!

The code renders this impossible, so where in the world this goes wrong..... Joost mag het weten!

I really need to put a scroller in my log system.....

This does shine a light on things... The data is stored in the item exit points, but not in the item objects themselves.....

Take XXVII

Actors will be voided from any further tests

the tester appears alleric to actors, but that is not really a concern

Take XXVI

More crap

Take XXV

Let's get this into the main crap then

Take XXIV

Let's see

This is not really possible.... The previous error did prove a string was succesfully received

A complete crash?

Take XXIII

Illegal function return

Take XXII

Fuck you!

Take XXI

Glue code typo

Take XX

Debug script expanded

Compiling

Put in Neil Glue

Put in API

Debug property added

The lie is complete.... Under no circumstances could the data produced by the logs be what they pretend to be.... I really need to sort this one out!

Take XIX

Extra debug - This must confirm the lie completely

Take XVIII

Glue isse

Take XVII

Should only confirm the computer is lying though

Ah, a small debug issue.....

Take XVI

Let's try a different approach here!

So the object is NOT properly tagged.... yet the clickable engine finds it, and so does TagMapper (the game would function at all if it didn't), so that result is a lie... Question is... Why does this happen?

Take XV

That doesn't fix this cockroach, but should at least allow me to debug

Neil glue missing a member

???

Take XIV

let's see... MOAR data required

The log shows that the data is empty indeed... Not possible since an earlier scan already proved it to be full.... so wtf happened here?

Take XIII

An extra debug line added, as I cannot yet rule out that the Item object itself is to blame (shouldn't be, but hey, nothing is certain now)

I take that as a fix ignored

Take XII (that does not yet fix the 'overstocking' but at least I can see if the 'nameless item' bug is fixed or not)

Another stupid error?

The next lie also comes in.... An item without a tagname

I heard the buzzer so that should indicate an overstocking, which is with empty inventories impossible, so what that happens needs to be sorted out, but first I need to see if this initial issue is fixed or not!

Non-existent members fixed?

Take XI

Perhaps this should do it!

Indeed it didn't

Take X

This cannot fix the problem as a whole, as the error itself refers to "nil" and not to a string containing a wrong value, but as crazier things have happened, perhaps I should still give this another go

At least I fixed a part of the problem

The log confirms the lie, but also confirms another issue

Take IX

So now to find out why the lie pops up

Computer lies.... No NIL value can be there

Take VIII

Whatever

Take VII

I hope....

But the issues are not yet solved

No more compilation errors

Take VI

Whiner!

Take V

ANother index error managed to sneak past me!

Take IV

Identifier trouble

Take III

#use error (another one)

Take II

Illegal field index

#use error

Take I

Well, that makes I'm ready to get the test on the roll

should be obvious, but you do need to tell the computer EVERYTHING!

If an item is succesfully picked up it will now also disappear from the map

One more thing to do

That links eveything together

Set up picking up treasure from map

Shorting thing... Really needed to get things done

And now to the actual function I was planning to get done!

Put into the main routine

Not there yet!

Draw Mini Messages

Base class Mini Messages

I will need some other things.... The minimessage system will now have to be put in place

I made sure the routine doesn't work on Briggs.... When walking around in the Yaqirpa this wouldn't be a problemm but in combat the same routine will be used, and then stuff could happen....

Now I can make it possible that items are being picked up

Link code added

A routine which can add items to somebody's personal inventory has now been made

I will remove the support for "key items" in Star Story. Why? Because the system has always been bugged from the start, that's why! And the key you need in the Yaqirpa is also the only key-item you'll ever get... It's just easy to make a quick script handle the key separately... no problem!

I have decided also that before I start on the combat system I'm first going to see if I can link the lzma library into JCR6 in C++. I really hate missing that....

I did need a quick study on the inventory system

From here I can start setting up the inventory system for real, but I'm not sure if it's wise to start on that one tonight....

FINALLY!

Take XXXIX

recompiling

Yup.... The parameter read-out from the scripter was faulty

I get the same values for the x and y check.... I checked the C++ code, and the variables there appear to be in order... that is in the Core of Kthura.... I do need to check the API code still, as C++ can still be where the evil lies

Take XXXVIII (inside visual studio this time)

I'm really mad now, can you tell?

Now a core debug note!

Take XXXVII

I must compile.... AGAIN!

It was a core error so

And fixed it!

I think I found it!

To make things even stranger, the data shown in my log indicates all must be well.... I don't follow....

Take XXXVI

No errors this time

Recompiling

It seems I didn't notice C++ threw me tons of errors

Take XXXV

Glue syntax error

Take XXXIV

Debug command adapted

And that should link it all

COmpiling

glue

API function

Debug function added

Some more debug crap is now definitely in order

Take XXXIII

It is NOT likely, that the script is to blame....

However I'm out of time for now, but this deserves more investigation

The outcome of this test point to a core error in the C++ code of Kthura, and that is pretty serious. A click far away from the savespot yet leading me to the savespot out of the blue even calling the save screen makes a lot clear

Take XXXII

A bit more information on my console please

This shines more light on things... Only ONE item appears to get Wendicka's attention, and if you click any other item Wendicka will ignore them and go to that one item.... In earlier tests this may not have come out because the ONE item was located on a different floor and therefore out of Wendicka's reach... At least that's the most plausible explanation....

Debug take - Take XXXI

This is a bit odd, but as I'm running out of time hard to get things done with now....

The clickable creator does log that the items are clickable, however, when I click them, it does not turn out that way.

Take XXX

I think I fixed that

So I need to find out why

The items do appear on the map, however they are not regarded as clickables

Take XXIX

Done!

Okay now it fell over a different item, but that's merely an asset, but still....

Take XXVIII

I think I fixed stuff.... Some object data was not properly copied... This should be now....

No crashes, but still not yet completely in order... However I do have some ideas why this is, so we can work that one out easily... I think...

Take XXVII

Project file Updated

Patch

Kthura now says it can't find a certain texture, but that's alright, since not all assets have yet been transferred

It appears that way

I think

....

Take XXVI

It looks like it!

Let's see

I hope

On the right way...
But not there yet! Far from it!

Take XXV

I think

But I think I see the "evil", though

This is getting nasty

Take XXIV

Generated new script ifles

I hope I fixed the class mismatch issue now

Take XXIII

No changes, but suddenly it works?

fix ignored

I think I fixed a MyData export issue

Take XXII

Conflict

That fixed it indeed

Take XXI

I think i found the source of all "evil"

Clearly not!

Take XX

Did I forget to save or anything?

Fix ignored

Take XIX

I think?

Texture "nil" not found????? Da fuuuuuck!

Take XVIII

ID was not remapped by Kthura in C++

Take XVII

Let's use some brute force then!

fix ignored!

Take XVI

DA FUUUUUUCK!

Take XV

Remaps

Take XIV

Issue

At indeed looks like to be the case.... Hmmm... Well, I need to sort this out somehow, or maybe it actually *is* for the better this way.... :-/

Take XIII