> For the complete documentation index, see [llms.txt](https://morningheartgames.gitbook.io/docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://morningheartgames.gitbook.io/docs/gameplay-ability-toolkit/integrations/game-creator/troubleshooting-verification.md).

# Troubleshooting And Verification

Use this page when a skill does not work in-editor, when a Game Creator graph cannot see nodes, or when you are preparing bridge changes for release.

## Symptoms

| Symptom                                       | Check                                                                                                                   |
| --------------------------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
| Game Creator nodes do not appear              | Confirm Game Creator Core is installed, then confirm `GAS_ENABLE_GAMECREATOR` and `GAS_HAS_UNITASK` in the Dashboard.   |
| Game Creator assemblies are excluded          | Confirm the extension is enabled and the selected build target has the required scripting define symbols.               |
| Instruction cannot find gameplay state        | Confirm the target GameObject has an `AbilitySystemComponent`.                                                          |
| Character-specific behavior fails             | Confirm the target GameObject has a Game Creator `Character`.                                                           |
| `Only If` cannot create a condition           | Save the ability asset first. Embedded modules need an asset path.                                                      |
| Event editor opens but no logic runs          | Add instructions under `Run` or add an enabled module under `Only If` whose conditions pass.                            |
| One click advances multiple combo stages      | Confirm both Press and Release Triggers exist and the actor has `GameCreatorAbilityInputGate`.                          |
| Target confirm also triggers another skill    | Keep `Input > Suppress Presses While Targeting` enabled and ensure the targeting tag is active during selection.        |
| Melee ability cancels immediately             | Confirm every swing montage has `Hit Start` and `Hit End` markers.                                                      |
| Light or heavy hit timing feels wrong         | Move montage markers. The recipe uses marker timing.                                                                    |
| Projectile does not spawn                     | Confirm projectile mode, prefab, spawn offsets, and cast notify settings.                                               |
| Falling projectile impacts at the wrong point | Confirm the targeting result writes the expected target point before cast completes.                                    |
| Channel does not stop                         | Confirm the release trigger fires and `End On Release` is enabled.                                                      |
| Channel cue stays active                      | Confirm the ability ends, release is received, and cue cleanup runs.                                                    |
| Montage does not play                         | Confirm the actor has a `MontagePlayer`, valid montage tracks, and either a Game Creator `Character` or Animator route. |
| Effect does not clean up                      | Remove the last applied effect explicitly or use normal effect duration and stack settings.                             |

## Diagnostics

Open:

```
Tools > Gameplay Ability Toolkit > Dashboard > Game Creator
```

Use diagnostics to check:

* required defines;
* Game Creator assembly visibility;
* Visual Scripting node metadata;
* icon and TIcon classes;
* common authoring configuration.

If a node is visible in Game Creator, it should have current `[Title]`, `[Category]`, `[Description]`, and icon metadata.

## Manual QA

For a playable project pass:

1. Create a new Game Creator Ability.
2. Switch through all seven execution modes and confirm the visible recipe steps update.
3. Save the asset, open an event, add one `Run` instruction, and add one `Only If` condition.
4. Reopen the asset and confirm embedded modules persist under the expected event phase.
5. Add a saved Visual Scripting module with a matching phase and confirm duplicate references are ignored.
6. Play the Game Creator Arena scene.
7. Test all listed controls and compare ability behavior with the regular Arena.

For a package maintenance pass:

1. Check asmdef define constraints.
2. Check Dashboard diagnostics.
3. Check Visual Scripting node metadata.
4. Check Game Creator Arena editor and play mode tests when Unity is available.
5. Check GitBook links and image paths.

## Static Documentation Checks

Run from the repository root:

```powershell
git diff --check
```

Check that nested `SUMMARY.md` links resolve:

```powershell
$book = "Assets/unity-gas-pure/GameplayAbilityToolkit"
$summary = Join-Path $book "SUMMARY.md"
Select-String -Path $summary -Pattern '\]\(([^)]+)\)' | ForEach-Object {
    $link = [regex]::Match($_.Line, '\]\(([^)]+)\)').Groups[1].Value
    if ($link -notmatch '^(https?:|#)' -and -not (Test-Path (Join-Path $book $link))) {
        throw "Missing SUMMARY link: $link"
    }
}
```

Check image paths from nested pages:

```powershell
Get-ChildItem "Assets/unity-gas-pure/GameplayAbilityToolkit/Documentation/integrations/game-creator" -Filter *.md |
    Select-String -Pattern '\]\(([^)]+images[^)]+)\)' |
    ForEach-Object {
        $path = [regex]::Match($_.Line, '\]\(([^)]+)\)').Groups[1].Value
        $full = Join-Path $_.Path "..\\$path"
        if (-not (Test-Path (Resolve-Path $full -ErrorAction SilentlyContinue))) {
            throw "Missing image: $($_.Path) -> $path"
        }
    }
```

Check that removed package-specific Game Creator names do not return. Keep the removed-name pattern in your local release checklist or CI script, not in the public docs:

```powershell
rg -n "<removed Game Creator bridge names>" Assets/unity-gas-pure/GameplayAbilityToolkit/Documentation
```

## Unity Tests

Recommended EditMode assemblies:

```
GameplayAbilityToolkit.GameCreator.Tests
GameplayAbilityToolkit.Demo.GameCreatorArena.EditorTests
GameplayAbilityToolkit.Tests.Editor
```

Recommended PlayMode assembly:

```
GameplayAbilityToolkit.Demo.GameCreatorArena.Tests
```

Example targeted commands:

```
Unity -batchmode -projectPath <project> -runTests -testPlatform editmode -testFilter GameplayAbilityToolkit.Demo.GameCreatorArena.EditorTests.GameCreatorArenaAuthoringTests.SceneHasValidArenaTrainingAuthoring
Unity -batchmode -projectPath <project> -runTests -testPlatform playmode -testFilter GameplayAbilityToolkit.Demo.GameCreatorArena.Tests.GameCreatorArenaTrainingSmokeTests.SceneStartsInPlayModeAndAcceptsSkillInputs
```


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://morningheartgames.gitbook.io/docs/gameplay-ability-toolkit/integrations/game-creator/troubleshooting-verification.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.