Tribe Design - Revision history

Talad: Undo revision 25740 by Talad (talk)

2026-02-17T21:35:42Z

Undo revision 25740 by Talad (talk)

← Older revision		Revision as of 21:35, 17 February 2026
Line 267:		Line 267:
	<percept event="fight" />		<percept event="fight" />
	</behavior>		</behavior>


			the important piece is target ="tribe" because this trigger a perception in the tribe in Tribe::SendPerception() that scans all the NPCs and sends the given perception = "tribesman attacked"

			This is defined again in AbstractTribesman
			<react event="tribesman attacked" behavior="normal_attacked" delta="100" do_not_interrupt="Chase"/>
			and this points to a normal attack! Which just asks the npc to fight.
	[[Category:Engine documents]] [[Category:NPCClient Design]]		[[Category:Engine documents]] [[Category:NPCClient Design]]

Talad: /* Tribe reaction to attacks */

2026-02-16T22:53:35Z

Tribe reaction to attacks

← Older revision		Revision as of 22:53, 16 February 2026
Line 267:		Line 267:
	<percept event="fight" />		<percept event="fight" />
	</behavior>		</behavior>


	~~the important piece is target ="tribe" because this trigger a perception in the tribe in Tribe::SendPerception() that scans all the NPCs and sends the given perception = "tribesman attacked"~~

	~~This is defined again in AbstractTribesman~~
	~~<react event="tribesman attacked" behavior="normal_attacked" delta="100" do_not_interrupt="Chase"/>~~
	~~and this points to a normal attack! Which just asks the npc to fight.~~
	[[Category:Engine documents]] [[Category:NPCClient Design]]		[[Category:Engine documents]] [[Category:NPCClient Design]]

Talad: /* Tribe reaction to attacks */

2026-02-16T22:53:30Z

Tribe reaction to attacks

← Older revision		Revision as of 22:53, 16 February 2026
Line 254:		Line 254:

	Anything but cowards gets		Anything but cowards gets
			reaction = "<react event=\"attack\" behavior=\"united_attacked\" delta=\"100\" />";

	~~reaction = "<react event=\"attack\" behavior=\"united_attacked\" delta=\"100\" />";~~

			When a player attacks a member of a tribe , the line above triggers a behavior on the attack.


			In AbstractTribesman this happens:
			<behavior name="united_attacked" decay="10">
			<talk text="The tribe is under attack!" target="false" />
			<locate obj="tribe:target" range="100" />
			<percept event="tribesman attacked" target="tribe" range="30" />
			<percept event="fight" />
			</behavior>


			the important piece is target ="tribe" because this trigger a perception in the tribe in Tribe::SendPerception() that scans all the NPCs and sends the given perception = "tribesman attacked"

			This is defined again in AbstractTribesman
			<react event="tribesman attacked" behavior="normal_attacked" delta="100" do_not_interrupt="Chase"/>
			and this points to a normal attack! Which just asks the npc to fight.
	[[Category:Engine documents]] [[Category:NPCClient Design]]		[[Category:Engine documents]] [[Category:NPCClient Design]]

Talad at 23:23, 10 February 2026

2026-02-10T23:23:55Z

← Older revision		Revision as of 23:23, 10 February 2026
Line 247:		Line 247:

	The mining tribe will send his members to explore in search of resources. This is done with the Behavior "Explore" in the AbstractTribsmen NPC Type stored in sc_npctypes.		The mining tribe will send his members to explore in search of resources. This is done with the Behavior "Explore" in the AbstractTribsmen NPC Type stored in sc_npctypes.

			== Tribe reaction to attacks ==


			In RecipeManager::CreateGlobalNPCType() we check the Unity Trait of the tribe: cowards / normal / united

			Anything but cowards gets

			reaction = "<react event=\"attack\" behavior=\"united_attacked\" delta=\"100\" />";



	[[Category:Engine documents]] [[Category:NPCClient Design]]		[[Category:Engine documents]] [[Category:NPCClient Design]]

Talad: /* Step #2 (RunTime) */

2021-08-29T19:18:03Z

