Reduce verb menu pop-in / rearranging (#6611)

Content.Client/Pointing/PointingSystem.cs

@@ -0,0 +1,47 @@
+using Content.Client.Pointing.Components;
+using Content.Shared.MobState.Components;
+using Content.Shared.Pointing;
+using Content.Shared.Verbs;
+
+namespace Content.Client.Pointing;
+
+internal sealed class PointingSystem : EntitySystem
+{
+    public override void Initialize()
+    {
+        base.Initialize();
+
+        SubscribeLocalEvent<GetVerbsEvent<Verb>>(AddPointingVerb);
+    }
+
+    private void AddPointingVerb(GetVerbsEvent<Verb> args)
+    {
+        // Really this could probably be a properly predicted event, but that requires reworking pointing. For now
+        // I'm just adding this verb exclusively to clients so that the verb-loading pop-in on the verb menu isn't
+        // as bad. Important for this verb seeing as its usually an option on just about any entity.
+
+        if (HasComp<PointingArrowComponent>(args.Target))
+        {
+            // this is a pointing arrow. no pointing here...
+            return;
+        }
+
+        // Can the user point? Checking mob state directly instead of some action blocker, as many action blockers are blocked for
+        // ghosts and there is no obvious choice for pointing (unless ghosts CanEmote?).
+        if (TryComp(args.User, out MobStateComponent? mob) && mob.IsIncapacitated())
+            return;
+
+        // We won't check in range or visibility, as this verb is currently only executable via the context menu,
+        // and that should already have checked that, as well as handling the FOV-toggle stuff.
+
+        Verb verb = new()
+        {
+            Text = Loc.GetString("pointing-verb-get-data-text"),
+            IconTexture = "/Textures/Interface/VerbIcons/point.svg.192dpi.png",
+            ClientExclusive = true,
+            Act = () => RaiseNetworkEvent(new PointingAttemptEvent(args.Target))
+        };
+
+        args.Verbs.Add(verb);
+    }
+}