View source for Zee August 8-August 15

Personally I think it was a good week. I've studied the server - superclient connection a lot to see how actions are triggered.

I've spent the time testing how the tribe behaves based on some simple target recipes (like... acquire 30 members... acquire 100 gold... etc)

I noticed that the former system had the tribe dig automatically for it's wealth. I've changed this and now the tribe explores for resources... and once it finds a mine it prospects it in order to see what's in it. (this is why I studied the network managers and added MSGTYPE_NPC_WORKDONE). Currently, the tribe explores and digs for whatever resource we signal in the recipes.

I've made some tweaks in the NPC code and tribe code in order to attach buffers to each npc. I wanted npcs to have their own buffers in order to remember their targets while working. (E.G. : once they are sent mining, they store their mining place in the NPC class, so the tribe can use it's buffers to keep own data or assign other tasks to other npcs) For this I added some other attributes in npcOperations. I will signal them in the wiki when I update the documentation.

I've added the CMD_SPAWN_BUILDING command. This will be used by the superclient to request a building from the server. I'm working on it atm... probably a MSGTYPE_PERSIST_ITEM will be the response sent to all clients containing the new building. (item dropped on the ground).
As per the location of the buildings... I think I'll use the easy way for now... as in... pre-select the locations for buildings and signal them in recipes.

PS: Various minor changes that I didn't note here can be found as comments on svn commits. They aren't as important on the long run though :)

High regards,
Zee.