Working on radial menus

Plugins/UEWingman/README.md

@@ -16,14 +16,12 @@ blueprints, widget blueprints, and materials.
 
 ## How Does it Work?
 
-This tool adds a command interpreter plugin to the Unreal
+This tool adds a command line interpreter plugin to the Unreal
 Editor. You can type commands, and the plugin in the editor
-will execute them. You can actually type commands directly
-from the command-line. Here's an example of what you might
-see:
+will execute them.
 
 ```
- $ ue-wingman.py Graph_Dump Graph=/Game/Testing/BP_Test,graph:EventGraph
+ $ ue-wingman Graph_Dump /Game/Testing/BP_Test,graph:EventGraph
  
  node K2Node_Event_0: Event BeginPlay
      output-pins OutputDelegate
@@ -32,33 +30,30 @@ see:
     output-pins OutputDelegate, DeltaSeconds
 ```
 
-There are tons of commands built in: Graph_Dump,
-GraphNode_Add, GraphPin_Connect,
-BlueprintComponent_Add, Widget_Add, and so forth.
-Using these commands, it's possible to examine and modify
-blueprints, widgets, and materials.
+The ue-wingman command has tons of subcommands: Graph_Dump,
+GraphNode_Add, GraphPin_Connect, BlueprintComponent_Add,
+Widget_Add, and so forth. Using these commands, it's
+possible to examine and modify blueprints, widgets, and
+materials.
 
 But, of course, these commands aren't really intended for humans.
-They're intended for an AI agent.  The AI is given access to these
-commands using what's called "Model Context Protocol," which is
-a goofy name for "a mechanism that an AI can use to send
-commands to other software."
+They're intended for an AI agent.
 
-## Why Choose this Particular Unreal Engine MCP?
+## Why Choose this Particular Unreal AI Plugin?
 
-There are a *lot* of Unreal Engine MCPs out there.  Some of
+There are a *lot* of Unreal Engine AI plugins out there.  Some of
 them are, shall we say, not carefully engineered.  I'm a
 reasonably skilled software engineer and I've designed
 this plugin to be robust and capable of sustained development.
 
-This MCP is also designed to be as broadly general as
-possible. I've seen MCPs that claim "can create 22 different
+This plugin is also designed to be as broadly general as
+possible. I've seen plugins that claim "can create 22 different
 kinds of graph nodes!"  This makes me ask: why not just
 provide the *entire catalog* of all possible graph nodes?
-I've seen MCPs claim "you can edit 15 different material
+I've seen plugins claim "you can edit 15 different material
 expression properties!"  Why not provide access to *all*
 editable material expression properties? I've tried to make
-every tool in this MCP as capable as possible, with as few
+every tool in this plugin as capable as possible, with as few
 limits as possible.
 
 Some of the MCPs out there expose the entire Unreal API to
@@ -76,15 +71,16 @@ commands.
 
 ## Installation
 
-There are three parts to UE Wingman:
+There are two parts to UE Wingman:
 
 * The Unreal Plugin, which does 99% of the work.
 
-* The python program "ue-wingman.py" which a human can
-  use to send commands to the plugin.
-  
-* The python program "ue-wingman-mcp.py", which an AI
-  can use to send commands to the plugin.
+* The python program "ue-wingman.py"
+
+The python program is actually less than 100 lines of code:
+all it does is package up its command line arguments, send
+them to the plugin, and let the plugin do the work.  Then it
+prints the output.
 
 If you build Unreal from source, the best way to install the
 plugin is to drop the entire UEWingman source folder into
@@ -106,25 +102,6 @@ and no other dependencies.
 To install the human version, ue-wingman.py, just drop it into
 a folder on your PATH.
 
-To install the AI version, ue-wingman-mcp.py, you have to
-usually set up some config file for your AI agent.  I use
-Claude Code, for that, you have to create a file ".mcp.json"
-in your project folder, and it needs to have this inside it:
-
-```
-{
-  "mcpServers": {
-    "ue-wingman": {
-      "command": "python3",
-      "args": ["Plugins/UEWingman/ue-wingman-mcp.py"]
-    }
-  }
-}
-```
-
-You can usually ask your AI agent for help creating this
-config file.
-
 ## The "User Manual"
 
 You might be interested in seeing the "user manual" for the
@@ -135,18 +112,17 @@ $ ue-wingman.py Documentation_Manual
 ```
 
 Of course, you're not the intended user: your AI agent is.
-When the AI agent starts up ue-wingman-mcp, it is
-automatically told to read the user manual.  From there, the
-User Manual says, among other things, that the AI agent can
-get a listing of built-in commands.  You can see that too:
+You should put a note into your agent's system prompt to
+let it know about the ue-wingman.py command, and to let
+it know that it can type ue-wingman.py Documentation_Manual.
+This in turn will tell your agent about this command:
 
 ```
 $ ue-wingman.py Documentation_Commands
 ```
 
-With these two commands at your disposal, you'll have a better
-understanding of what exactly your AI agent is doing with this
-plugin, and how it all works.
+Using these commands, you can learn more about what this
+plugin can do.
 
 ## Fun things to Try