startgrid is the developer of the game Endless ATC (also available on Steam and Android).
This github is managed by moderators of the discord server. Please join here.
You can find "raw" airport files here. These are automatically generated files with only the basics. They're not intended as ready-to-play airports, but as a starting point to create a new airport file. You'll have to fix issues with the raw file as well add properties (like SIDs, STARs and runway configurations) yourself. We recommend starting with a simple airport - single runway airports with simple airspace are a good starting point.
Use a text editor, together with the included example.txt file as a guide, to create a working file in the locations folder of the game. In theory, just a runway and an airport code is enough data to create a minimal, playable file. You can always decide to add more detail later. First thing to do is to make sure the '#code = ' item in the [airport1] section is un-commented to make the airport appear in-game at the bottom of the airport menu. So just remove the # at the beginning of that line. Carefully put each item in the correct section, in the same format as the example. Start the game every now and then to make sure it still works as expected.
- Open an issue describing the work you want to do (or want done, but it will be faster if you participate!)
- Fork this repository
- Clone your fork to your computer so you can work on it
- Set this repository to be the upstream repository of your fork
- Ensure your repository has the most recent changes from upstream
- Create a branch in your repository:
git checkout -b iss#/descwhere the open issue and description are both included - Make local changes until your repository contains all completed work
- Commit your changes:
git commit -am 'iss#/desc - closes iss#'Use keywords to assist with linking issues and pull requests - Push to your branch:
git push origin iss#/desc - Submit a pull request from your fork to the upstream repository
Note, many editors and GUI git clients will help and even combine many of these commands. Refer to the documentation for whichever application you are using as well as this guide with any questions. If you are connected to our Discord server, feel free to ask for help in #github-help
We are thrilled to accept new and updated airports. We also would welcome markdown files in the GitHub wiki with gameplay tips - especially for more advanced usage (such as STAR) - and development tips/guidelines. Those who wish to volunteer to test updates before they are finalized should open an issue to volunteer.
Finally, all players, testers, and developers are encouraged to join our Discord server for extra assistance and information.
- All files that have been customized should be placed in the final folder.
- The directory structure below that follows the continent abbreviation found here
- The directory structure should have the four character ICAO code
- The file should have the four character ICAO code, with a .txt extension.
- Alternate configurations should be differentiated by adding "_description", such as IACO_27s.txt
- "Fantasy" or other airports that cannot be placed in this structure should go into final/custom
For example, Zurich airport is placed in
final/EU/LSZH/LSZH.txt. Hong Kong has bothfinal/AS/VHHH/VHHH_mobile.txtandfinal/AS/VHHH/VHHH_PC.txt
It is highly encourage to remove the first seven lines of comments, since we are no longer using an "automatically generated airport file" at this point.
Is it encouraged to cite any references that you used while creating your file, including the airchart, airliner data, and even airport website.
If you wish to include personal information (such as your contact information), this is allowed, although not necessary.
It may be best to add a readme file in markdown format with the same airport code in the same directory with references, information, and a change log (e.g. final/EU/LSZH/LSZH_readme.md)