@uemcp/server 1.12.0 → 1.13.0

package/README.md

@@ -693,6 +693,7 @@ This is intended to let an MCP client resolve the canonical Unreal project ident
 - `create_nav_area` makes a nav area Blueprint under `NavArea` (or one of the stock parents) and reports `generatedClassPath` — the class, not the asset, is what a modifier volume or a link references
 - `add_nav_modifier_volume` places an `ANavModifierVolume` and builds its cube brush through the same actor factory the place-actor panel uses. Without that brush the volume covers nothing, so a non-positive extent is refused rather than placed
 - `add_nav_link` replaces the proxy's default link with the ones the request carries. `left` and `right` are offsets from the actor, the space the level editor's own link handles move in, and the response reports them in world space so a link and the `find_path` that crosses it can be compared directly
+- Detour joins a link only when its two ends lie in the same navmesh tile or neighboring ones. A longer link still builds, connected at one end, so nothing can cross it and the build reports no error; `add_nav_link` says so in `message` when a link spans more than one tile (`TileSizeUU`, 1000 units by default)
 - All three leave the navmesh untouched until the next `build_navigation`, and say so through `rebuildRequired`
 
 ### `find_path` / `test_reachability`
@@ -704,10 +705,10 @@ This is intended to let an MCP client resolve the canonical Unreal project ident
 
 ### `create_smart_object_definition` / `get_smart_object_definition` / `add_smart_object_component`
 
