OpenParable
Skip to content
← Back to skills

Uloop Find Game Objects

Apps & Automation
uloop-find-game-objects

Uloop Find Game Objects is an Agent Skill for apps & automation published in the kurotu/VRCQuestTools repository on GitHub: a SKILL.md instruction file an AI agent can load to do this task.

Find or inspect Unity GameObjects, especially objects the user currently selected in the Hierarchy. Use for details, components, tags, layers, or name/path searches.

View on GitHub ↗
QUICK START

How to use this skill

Bring this guide into your coding agent with a prompt tailored to the tool you use.

  1. Open your project in Codex.
  2. Copy and paste the prompt below.
  3. Review files and risks before approving any action.
Prompt to paste
Inspect the Agent Skill at https://github.com/kurotu/VRCQuestTools/blob/HEAD/.claude/skills/uloop-find-game-objects/SKILL.md and all supporting files. Report provenance, permissions, scripts, dependencies, and security risks. Propose an exact installation into .agents/skills/uloop-find-game-objects, but wait for my approval before writing files or running scripts.

Copying this prompt does not install or run the skill. Review third-party files before use.

npx --yes [email protected] find-game-objects

Find GameObjects with search criteria or get details for currently selected Hierarchy objects.

Use this before execute-dynamic-code when identifying or inspecting selected GameObjects. Use get-hierarchy instead when you need the child tree, parent-child structure, or descendants under the selection.

Usage

npx --yes [email protected] find-game-objects [options]

Parameters

ParameterTypeDefaultDescription
--name-patternstring-Name pattern to search
--search-modestringExactSearch mode: Exact, Path, Regex, Contains, Selected
--required-componentsarray-Required components
--tagstring-Tag filter
--layerinteger-Layer filter (layer number)
--max-resultsinteger20Maximum number of results
--include-inactivebooleanfalseInclude inactive GameObjects
--include-inherited-propertiesbooleanfalseInclude inherited properties in results

Search Modes

ModeDescription
ExactExact name match (default)
PathHierarchy path search (e.g., Canvas/Button)
RegexRegular expression pattern
ContainsPartial name match
SelectedGet currently selected GameObjects in Unity Editor

Global Options

OptionDescription
--project-path <path>Optional. Use only when the target Unity project is not the current directory.

Examples

# Find by name
npx --yes [email protected] find-game-objects --name-pattern "Player"

# Find with component
npx --yes [email protected] find-game-objects --required-components Rigidbody

# Find by tag
npx --yes [email protected] find-game-objects --tag "Enemy"

# Regex search
npx --yes [email protected] find-game-objects --name-pattern "UI_.*" --search-mode Regex

# Get selected GameObjects
npx --yes [email protected] find-game-objects --search-mode Selected

# Get selected including inactive
npx --yes [email protected] find-game-objects --search-mode Selected --include-inactive

Output

Returns JSON with:

  • results (array): Matching GameObjects, each containing:
    • name (string): GameObject name
    • path (string): Hierarchy path (e.g., Canvas/Panel/Button)
    • isActive (boolean): Active state in hierarchy
    • tag (string): GameObject tag
    • layer (number): Layer index
    • components (array): Each entry has type (short name, e.g., Rigidbody), fullTypeName (e.g., UnityEngine.Rigidbody), and properties (array of Inspector-visible {name, type, value} pairs)
  • totalFound (number): Number of results returned inline, or number exported for multi-selection file output. For search modes, this is after --max-results clipping and serialization.
  • errorMessage (string): Top-level failure summary (empty on success)
  • processingErrors (array): Selected-mode per-GameObject serialization failures, each {gameObjectName, gameObjectPath, error}. Omitted/null or empty on clean runs.

Multi-selection file export

For Selected mode with multiple successfully serialized GameObjects, inline results is not populated and the data is written to a file instead. Two extra fields appear:

  • resultsFilePath (string): Relative path under .uloop/outputs/FindGameObjectsResults/
  • message (string): Human-readable summary (e.g., "5 GameObjects exported")

Single-selection and search-mode calls (Exact, Path, Regex, Contains) always return inline. No selection (Selected mode with empty selection) returns empty results plus a message.