17
edits
Changes
→Behaviors
{{Under construction}}
{{Under construction}}
Brains were introduced in 1.14 (Village & Pillage) as an alternative to Goals and Targets, for use by the updated Villagers. Since then, all new mobs have been implemented using brains.
Brains were introduced in 1.14 (Village & Pillage) as an alternative to Goals and Targets, for use by the updated Villagers. Since then, almost all new mobs (exceptions: bees & striders) have been implemented using brains.
== Sensors ==
== Sensors ==
Sensors are used to collect information about the entity’s world. This is where things like entity searches and block searches should be performed. After a specified amount of ticks, any search logic will run and store relevant information in the entity’s Brain using Memory Modules.
Sensors are used to collect information about the entity’s world. This is where things like entity searches and block searches should be performed. After a specified amount of ticks (if not specified, it defaults to 20), any search logic will run and store relevant information in the entity’s Brain using Memory Modules.
== Memory Modules ==
== Memory Modules ==
== Behaviors ==
== Behaviors ==
Behaviors are Brain's equivalent of Goals, constructed using a map of MemoryModuleTypes to MemoryStatus that dictates whether or not the Behavior can start executing based on the presence or absence of specific Memory Modules. The equivalent to this in Goals is the Flags passed in to the "setFlags" method.
Behaviors are Brain's equivalent of Goals, constructed using a map of MemoryModuleTypes to MemoryStatus. This map functions as an "entry condition" that dictates whether or not the Behavior can start executing based on the presence or absence of specific Memory Modules. The equivalent to this in Goals is the Set of Flags passed in to the "setFlags" method during the Goal's construction.
They can also be given a min and/or max runtime duration in ticks, automatically terminating at a timestamp randomly determined by the supplied runtime duration value(s). The "checkExtraStartConditions", "start", "canStillUse", and "stop" methods correspond to Goal's "canUse", "start", "canContinueToUse" and "stop" methods, respectively.
They can also be given a min and/or max runtime duration in ticks, automatically terminating at a timestamp randomly determined by the supplied runtime duration value(s). The "checkExtraStartConditions", "start", "canStillUse", and "stop" methods correspond to Goal's "canUse", "start", "canContinueToUse" and "stop" methods, respectively.