> For the complete documentation index, see [llms.txt](https://g3m.gitbook.io/g3mwiki/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://g3m.gitbook.io/g3mwiki/main/g3mlib/apis-and-examples/faq.md). # FAQ ## Does G3MLib launch games or manage mods? No. It supplies DATA and modding APIs. The host manages games, profiles, downloads, backups around play sessions, and its own user interface. ## Can every GameMaker game be edited? Support depends on the file's format and available resources. A readable metadata header does not guarantee that every resource or compiled-code variant supports editing. Keep warnings and test the written result with its game. ## Are `.csx` inputs accepted by every patch method? No. G3MTool provides a script execution layer around the library. A direct library host must execute its scripts through the chosen scripting environment and supply the resulting DATA to the patch workflow. ## Why does a merge succeed with conflicts? The service can resolve an overlap by priority and still report it. Inspect TotalConflicts and the report; successful processing does not establish that both mods' intended behavior survives. ## Why are dialogs unavailable in ProjectContext scripts? The default library context has no application UI. Connect text callbacks or provide an interactive scripting host. Do not rely on G3MTool CLI's prompt return values for a different host. ## Do I need xdelta for ordinary resource patching? Not for every operation. Binary patch creation/application and embedded fallback paths need a configured executable. The host is responsible for supplying it. ## Can I distribute a DATA file or exported sprites? The library's license does not grant rights to the game's assets. Follow the game's and content owners' redistribution terms. A patch can avoid shipping complete originals, but its payload still needs review. --- # 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://g3m.gitbook.io/g3mwiki/main/g3mlib/apis-and-examples/faq.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.