Content.Server/DoAfter/DoAfterSystem.cs

using Content.Shared.DoAfter;
using JetBrains.Annotations;

namespace Content.Server.DoAfter;

[UsedImplicitly]
public sealed class DoAfterSystem : SharedDoAfterSystem
{

}
"ECS" do_after (#6531) 2022-02-20 06:15:57 +11:00			`using Content.Shared.DoAfter;`
do_after (#1616) * do_after Ports (most of) do_after from SS13. Callers are expected to await the DoAfter task from the DoAfterSystem. I had a dummy component for in-game testing which I removed for the PR so nothing in game uses do_after at the moment. Currently only the movement cancellation is predicted client-side. * Minor do_after doc cleanup * do_the_shuffle Fix nullable build errors. * The last nullable * Implement NeedHand Thanks zum. * nullable dereference * Adjust the system query Co-authored-by: Metal Gear Sloth <metalgearsloth@gmail.com> 2020-08-09 02:16:13 +10:00			`using JetBrains.Annotations;`

DoAfter Refactor (#13225) Co-authored-by: DrSmugleaf <drsmugleaf@gmail.com> 2023-02-24 19:01:25 -05:00			`namespace Content.Server.DoAfter;`
ECS damageable (#4529) * ECS and damage Data * Comments and newlines * Added Comments * Make TryChangeDamageEvent immutable * Remove SetAllDamage event Use public SetAllDamage function instead * Undo destructible mistakes That was some shit code. * Rename DamageData to DamageSpecifier And misc small edits misc * Cache trigger prototypes. * Renaming destructible classes & functions * Revert "Cache trigger prototypes." This reverts commit 86bae15ba6616884dba75f552dfdfbe2d1fb6586. * Replace prototypes with prototype IDs. * Split damage.yml into individual files * move get/handle component state to system * Update HealthChange doc * Make godmode call Dirty() on damageable component * Add Initialize() to fix damage test * Make non-static * uncache resistance set prototype and trim DamageableComponentState * Remove unnecessary Dirty() calls during initialization * RemoveTryChangeDamageEvent * revert Dirty() * Fix MobState relying on DamageableComponent.Dirty() * Fix DisposalUnit Tests. These were previously failing, but because the async was not await-ed, this never raised the exception. After I fixed MobState component, this exception stopped happening and instead the assertions started being tested & failing * Disposal test 2: electric boogaloo * Fix typos/mistakes also add comments and fix spacing. * Use Uids instead of IEntity * fix merge * Comments, a merge issue, and making some damage ignore resistances * Extend DamageSpecifier and use it for DamageableComponent * fix master merge * Fix Disposal unit test. Again. Snapgrids were removed in master * Execute Exectute 2021-09-15 03:07:37 +10:00
DoAfter Refactor (#13225) Co-authored-by: DrSmugleaf <drsmugleaf@gmail.com> 2023-02-24 19:01:25 -05:00			`[UsedImplicitly]`
			`public sealed class DoAfterSystem : SharedDoAfterSystem`
			`{`
do_after (#1616) * do_after Ports (most of) do_after from SS13. Callers are expected to await the DoAfter task from the DoAfterSystem. I had a dummy component for in-game testing which I removed for the PR so nothing in game uses do_after at the moment. Currently only the movement cancellation is predicted client-side. * Minor do_after doc cleanup * do_the_shuffle Fix nullable build errors. * The last nullable * Implement NeedHand Thanks zum. * nullable dereference * Adjust the system query Co-authored-by: Metal Gear Sloth <metalgearsloth@gmail.com> 2020-08-09 02:16:13 +10:00
Fix namespaces and optimize imports (#1651) * Fix namespaces and optimize imports * Cleanup fixes * Merge conflict fixes * Merge conflict fixes * Merge conflict fixes 2020-08-13 14:40:27 +02:00			`}`