Step #2 (RunTime)

← Older revision		Revision as of 19:18, 29 August 2021
Line 180:		Line 180:
	* Distributed Parsing : The parser takes the first requirement and checks it + tries to achieve it. When the same recipe gets parsed again, the parser takes the second requirement (even if the first is still not met) and tries to achieve it. This way, the parser loops through requirements and tries to achieve all in parallel.		* Distributed Parsing : The parser takes the first requirement and checks it + tries to achieve it. When the same recipe gets parsed again, the parser takes the second requirement (even if the first is still not met) and tries to achieve it. This way, the parser loops through requirements and tries to achieve all in parallel.
	* Concentrated Parsing : The parser tries to achieve the first requirement on each recipe parse until it is met. After that it picks the second requirement and applies the same principle.		* Concentrated Parsing : The parser tries to achieve the first requirement on each recipe parse until it is met. After that it picks the second requirement and applies the same principle.

			5) A new child of the RecipeTree is added as soon as the tribe decides that something can be executed (all requirements met). This is added to 'tribalRecipe' variable. Then the algorithm of this recipe is executed (for example percect NPC to go work), and the child is immediately removed from the tree. This mean that while the NPC is working, the tree does not contain that child anymore, so if another NPC becomes available, it will pick the NEXT requirement in line.



			Example of Distributed vs Concentracted Parsing:

	E.G.: We want our tribe to gain 150 of Coal, Silver, Gold and Platinum.		E.G.: We want our tribe to gain 150 of Coal, Silver, Gold and Platinum.

Talad: /* Step #2 (RunTime) */

2021-08-28T23:05:20Z

Step #2 (RunTime)

← Older revision		Revision as of 23:05, 28 August 2021
Line 164:		Line 164:

	(executed once on startup and each time a recipe is completed)		(executed once on startup and each time a recipe is completed)

			1) NPCManager is ticking all the tribes with frequency TRIBE_TICK (tribe.h) and calling Advance() on each tribe

			2) Each tribe searches for idle members, to assign tasks in Tribe::Advance()

			3) updates the waiting time of all the TOP level recipe (the ones listed in mysql:'tribes_recipe.algorithm' as loadRecipe())

			4) select the best recipe based on lowest wait time and high priority (where priority is defined level in the recipe tree, the lowest the better)

	The Tribal Object selects the top-priority recipe which needs execution and sends it to the Recipe Manager.		The Tribal Object selects the top-priority recipe which needs execution and sends it to the Recipe Manager.
Line 189:		Line 197:
	*Step 151: Assign miner to Silver.		*Step 151: Assign miner to Silver.
	...		...


	==Step #3 (Recipe's Algorithm)==		==Step #3 (Recipe's Algorithm)==

Talad: /* Step #1 (Loading) */

2021-08-28T22:08:28Z

Step #1 (Loading)

← Older revision		Revision as of 22:08, 28 August 2021
Line 140:		Line 140:
	On NPCClient's startup everything is loaded into the classes.		On NPCClient's startup everything is loaded into the classes.

	The Recipe Manager loads all available recipes from mysql:'tribe_recipes' and add those in a flat array "recipes", one entry per recipe.		1) The Recipe Manager loads all available recipes from mysql:'tribe_recipes' and add those in a flat array "recipes", one entry per recipe.

	~~During load,~~ the ~~Recipe Manager parses~~ the ~~requirements and keeps them in the Recipe Class. (Recipe~~:~~:requirements<Recipe::Requirement>)~~		2) psNPCManager::LoadTribes() loads from the database all the tribes from mysql:'tribes'

	~~The Tribal Object receives~~ all the information regarding the tribe:		3) For each tribe psNPCManager::LoadTribes() loads all the information regarding the tribe:
	*resources from mysql:'sc_tribe_resources'		*resources from mysql:'sc_tribe_resources'
	*memories from mysql:'sc_tribe_memories'		*memories from mysql:'sc_tribe_memories'
