Player-Condition-Profile.md

On it self it doesn't do anything, check where it is being referenced below.

For most cases, it loops through all the players and for each player it checks if the player passes all conditions, if that is the case the action, chat, spawncondition will only activate for that player. Handy for MP situations.

Player Tags

You can add Tags to certain players, what can be added by Behavior Actions and Event Actions, and be used as an extra condition for this condition profile. Examples on what you can make:

-Player attacks a factions ship -> Player gets tag ("Attacked_GC_recently") -> Retribution Spawngroup becomes eligible only for that player

-Make an Event that checks which SpawnOption the player chooses. -> What happens: Player chooses SpawnoptionA -> Event will trigger that activates some chat message -> using PlayerCondition again the message will only be visible for the player

-Some custom behaviour/chat messages from NPC based which tags player have.

Referenced by:

Event Conditions
Event Actions
Behavior Actions
Chat Profiles
SpawnConditions

Here's an example of how a Player Condition Profile definition is setup:

<EntityComponent xsi:type="MyObjectBuilder_InventoryComponentDefinition">
      <Id>
          <TypeId>Inventory</TypeId>
          <SubtypeId>PlayerConditionProfile-AHESpecialMessage</SubtypeId>
      </Id>
      <Description>
    [MES Player Condition]

    [CheckPlayerReputation:true]
    [CheckReputationwithFaction:AHE]
    [MinPlayerReputation:500]
    [MaxPlayerReputation:1500]

        [CheckPlayerTags:true]
    [IncludedPlayerTag:RecentyAttackedGCVessel]

      </Description> 
    </EntityComponent>

Tag:	AllowOverrides
Tag Format:	[AllowOverrides:Value]
Description:	nan
Allowed Values:	true false
Multiple Tag Allowed:	no

Tag:	AllPlayersMatchThisCondition
Tag Format:	[AllPlayersMatchThisCondition:Value]
Description:	nan
Allowed Values:	true false
Multiple Tag Allowed:	no

Tag:	UseFailCondition
Tag Format:	[UseFailCondition:Value]
Description:	nan
Allowed Values:	true false
Multiple Tag Allowed:	no

Tag:	UseAnyPassingCondition
Tag Format:	[UseAnyPassingCondition:Value]
Description:	nan
Allowed Values:	true false
Multiple Tag Allowed:	no

Tag:	CheckPlayerReputation
Tag Format:	[CheckPlayerReputation:Value]
Description:	nan
Allowed Values:	true false
Multiple Tag Allowed:	no

Tag:	CheckReputationwithFaction
Tag Format:	[CheckReputationwithFaction:Value]
Description:	nan
Allowed Values:	Any name string excluding :, [, ]
Multiple Tag Allowed:	yes

Tag:	MinPlayerReputation
Tag Format:	[MinPlayerReputation:Value]
Description:	nan
Allowed Values:	Any interger
Multiple Tag Allowed:	yes

Tag:	MaxPlayerReputation
Tag Format:	[MaxPlayerReputation:Value]
Description:	nan
Allowed Values:	Any interger
Multiple Tag Allowed:	yes

Tag:	CheckLastRespawnShipName
Tag Format:	[CheckLastRespawnShipName:Value]
Description:	nan
Allowed Values:	true false
Multiple Tag Allowed:	no

Tag:	LastRespawnShipName
Tag Format:	[LastRespawnShipName:Value]
Description:	nan
Allowed Values:	Any name string excluding :, [, ]
Multiple Tag Allowed:	no

Tag:	CheckPlayerTags
Tag Format:	[CheckPlayerTags:Value]
Description:	nan
Allowed Values:	true false
Multiple Tag Allowed:	no

Tag:	IncludedPlayerTag
Tag Format:	[IncludedPlayerTag:Value]
Description:	nan
Allowed Values:	Any name string excluding :, [, ]
Multiple Tag Allowed:	yes

Tag:	ExcludedPlayerTag
Tag Format:	[ExcludedPlayerTag:Value]
Description:	nan
Allowed Values:	Any name string excluding :, [, ]
Multiple Tag Allowed:	yes

Tag:	CheckPlayerNear
Tag Format:	[CheckPlayerNear:Value]
Description:	nan
Allowed Values:	true false
Multiple Tag Allowed:	no

Tag:	PlayerNearCoords
Tag Format:	[PlayerNearCoords:Value]
Description:	nan
Allowed Values:	A Vector3D Value in the following format: {X:# Y:# Z:#} .
Multiple Tag Allowed:	no

Tag:	PlayerNearDistanceFromCoords
Tag Format:	[PlayerNearDistanceFromCoords:Value]
Description:	nan
Allowed Values:	Any interger equal or greater than 0
Multiple Tag Allowed:	no

Tag:	PlayerNearMinDistanceFromCoords
Tag Format:	[PlayerNearMinDistanceFromCoords:Value]
Description:	nan
Allowed Values:	Any interger equal or greater than 0
Multiple Tag Allowed:	no

Additional Tags

These tags add player-state checks and requirements for Player Condition profiles.

Tag:	AllowAnyExcludedPlayerTag
Tag Format:	[AllowAnyExcludedPlayerTag:Value]
Description:	When true, allows any excluded player tag.
Allowed Value(s):	true false
Multiple Tags Allowed:	No

Tag:	AllowAnyIncludedPlayerTag
Tag Format:	[AllowAnyIncludedPlayerTag:Value]
Description:	When true, allows any included player tag.
Allowed Value(s):	true false
Multiple Tags Allowed:	No

Tag:	CheckPlayerCreditBalance
Tag Format:	[CheckPlayerCreditBalance:Value]
Description:	When true, checks player credit balance.
Allowed Value(s):	true false
Multiple Tags Allowed:	No

Tag:	CheckPlayerInActiveZone
Tag Format:	[CheckPlayerInActiveZone:Value]
Description:	When true, checks player in active zone.
Allowed Value(s):	true false
Multiple Tags Allowed:	No

Tag:	CheckPlayerInZone
Tag Format:	[CheckPlayerInZone:Value]
Description:	When true, checks player in zone.
Allowed Value(s):	true false
Multiple Tags Allowed:	No

Tag:	ExcludedPlayerTags
Tag Format:	[ExcludedPlayerTags:Value]
Description:	List of values for excluded player tags.
Allowed Value(s):	Comma-separated list of values
Multiple Tags Allowed:	Yes

Tag:	IncludedPlayerTags
Tag Format:	[IncludedPlayerTags:Value]
Description:	List of values for included player tags.
Allowed Value(s):	Comma-separated list of values
Multiple Tags Allowed:	Yes

Tag:	MaxPlayerCreditBalance
Tag Format:	[MaxPlayerCreditBalance:Value]
Description:	Maximum value for player credit balance.
Allowed Value(s):	Any Integer Value
Multiple Tags Allowed:	No

Tag:	MinPlayerCreditBalance
Tag Format:	[MinPlayerCreditBalance:Value]
Description:	Minimum value for player credit balance.
Allowed Value(s):	Any Integer Value
Multiple Tags Allowed:	No

Tag:	ZoneName
Tag Format:	[ZoneName:Value]
Description:	Configures zone name.
Allowed Value(s):	Comma-separated list of values
Multiple Tags Allowed:	Yes