Make the Blueprint finder smart about name clashes and mixed path formats #17
+167
−54
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Implemented logic to handle multiple assets with the same name by prompting the user to select the desired asset. - Enhanced `HandleSpawnBlueprintActor` to support spawning actors from Blueprint assets - Refactored `FindBlueprintAssets` to normalize input paths, handle "Copy Reference" formats, and improve asset filtering using `FARFilter`. - Added support for relative and absolute paths in Blueprint asset searches.
- Added `CreateAssetChoicesResponse` function to `FUnrealMCPCommonUtils` for generating JSON responses with asset choices.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary & Motivation
Generic LLM agents often supply Blueprint identifiers in inconsistent formats (simple names, package paths, Reference strings, etc.), leading to missed or incorrect spawns—especially when duplicate names exist.
This patch adds a normalization layer that aims to resolve input paths as accurately as possible across common formats and, when clashes occur, returns clear choices so users can pick the correct asset.
This issue isn’t confined to this tool; it’s a recurring, predictable challenge when building tools for any LLM‑powered agent. I’m opening this PR to propose a solution and refine it together.
Related Issues
Key Changes
FUnrealMCPCommonUtils::FindBlueprintAssetsFARFiltersearch confined toUBlueprintassets, support for relative/absolute pathsFUnrealMCPEditorCommands::HandleSpawnBlueprintActor• single match → spawns actor
• no match → error JSON
• multiple matches →
choicesarray for user choiceScreenshots – Expected Behavior