> For the complete documentation index, see [llms.txt](https://wiki.thescriptersguild.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.thescriptersguild.com/knowledge/scripting/bugs.md).

# Bugs

- ["Killed Unit Position" Pin in On AI Unit Killed Node is Scaled 10x Smaller](https://wiki.thescriptersguild.com/knowledge/scripting/bugs/killed-unit-position-pin-in-on-ai-unit-killed-node-is-scaled-10x-smaller.md): The Killed Unit Position pin in the On AI Unit Killed node outputs coordinates that are 10x smaller than standard Forge coordinates.
- [Get Objects In Prefab Node Returns Only Parent Object](https://wiki.thescriptersguild.com/knowledge/scripting/bugs/get-objects-in-prefab-node-returns-only-parent-object.md): In Custom Games, retrieving objects via the Get Objects In Prefab node may only affect the parent object instead of all constituent parts. A simple fix is available.
- [Invisible Nodes or Connections](https://wiki.thescriptersguild.com/knowledge/scripting/bugs/invisible-nodes-or-connections.md)
- [Unpredictable Node Selection Movement](https://wiki.thescriptersguild.com/knowledge/scripting/bugs/unpredictable-node-selection-movement.md)


---

# 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, and the optional `goal` query parameter:

```
GET https://wiki.thescriptersguild.com/knowledge/scripting/bugs.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.