> For the complete documentation index, see [llms.txt](https://docs.flatredball.com/flatredball/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/flatredball/contributing/adding-new-platforms.md).

# Adding New Platforms

## Introduction

This guide provides instructions for adding a new platform. This could include a new .NET version (such as going to .NET 10) or it could be a new runtime (such as KNI).

## 1. Adding a Template

To add a new template, open the Templates folder and copy an existing template, or add a new project from scratch. Note that the Game1 will get copied over so the contents of Game1 do not matter, and should not differ per platform. If certain platforms (like iOS) require custom code in Game1, you need to add #if blocks.

## 2. Modifying Game1Copier

Open Game1Copier.sln and find Program.cs.

Add information about the newly-created template to the templates list. Rebuild the project, then copy the built .exe to root Templates folder so the new template is copied.

## 3. Modifying BuildServerUploader

Open BuildServerUploader.cs and modify AllData.cs to add the new engine.

## 4. Modifying Glue

Update EmptyTemplates.cs to include the new template.

## 5. Update Engine.yml

Add the NuGet package building steps


---

# 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/flatredball/contributing/adding-new-platforms.md?ask=<question>&goal=<user_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.