Player controller code to sort input components better: widgets with 'Stop Input' go to top of priority stack, and also, priority actually works now.

Plugins/UEWingman/Source/UEWingman/Handlers/Sequence.h

@@ -23,8 +23,10 @@ public:
 	virtual void Register() override
 	{
 		UWingServer::AddHandler(this,
-			TEXT("Execute multiple commands in one request. Each subcommand produces its own content block in the response. "
-				"Nested Sequence commands are not allowed."));
+			TEXT("Execute multiple commands in one request. Each subcommand "
+				"produces its own content block in the response. The big win "
+				"performance-wise is that fewer MCP calls means fewer "
+				"round-trip invocations of the LLM."));
 	}
 	virtual void Handle() override
 	{
@@ -32,9 +34,8 @@ public:
 		// WingServer. Because of that, this handler is never actually called
 		// under normal conditions.  The handler exists for two reasons: to
 		// provide documentation, and also to catch the case where somebody
-		// nests a sequence inside another sequence (WingServer doesn't catch
-		// that).
-		//
-		WingOut::Stdout.Print(TEXT("ERROR: Sequence inside a Sequence is not allowed.\n"));
+		// nests a sequence inside another sequence.
+		WingOut::Stdout.Print(
+			TEXT("ERROR: Sequence inside a Sequence is not allowed.\n"));
 	}
 };

Plugins/UEWingman/Source/UEWingman/Private/WingManual.cpp

@@ -211,6 +211,7 @@ void UWingManualSections::ImportantCommands()
         "\n   Graph_Dump: a fairly detailed listing of any Graph"
         "\n   Details_Dump: Dump the details panel for a given object"
         "\n   Details_Set: Manipulate the details panel for a given object"
+        "\n   Sequence: Batch commands together for faster execution"
         "\n"
         "\n   You can use Documentation_Commands(Query=Command,Verbose=true)"
         "\n   to get detailed help for a specific command."