> For the complete documentation index, see [llms.txt](https://modding.corekeepergame.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://modding.corekeepergame.com/known-issues.md). # Known Issues This page lists all known issues. #### Ghost Component cap Creating more than a handful new ghost components results in the game crashing. ~~This will be fixed in the next stability patch, most likely early next week~~. This issue has been fixed, but a related issue has appeared where exceeding the player archetypes' limit causes similar crashes. The workaround for this is the same as before - to have less components. We are investigating the issue. #### SDK Error: LimitExceeded This happens when you are trying to upload an art asset to Steam Workshop that exceeds their file limit. This limit is set to 5MB by Steam and we are currently working on implementing this file limit on the SDK side as well. For now, please refrain from using images that are larger than 5MB. --- # 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://modding.corekeepergame.com/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.