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

I looks like ISGET is for some reason making pure Lua calls, while it should be based on Neil.... I need to check this out, though

Did this affect the code? (Take XII)

Stuff taken care off?

Geany is acting up on me a bit....

Fix ignored???

Take XI

A certain local function had to be declared as a global (or interstate data traffic wouldn't be possible)

Take X

Illegal function call

Take IX

Compiling

That should link it all

Neil code

Wrote access to this

Ah, I see

No "data"?

Take VIII

barf

Fixed that

Some connections between script and engine are not in order, I see

Take VII

Fixed that

Yup, it was a bug!

The item spots have all been seen but also all been skipped... Question is if this is coincidence due to the random routine, or if this is actually a bug.... I think the latter, though....

No more crashes, but I need to check the log to see more... I didn't see any items in the field, but due to my limit possibilities at the present time, that's not a very viable source of information

Take VI

Did I void it now?

Take V

So let's force Neil to dump out its translation

Lua insists on an unexpected ) that Neil should never be able to create at that point

Take IV

Some chopping faults neil produces (I think)

Take III

Identifier issue

Take II

"end" too many

Okay, testing time -- Take ONE!

Nerd humor!

Well, that hit da spot!

After that the test can begin! ;)

I am hungry, I need to feed myself, and the clock also tells me I need to fill my cat's food bowl as well, so let's take care of that serious issue first!

Trith is that I do not expect anything to work at all, as this is pretty delecate code, however now all code that should lead to a result as at least been written allowing me to start an actual test....

When everything works the way it should Wendicka will leave the item itself be, but her arrival should cause a message to be generated in my debug log, allowing me to test if everything works

I've set up the routine which will allow Wendicka to walk to the item

And now it appears to work!

Again!

Syntax error in API

Compiling!

And that should link it all together

Neil code

API set up to make it possible for Apollo to create new Kthura objects of any kind and not just actors

It's late now... I hope I can get into the deep of all this tomorrow....

Assuming everything works the way it should (which is as I cannot test yet, far from certain) adding items to the field should be easy now, however I must take in mind that a few adaptions to the Apollo engine could be needed, as spawning actors is already possible but creating other kinds of Kthura objects may not yet be fully covered....

I've set up a generator which determines which items can be found randomly in a dungeon... This script is also set up to keep in mind that more kinds of items can be added when you enter the same dungeon during later cycles

I had to set a few things in order ... It's been a long time, so you cannot expect me to remember everything

I will do things a bit different than in the original game. In the original game you merely had to come close to an item to pick it up.... On slower computers this is bound to cause lags. In order to get rid of that I decided to make all items in the field clickables. This can make you miss some items in longer runs when you merely use Dijkstra to get to the next floor in one click as the heroes will no longer pick up items they come past, but it saves so much CPU speed in the process (as I now only have to check stuff whe you actually click something) I'll take that as a valid price to pay.

The way things are now cannot be tested... I cannot tell if this works now.... But from here I can set up the system that places items at random in dungeons

And now a headache is getting the better of me

Sub itself

More linkup done

I've set up some linkup code for Inventory read-outs

Big backup running now... May take longer than one day, but it's needed sometimes

The next step should be to make it possible for items to appear in the dungeons. After all, no items, no inventory

Take III

Coordinate fix

Wrong color fixed

The basis works, but some more work is required

Take II

That!

I wish I could say that for the inventory code

At least it appers the link works