Line 152:		Line 152:
	*npc's are loaded by the psNPCClient and assigned to the tribe		*npc's are loaded by the psNPCClient and assigned to the tribe

	Further on, each Tribal Object is linked to the Recipe Manager. (a pointer is sent and loaded into a csArray)		4) For each tribe it calls RecipeManager::AddTribe() , which parses the requirements and keeps them in the Recipe Class. (Recipe::requirements<Recipe::Requirement>)

			5) Further on, each Tribal Object is linked to the Recipe Manager. (a pointer is sent and loaded into a csArray)
	For each tribe loaded, the Recipe Manager does the following:		For each tribe loaded, the Recipe Manager does the following:
	* assembles a data structure named 'TribeData'		* assembles a data structure named 'TribeData'

Talad: /* Step #1 (Loading) */

2021-08-28T22:00:28Z

Step #1 (Loading)

← Older revision		Revision as of 22:00, 28 August 2021
Line 140:		Line 140:
	On NPCClient's startup everything is loaded into the classes.		On NPCClient's startup everything is loaded into the classes.

	The Recipe Manager loads all available recipes from mysql:'tribe_recipes'.		The Recipe Manager loads all available recipes from mysql:'tribe_recipes' and add those in a flat array "recipes", one entry per recipe.

	During load, the Recipe Manager parses the requirements and keeps them in the Recipe Class. (Recipe::requirements<Recipe::Requirement>)		During load, the Recipe Manager parses the requirements and keeps them in the Recipe Class. (Recipe::requirements<Recipe::Requirement>)

Talad: /* Mining tribe */

2021-06-19T17:39:45Z

Mining tribe

← Older revision		Revision as of 17:39, 19 June 2021
Line 211:		Line 211:
	<react event="tribe:mine" behavior="MineResource" />		<react event="tribe:mine" behavior="MineResource" />

	~~Upon~~ 'Explore' behavior, tribe members ~~may~~ find ~~locations named '~~mine'. After mining from an unknown deposit, the npcclient will receive a psWorkDoneMessage telling it what his npc just mined. This function renames the former 'mine' Memory with it's real deposit name.		During the 'Explore' behavior, tribe members will move around the map. psNPCManager::PerceptProximityLocations() is called every second, triggering a LocationPerception with "location sensed" to all NPC in range. This perception will make the NPC find the mine.

			After mining from an unknown deposit, the npcclient will receive a psWorkDoneMessage telling it what his npc just mined. This function renames the former 'mine' Memory with it's real deposit name.

	Two things need to happen:		Two things need to happen:

Talad: /* Runtime */

2021-06-19T17:07:38Z

Runtime

← Older revision		Revision as of 17:07, 19 June 2021
Line 211:		Line 211:
	<react event="tribe:mine" behavior="MineResource" />		<react event="tribe:mine" behavior="MineResource" />

	The tribe ~~will then select~~		Upon 'Explore' behavior, tribe members may find locations named 'mine'. After mining from an unknown deposit, the npcclient will receive a psWorkDoneMessage telling it what his npc just mined. This function renames the former 'mine' Memory with it's real deposit name.

			Two things need to happen:

			1) The tribe sends a member to explore for mining locations, this happens with

			<react event="tribe:explore" behavior="Explore" />

			2) The tribe sends a members to mine for a KNOWN resource location, this happens with

			<react event="tribe:mine" behavior="MineResource" />


			Important methods:
			* psNPCManager::PerceptProximityLocations() is called every second, triggering a LocationPerception with "location sensed" to all NPC in range
			* NPCType::FirePerception() is checking if this NPC should automemorize the new locations sensed
			* Tribe::Memorize() where we add the location found to the NPC memory

	The mining tribe will send his members to explore in search of resources. This is done with the Behavior "Explore" in the AbstractTribsmen NPC Type stored in sc_npctypes.		The mining tribe will send his members to explore in search of resources. This is done with the Behavior "Explore" in the AbstractTribsmen NPC Type stored in sc_npctypes.

	~~Inside the "Explore"~~

	[[Category:Engine documents]] [[Category:NPCClient Design]]		[[Category:Engine documents]] [[Category:NPCClient Design]]