-- Backed by the SmartObjects engine plugin, which MCPBridge enables. When its module is not loaded the three tools answer `state: 'unsupported'` with the reason instead of failing
+- Backed by the SmartObjects engine plugin through the `MCPBridgeSmartObjects` add-on (see [Add-ons](../../plugins/ue-plugin/README.md#add-ons)). Until that add-on is enabled, these tools are hidden
 - A definition is created with its slots in one call: offset and rotation relative to the owning actor, activity tags, an enabled flag and behavior definitions (instanced `USmartObjectBehaviorDefinition` subclasses configured through `params`). Activity tags must already be registered; a definition missing one is refused and nothing is left behind
 - Both the create and the read report `valid` and the engine's `validationMessages`. The Smart Object subsystem refuses to register a component whose definition fails validation, most often a slot with no behavior definition and no default, so `valid: false` means nothing can ever claim it
-- `add_smart_object_component` takes exactly one of `blueprintPath` (the Blueprint is recompiled) or `actorPath` (a placed actor in the editor level). An existing Smart Object component is pointed at the new definition rather than joined by a second, because an actor carrying two registers as two objects; `created` says which happened. The component registers with the subsystem when play begins
+- `add_smart_object_component` takes exactly one of `blueprintPath` (the Blueprint is recompiled) or `actorPath` (a placed actor in the editor level). An existing Smart Object component is pointed at the new definition rather than joined by a second, because an actor carrying two registers as two objects; `created` says which happened. A Blueprint that inherits one from its parent class is refused with `inherited_smart_object_component`, since that component belongs to the parent. The component registers with the subsystem when play begins
 
 ### `create_mass_entity_config` / `edit_mass_entity_config` / `get_mass_entity_config` / `validate_mass_entity_config`
 
@@ -715,13 +716,13 @@ This is intended to let an MCP client resolve the canonical Unreal project ident
 - `edit_mass_entity_config` applies `add`, `remove` and `set` edits in order and reports each one. Traits are named by class (`MassMovementTrait`, `MassLODCollectorTrait`, `MassVisualizationTrait`, `MassStateTreeTrait`, or a `/Script/Module.Class` path), and properties are `{ propertyPath, value }` pairs in exported-text form, the same shape `set_asset_property` takes. Only the config's own traits are edited, never a parent's. A new trait whose properties are rejected is taken back out
 - `get_mass_entity_config` reads the parent and each own trait with its editable properties as exported text, trimmed by encoded size with `truncated` set
 - `validate_mass_entity_config` builds the entity template in the editor world, the way the asset editor's Validate button does, and returns the engine's own error and warning lines verbatim in `messages`
-- Every tool returns `state: 'unsupported'` with a reason when the Mass runtime is not loaded (MCPBridge enables `MassGameplay` and `MassAI`), and validation does the same when the editor world has no Mass entity subsystem
+- Backed by the `MassGameplay` engine plugin through the `MCPBridgeMass` add-on (see [Add-ons](../../plugins/ue-plugin/README.md#add-ons)). Until that add-on is enabled, these tools are hidden. `MassAI` is optional: without it, its traits (`MassStateTreeTrait` and the navigation ones) do not resolve and the tools say so. Validation returns `state: 'unsupported'` with a reason when the editor world has no Mass entity subsystem (`mass.RuntimeSubsystemsEnabled` off)
 
 ### `diagnose_navmesh`
 
 - A read-only audit of the editor level's navmesh: missing `NavMeshBoundsVolume`s, no navigation data or an empty navmesh, disconnected islands, and spawn points that are off the navmesh or cannot path to the first one. Each finding lands in `issues` with a `code`, and `healthy` is true when there are none. Nothing is rebuilt or fixed
 - Islands are the connected components of the Recast polygon graph, nav links included, listed largest walkable area first with poly count, area and bounds. One-way links still join two areas, so a drop-down ledge is not reported as a stray island. `islandCount` stays the full count when `maxIslands` cuts the list
-- Every `PlayerStart` is checked by default; AI spawners have no common base class, so a level's own spawn actors are named in `spawnActorPaths`. Player starts come first, and the first spawn on the navmesh is the anchor every other spawn is path-tested against with the same query `find_path` runs. Spawns on different islands are reported unreachable from the island map without a search
+- Every `PlayerStart` is checked by default; AI spawners have no common base class, so a level's own spawn actors are named in `spawnActorPaths`. Player starts come first, and the first spawn on the navmesh is the anchor every other spawn is path-tested against with the same query `find_path` runs. Spawns on different islands are reported unreachable from the island map without a search. A spawn the anchor reaches is also path-tested back to it, and one with no way back (past a one-way link) is reported as `spawn_cannot_return`. Every spawn is checked; only the returned `spawnPoints` list is capped
 - An island no spawn point stands on is reported as `island_without_spawn`: the isolated platform an AI can be placed on but never walk off. A level with no navmesh at all reports that once rather than blaming every spawn point for it
 
 ## MCP Resources

package/dist/index.mjs

@@ -11262,7 +11262,8 @@ const BRIDGE_NAV_DIAGNOSTIC_ISSUE_CODES = [
 	"island_without_spawn",
 	"spawn_not_found",
 	"spawn_off_navmesh",
-	"spawn_unreachable"
+	"spawn_unreachable",
+	"spawn_cannot_return"
 ];
 const BRIDGE_NAV_SPAWN_POINT_KINDS = ["player_start", "actor"];
 const bridgeDiagnoseNavmeshRequestSchema = z.object({
@@ -11293,7 +11294,8 @@ const navDiagnosticSpawnPointSchema = z.object({
 	onNavMesh: z.boolean(),
 	pathLength: z.number().optional(),
 	projectedLocation: navPointSchema.optional(),
-	reachableFromAnchor: z.boolean()
+	reachableFromAnchor: z.boolean(),
+	returnsToAnchor: z.boolean()
 });
 const navDiagnosticIssueSchema = z.object({
 	actorPath: z.string().optional(),
@@ -11385,8 +11387,8 @@ const bridgeAddSmartObjectComponentRequestSchema = bridgeAddSmartObjectComponent
 	path: ["blueprintPath"]
 });
 const bridgeSmartObjectSlotReportSchema = z.object({
-	activityTags: z.array(z.string()).max(16),
-	behaviorDefinitions: z.array(z.string()).max(8),
+	activityTags: z.array(z.string()),
+	behaviorDefinitions: z.array(z.string()),
 	enabled: z.boolean(),
 	index: z.number().int().min(0),
 	name: z.string(),
@@ -11394,9 +11396,9 @@ const bridgeSmartObjectSlotReportSchema = z.object({
 	rotation: bridgeRotatorSchema
 });
 const smartObjectDefinitionReportFields = {
-	activityTags: z.array(z.string()).max(16),
-	defaultBehaviorDefinitions: z.array(z.string()).max(8),
-	slots: z.array(bridgeSmartObjectSlotReportSchema).max(32),
+	activityTags: z.array(z.string()),
+	defaultBehaviorDefinitions: z.array(z.string()),
+	slots: z.array(bridgeSmartObjectSlotReportSchema),
 	valid: z.boolean(),
 	validationMessages: z.array(z.string()).max(32)
 };
@@ -11611,7 +11613,7 @@ function createBridgeValidateMassEntityConfigRequest(assetPath, requestId = rand
 }
 //#endregion
 //#region src/version.ts
-const SERVER_VERSION = "1.12.0";
+const SERVER_VERSION = "1.13.0";
 //#endregion
 //#region src/bridgeSocketClient.ts
 var BridgeSocketError = class extends Error {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@uemcp/server",
-  "version": "1.12.0",
+  "version": "1.13.0",
   "description": "MCP server for making Unreal Engine and C++ development easier",
   "type": "module",
   "main": "dist/index.mjs",