> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/gum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.flatredball.com/gum/code/monogame/known-issues.md). # Known Issues Gum projects can be loaded and used in MonoGame projects with most features available. The following lists the missing features and known issues as of January 2025. These features are actively being worked on and in the future these will be improved. If you are waiting for a particular feature for your game and would like to see it prioritized, please make a request on the Gum Discord or in a GitHub issue. ## Missing Features * Variable References - note that variable references propagate variable assignments, so you can use variable references in your project, but they will not update in real-time in your game * Skia is not directly supported, a NuGet package exists to add ColoredCircle, Arc, and RoundedRectangle. For more information see the [Apos.Shapes](/gum/code/standard-visuals/shapes-apos.shapes.md) page. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.flatredball.com/gum/code/monogame/known-issues.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.