Now it's gonna be interessting ^^ I was wondering why I couldn't find any code using add_struct in your new itemsystem. That's why I asked the saving-question.

Saving structs seems not to be a problem. You have some itemcreate-function where you malloc the struct: This could be a place for add_struct. A disadvantage is if those added items doesn't exists anymore when saving the game. To solve this you could implement an array or a motherstruct which manages the items an saves all pointers to existing ones. When the user saves the game you have to use add_struct for all these struct-pointers.
But loading structs is mystery for my as well. Don't get where the data could be after loading or meet some errors like "Couldn't load xyz.sav".

After doing these add_structs I still have a showdescription error in inventory and equipment. Not sure where to place those or what to use as the void* data that the add_struct calls for. Here is what I have done so far and not sure if these are even correct.

add_struct(NHAC_CINVENT_CELLS[NHAC_CINVCELLS], sizeof(RPGItem));
add_struct(NHAC_CINVENT_EQUIP[NHAC_CINVCELLS], sizeof(RPGItem));
add_struct(NHAC_MOUSEITEM, sizeof(RPGItem));

Try this instead to get the correct memory areas



However this won't do, as it will not save items dropped on the ground

Yeah I dont know. This is little bit beyond my ability and kinda frustrating. I was planning on doing structs for character stats, monster stats and combat tables but now I might rethink it all unless I can figure it out.

Items on the ground exists as ENTITY in the level - Entities could save by the normal game_save() function. You need only a code in the action which cretae a new struct for this item after loading the game and maybe register this struct to your item-management-system if necessary.
Have your get the save and load of the item-structs in the inventory worked?

I think that the best way would be to put all struct instances into a linked list, to easily iterate through them and make sure that all items are saved.

About the items on the ground - those entities got the address of an RPGItem instance, and that address might not be valid after a game_load. Another option is to remove the RPGItem-instance when an item is dropped on the ground, and then store the item stats in the skills of the entity (and then re-create the RPGItem instance when the item is picked up).

However, it would be very nice if struct-instances in Lite-C was saved automatically - I'll suggest that in the "The Future" forum

@Claus,
I was thinking since the members of the data structure only exist during runtime that maybe they should be saved to a file. I found similar in aum 83 and aum 69. If they were saved to like a *.ini file then they could be read anytime and none of the information would be lost. The thing is that your template is alot of code and every instance would have to be found and then read from a file.

I'm still at the artwork stage of my game and unfortunately I dont have the time to help.

Saving it in a separate file would no doubt be the best, but such things as items lying on the ground does complicate it a bit.

I'm currently trying to get a project done in time for the shader contest (and I'm quite a noob at shaders, so it really takes some time :P), and my summer holidays are over when I'm done with that, so I don't know when I'll have time to see to this

can someone post a new link for this? it seems that its inaccessible on the nighthawk website

thanks in advanced

Is there anyone who still has this OLD template on it's HDD? I would be grateful.