Talk:Tribes expansion - Revision history

Magodra: /* XML DB */

2011-05-19T18:51:28Z

XML DB

← Older revision		Revision as of 18:51, 19 May 2011
Line 42:		Line 42:

	--[[User:Zee\|Zee]] 21:11, 4 May 2011 (UTC)		--[[User:Zee\|Zee]] 21:11, 4 May 2011 (UTC)

			Currently we are in the process of moving the npcbehavior.xml file into the DB. Configuration Managment of xml files that needs to be loaded is a nightmare, so we prefer having tables that can be edited through the [[Web Console]]. For th enpcbehavior we will use a text field that will have xml in it. So if the data isn't of a sort that is easy to put in tables we can do the same. But the new stuff should not depend on some xml files loaded from the filesystem.

			--[[User:Magodra\|Magodra]] 18:51, 19 May 2011 (UTC)

	== Treats ==		== Treats ==

2011-05-06T20:59:16Z

Treats

← Older revision		Revision as of 20:59, 6 May 2011
Line 52:		Line 52:

	--[[User:Zee\|Zee]] 21:16, 4 May 2011 (UTC)		--[[User:Zee\|Zee]] 21:16, 4 May 2011 (UTC)

			== Tribe object ==
			=== Splitting member arrays ===
			Comment to splitting the npcs in the tribe into different tables. At least we should still keep the current members table so that iterating all members will be easy. Though if needed we can create new access functions to speed up things. Though today each NPC have the tribeMemberType that is used to select what need set to use. This was thought to be a way to create different professions.
			--[[User:Magodra\|Magodra]] 20:59, 6 May 2011 (UTC)
			=== Recipe System ===

			Many of the needs have a concept of depended needs. E.g. the tribe ResourceArea (The need to go harvest/dig something have a dependency to explore. Can't get resources unless you know where they are. The ReproduceNeed have a dependency that in most cases will be to gather resources. If the key to be able to do the need isn't yet reached the depended need will be selected in the tribe brain when an npc become available for a new task.
			--[[User:Magodra\|Magodra]] 20:59, 6 May 2011 (UTC)

2011-05-04T21:29:07Z

Moods

@@ Line 7: / Line 7: @@
 --[[User:Magodra|Magodra]] 19:06, 3 May 2011 (UTC)
-For the random behavior I suggest to look into sending them as perceptions. When the npcclient advance the the npcclient could loop over every npc that has a reaction of type mood and than check if a perception should be fired. This should include to create a general map of perception_types_by_npc to greatly improve the performance of the perception system in general in the NPCClient. Today every npc and ever reaction is checked when a perception is fired. With this map only the npcs that has a given reaction type would be iterated.
+Adding an operation to handle mood changing and executing it on a TimeOfTheDay perception is a great idea, I'll work on it.
 --[[User:Magodra|Magodra]] 04:01, 4 May 2011 (UTC)
 == XML <-> DB ==

2011-05-04T21:16:21Z

Treats

← Older revision		Revision as of 21:16, 4 May 2011
Line 31:		Line 31:

	--[[User:Magodra\|Magodra]] 19:06, 3 May 2011 (UTC)		--[[User:Magodra\|Magodra]] 19:06, 3 May 2011 (UTC)

			I read the documentation on TribeNeedSet before writing the page. I wanted to adapt my ideas as much as I can so I can alter the existing code as little as possible. I think we will only need to add some methods on TribeNeedSet that will break more complex needs into base needs and prioritize them. (Mention: More Research on my behalf is required here)

			--[[User:Zee\|Zee]] 21:16, 4 May 2011 (UTC)

2011-05-04T21:11:26Z

XML DB

← Older revision		Revision as of 21:11, 4 May 2011
Line 21:		Line 21:
	Tribes, as I see them, have a variable number of needsets, so storing them in the database will require us to serialize everything into a single column.		Tribes, as I see them, have a variable number of needsets, so storing them in the database will require us to serialize everything into a single column.
	Example: Needsets: expansionist\|advanced\|diplomatic		Example: Needsets: expansionist\|advanced\|diplomatic

	I think moods can be stored in a db, yes.		I think moods can be stored in a db, yes.

2011-05-04T21:11:02Z

XML DB

← Older revision		Revision as of 21:11, 4 May 2011
Line 22:		Line 22:
	Example: Needsets: expansionist\|advanced\|diplomatic		Example: Needsets: expansionist\|advanced\|diplomatic
	I think moods can be stored in a db, yes.		I think moods can be stored in a db, yes.

			--[[User:Zee\|Zee]] 21:11, 4 May 2011 (UTC)

	== Treats ==		== Treats ==

2011-05-04T21:10:44Z

XML DB

← Older revision		Revision as of 21:10, 4 May 2011
Line 17:		Line 17:

	--[[User:Magodra\|Magodra]] 19:06, 3 May 2011 (UTC)		--[[User:Magodra\|Magodra]] 19:06, 3 May 2011 (UTC)

			What do you suggest we should keep in a database? (rather than in the xml)
			Tribes, as I see them, have a variable number of needsets, so storing them in the database will require us to serialize everything into a single column.
			Example: Needsets: expansionist\|advanced\|diplomatic
			I think moods can be stored in a db, yes.

	== Treats ==		== Treats ==

2011-05-04T04:01:16Z

Moods

← Older revision		Revision as of 04:01, 4 May 2011
Line 6:		Line 6:

	--[[User:Magodra\|Magodra]] 19:06, 3 May 2011 (UTC)		--[[User:Magodra\|Magodra]] 19:06, 3 May 2011 (UTC)

			For the random behavior I suggest to look into sending them as perceptions. When the npcclient advance the the npcclient could loop over every npc that has a reaction of type mood and than check if a perception should be fired. This should include to create a general map of perception_types_by_npc to greatly improve the performance of the perception system in general in the NPCClient. Today every npc and ever reaction is checked when a perception is fired. With this map only the npcs that has a given reaction type would be iterated.

			--[[User:Magodra\|Magodra]] 04:01, 4 May 2011 (UTC)

	== XML <-> DB ==		== XML <-> DB ==

2011-05-03T19:08:12Z

Threats

← Older revision		Revision as of 19:08, 3 May 2011
Line 14:		Line 14:
	--[[User:Magodra\|Magodra]] 19:06, 3 May 2011 (UTC)		--[[User:Magodra\|Magodra]] 19:06, 3 May 2011 (UTC)

	== ~~Threats~~ ==		== Treats ==

	The npcclient has a needset concept already. It should be evaluated if the existing need set concept is the same as the new suggested sets.		The npcclient has a needset concept already. It should be evaluated if the existing need set concept is the same as the new suggested sets.

	--[[User:Magodra\|Magodra]] 19:06, 3 May 2011 (UTC)		--[[User:Magodra\|Magodra]] 19:06, 3 May 2011 (UTC)

2011-05-03T19:06:27Z

Moods