Need more triggers

[slarticodefast]

Description

Now that #39034 is merged we can start adding a lot more triggers and trigger effects. Many of these will be needed for the game tutorial.

Implementing them is pretty straightforward, in most cases it's just a single event subscription. If you want to add some of these best do them in small batches to make it easier to review.
Make sure to add datafields for parameters that might be needed and set the user entity to something useful where possible.

Triggers:

• TriggerOnExamined Add trigger-refactor components and systems: Batch 1 #39391
• TriggerOnInsertedIntoContainer Add container-related triggers #39647
• TriggerOnGotInsertedIntoContainer Add container-related triggers #39647
• TriggerOnRemovedFromContainer Add container-related triggers #39647
• TriggerOnGotRemovedFromContainer Add container-related triggers #39647
• TriggerOnRoundEnd Trigger on round end #39545
• TriggerOn(Un)Embed
• TriggerOnUiOpen (should be possible to use with a specific ui key)
• TriggerOnUiClose
• TriggerOnInteractHand ExtinguishOnTrigger and TriggerOnInteractHand #39537
• TriggerOnInteractUsing (should have a whitelist) Trigger for OnInteractUsing #39692
• TriggerOnToolUse TriggerOnSimpleToolUsage and add tool locks to syndicate items #39900
• TriggerOnMeleeHit TriggerOnMeleeHit and more #39826
• TriggerOnThrow Throwing triggers #39650
• TriggerOnThrown Throwing triggers #39650
• TriggerOnLand Add trigger-refactor components and systems: Batch 1 #39391
• TriggerOnDid(Un)EquipHand Hand pickup and drop triggers #39663
• TriggerOnGot(Un)EquippedHand Hand pickup and drop triggers #39663
• TriggerOnDropped Hand pickup and drop triggers #39663
• TriggerOnHandSelected
• TriggerOnHandDeselected
• TriggerOn(Un)Equip Equip and unequip triggers #39675
• TriggerOn(Got)UnEquipped Equip and unequip triggers #39675
• TriggerOnGamerule
• TriggerOnKeyPressed (should work for various input buttons, needed for the tutorial to check if the player has completed a step)
• TriggerOnPullStarted (should have a bool for triggering when being the puller or pulled entity)
• TriggerOnPullStopped
• TriggerOnCombatMode
• TriggerOn(Un)Anchored
• TriggerOnCrafted (when a player sucessfully crafted something, should have some kind of whitelist)
• TriggerOn(Un)Buckle Add trigger-refactor components and systems: Batch 1 #39391
• TriggerOn(Un)Stapped Add trigger-refactor components and systems: Batch 1 #39391
• TriggerOnSolutionEmpty
• TriggerOnLock
• TriggerOnUnlock
• TriggerOnPlayerSpawnComplete (PlayerSpawnCompleteEvent) TriggerOnPlayerSpawnComplete and ExplosionOnTrigger #39820
• TriggerOnImplantImplanted
• TriggerOnImplantRemoved

Trigger effects:

• PopupOnTrigger PopupOnTrigger #39913
• UseChargeOnTrigger (for LimitedChargesComponent)
• FlameStackOnTrigger Fire stacks trigger #39530
• ExtinguishOnTrigger ExtinguishOnTrigger and TriggerOnInteractHand #39537
• TransferSolutionOnTrigger
• AddSolutionOnTrigger AddReagentOnTrigger #39875
• RemoveSolution/ReagentOnTrigger
• AddTagOnTrigger
• RemoveTagOnTrigger
• OpenAirlockOnTrigger
• CloseAirlockOnTrigger
• (Un)BoltAirlockOnTrigger
• ToggleEmergencyAccessOnTrigger
• MapTextOnTrigger (see MapTextComponent, should be possible to both enable and disable it)
• TogglePointLightOnTrigger
• TippyOnTrigger (will need refactoring)
• ToggleApcOnTrigger
• SwapLocationOnTrigger (between the entity and the user)
• ExplosionOnTrigger (ExplodeOnTrigger already exists, but we need another one that works without ExplosiveComponent, so use QueueExplosion) TriggerOnPlayerSpawnComplete and ExplosionOnTrigger #39820
• GameRuleOnTrigger GameRuleOnTrigger #39845
• AddMindRoleOnTrigger
• RemoveMindRoleOnTrigger
• MakeAntagOnTrigger
• RemoveComponentsOnTrigger RemoveComponentsOnTrigger, ToggleComponentsOnTrigger #39639
• ToggleComponentsOnTrigger RemoveComponentsOnTrigger, ToggleComponentsOnTrigger #39639
• AdminLogOnTrigger
• ScramOnTrigger Turn some implants into triggers #39364
• DnaScrambleOnTrigger Turn some implants into triggers #39364
• UncuffOnTrigger Turn some implants into triggers #39364
• StunOnTrigger
• StaminaDamageOnTrigger StaminaDamageOnTriggerComponent #39607
• KnockdownOnTrigger
• StatusEffectOnTrigger
• AddObjectiveOnTrigger
• RemoveObjectiveOnTrigger
• TeleportOnTrigger (To specified map or grid coordinates)
• LockOnTrigger Add voice locks to various hidden syndicate items #39310
• SpawnEntityTable on Trigger SpawnEntityTableOnTrigger #39909
• WeatherOnTrigger Weather On Trigger #40505
• EntityEffectOnTrigger Add EntityEffectOnTrigger and RejuvenateOnTrigger #40967
• RejuvenateOnTrigger Add EntityEffectOnTrigger and RejuvenateOnTrigger #40967

Trigger conditions:

• MindRoleTriggerCondition Mindrole trigger condition #40323
• ChargeTriggerCondition
• RandomChanceTriggerCondition RandomChance trigger condition #39543

If you got more ideas let me know and I'll add them to the list.

[iaada]

The update loop in PowerSinkSystem could be cut down to a TriggerOnFullBattery and the existing ExplodeOnTrigger.

TrashOnSolutionEmpty could also be replaced with TriggerOnSolutionEmpty and AddTagOnTrigger, but you would also need something along the lines of TriggerOnSolutionNotEmpty (but maybe not so specific).

[slarticodefast]

The update loop also does some other stuff, so I think it's fine to keep it that way without forcing triggers into it.
TrashOnSolutionEmpty also seems fine for convenience, it's more compact to add this single component to food items than a bunch of triggers that have to raise multiple events.

But there are some other components that can be split up into trigger component pairs, for example DamageOnToolInteract, AnnounceOnSpawnComponent or ExtinguishOnInteract.

[perryprog]

Stun (including non-stunning stamina damage) and knockdown on trigger would be neat.

Anyway I wonder what we need to add to make triggers turing complete.

[perryprog]

A RandomChanceTriggerCondition type of thing would be nice too. Mutually exclusive args for specifying the probability with triggerOnOneIn: 5 versus triggerWithProbability: 0.2 would be neat (or maybe make it a percentage I dunno; also note the field names since it's otherwise ambiguous if it's 'doesn't trigger 1/5 times' or 'does trigger in 1/5 times'). Would want to be optionally predicted via for cases where you want to avoid the client gaming it Doom RNG manipulation style. See:

space-station-14/Content.Shared/Body/Systems/SharedBloodstreamSystem.cs

Lines 224 to 228 in 22e3d53

	// TODO: Replace with RandomPredicted once the engine PR is merged
	// Use both the receiver and the damage causing entity for the seed so that we have different results for multiple attacks in the same tick
	var seed = SharedRandomExtensions.HashCodeCombine(new() { (int)_timing.CurTick.Value, GetNetEntity(ent).Id, GetNetEntity(args.Origin)?.Id ?? 0 });
	var rand = new System.Random(seed);
	var prob = Math.Clamp(totalFloat / 25, 0, 1);

[beck-thompson]

Add objective on trigger might be cool as well

[Bamgeglo1485]

THESE POSSIBILITIES FOR MY PROTOTYPES WITHOUT THE NEED FOR MY SHITCODE, I HAVE AN ERECTION

[ScarKy0]

Added in TeleportOnTrigger