diff --git a/README.md b/README.md
index 4579112..53b4e17 100644
--- a/README.md
+++ b/README.md
@@ -58,7 +58,7 @@ This manual is for Windows 10/11 installations. On other operating systems these
1. Run `aerofly-missions` in the open terminal to convert `main.mcf` to a `tmc` file (see below).
1. Grab your exported `tmc` file with all your settings converted into a single mission file. This file can now be placed into the custom mission directory in Aerofly FS 4.
-Be aware that right now Aerofly FS 4 accepts custom missions exclusively from within `…\Aerofly FS 4 Flight Simulator\missions\custom_missions.tmc`. You will need to replace the file located there or append your missions to this file. See [installation instructions](https://fboes.github.io/aerofly-missions/docs/generic-installation.html) on how to get started.
+Be aware that right now Aerofly FS 4 accepts custom missions exclusively from within `…\Aerofly FS 4 Flight Simulator\missions\custom_missions_user.tmc`. See [installation instructions](https://fboes.github.io/aerofly-missions/docs/generic-installation.html) on how to get started.
See the [custom missions documentation](docs/custom-missions.md) for more information. See also [more sources for flight plans on the Internet](docs/importing-flightplans.md).
diff --git a/dist/Cli/Arguments.js b/dist/Cli/Arguments.js
index 531be2f..129559c 100644
--- a/dist/Cli/Arguments.js
+++ b/dist/Cli/Arguments.js
@@ -148,7 +148,7 @@ export class Arguments {
}
helpText(c) {
return `${c.lightBlue}Usage: nodejs index.js [PARAMETERS...]${c.reset}
- Convert Aerofly FS 4 main.mcf file into a custom_missions.tmc file.
+ Convert Aerofly FS 4 main.mcf file into a custom_missions_user.tmc file.
Parameters:
${c.lightBlue} -s, --source ${c.reset} Location of the main.mcf; defaults to \`${this.source}\`
diff --git a/dist/Export/Markdown.js b/dist/Export/Markdown.js
index 4c6d3d7..de28948 100644
--- a/dist/Export/Markdown.js
+++ b/dist/Export/Markdown.js
@@ -20,7 +20,7 @@ export class Markdown extends Outputtable {
}
return fields;
}
- toString(filename = "custom_missions.tmc") {
+ toString(filename = "custom_missions_user.tmc") {
const m = this.mission;
const s = new SkyVector(m);
const total_distance = m.distance;
diff --git a/dist/Web/ComponentsDownloadButtons.js b/dist/Web/ComponentsDownloadButtons.js
index 7ffce43..b0c4574 100644
--- a/dist/Web/ComponentsDownloadButtons.js
+++ b/dist/Web/ComponentsDownloadButtons.js
@@ -7,7 +7,7 @@ import { XplaneFmsExport } from "../Import/XplaneFms.js";
export class ComponentsDownloadButtons extends HTMLElement {
constructor() {
super();
- this.innerHTML = `
+ this.innerHTML = `
diff --git a/dist/index.html b/dist/index.html
index 0bf5e1c..64c7e1a 100644
--- a/dist/index.html
+++ b/dist/index.html
@@ -34,7 +34,7 @@
-
The Aerofly Missionsgerät converts Aerofly FS 4'smain.mcf (and other flight plan file formats) into a custom_missions.tmc file (and other flight plan file formats), using your current flight plan and other settings to generate a shareable mission.
+
The Aerofly Missionsgerät converts Aerofly FS 4'smain.mcf (and other flight plan file formats) into a custom_missions_user.tmc file (and other flight plan file formats), using your current flight plan and other settings to generate a shareable mission.
Step 1: Load flight plan file
diff --git a/docs/README.md b/docs/README.md
index b64220e..82647e1 100644
--- a/docs/README.md
+++ b/docs/README.md
@@ -3,7 +3,7 @@
1. [Building a custom missions file](./custom-missions.md)
1. [Flight plan output](./flightplan.md)
1. [Sources for flight plans](./importing-flightplans.md)
-1. [Generic `custom_missions.tmc` installation instructions](./generic-installation.md)
+1. [Generic `custom_missions_user.tmc` installation instructions](./generic-installation.md)
On a more theoretical level:
diff --git a/docs/carls_homecoming/README.md b/docs/carls_homecoming/README.md
index b8476bd..42c727a 100644
--- a/docs/carls_homecoming/README.md
+++ b/docs/carls_homecoming/README.md
@@ -6,11 +6,11 @@ Being a close friend to him, your name came up in his testament. You are to carr
So take a seat in Carl's Pitts S-2, and starting in Hamburg travel up to Denmark, Sweden and finally Finnland.
-> This is a custom missions file for [Aerofly FS 4](https://www.aerofly.com/). Download [`custom_missions.tmc`](./custom_missions.tmc) and see [installation instructions](https://fboes.github.io/aerofly-missions/docs/generic-installation.html) on how to get started.
+> This is a custom missions file for [Aerofly FS 4](https://www.aerofly.com/). Download [`carls_homecoming.tmc`](./carls_homecoming.tmc) and see [installation instructions](https://fboes.github.io/aerofly-missions/docs/generic-installation.html) on how to get started.
## The tour
-Each leg is about 130 kilometres (70 nautical miles). Which is just as well, because the Pitts was never built for cross-country flights, with its tiny fuel tank limited to about 120 nautical miles of full throttle flight.
+Each leg is about 130 kilometers (70 nautical miles). Which is just as well, because the Pitts was never built for cross-country flights, with its tiny fuel tank limited to about 120 nautical miles of full throttle flight.
Your flights:
diff --git a/docs/carls_homecoming/custom_missions.tmc b/docs/carls_homecoming/carls_homecoming.tmc
similarity index 100%
rename from docs/carls_homecoming/custom_missions.tmc
rename to docs/carls_homecoming/carls_homecoming.tmc
diff --git a/docs/generic-installation.md b/docs/generic-installation.md
index 2b62bf5..145e9ae 100644
--- a/docs/generic-installation.md
+++ b/docs/generic-installation.md
@@ -1,18 +1,16 @@
-# ![](favicon-64x64.png) `custom_missions.tmc` installation instructions
+# ![](favicon-64x64.png) `custom_missions_user.tmc` installation instructions
To install a custom missions file in Aerofly FS 4:
1. Open a file explorer in your Aerofly FS 4 game folder.
2. Open up the `missions` folder.
-3. Rename `custom_missions.tmc` to any other file name,
- e.g. `_custom_missions.tmc`.
-4. Put the new `.tmc` file into the `missions` folder,
- and rename it to `custom_missions.tmc`.
-5. On starting Aerofly FS 4, all your custom missions will be loaded from the
- new `custom_missions.tmc`.
+3. Put the new `.tmc` file into the `missions` folder,
+ and rename it to `custom_missions_user.tmc`.
+4. On starting Aerofly FS 4, your custom missions will be loaded from the
+ new `custom_missions_user.tmc`.
-To revert back to the original custom missions file, simply delete the new file
-and rename the old file `_custom_missions.tmc` back to `custom_missions.tmc`.
+Be aware that there is only on `custom_missions_user.tmc` at any given time.
+If you have multiple mission files, rename them accordingly and keep backups of the original files.
In case your Aerofly FS 4 installation gets damaged in this process, consider
a fresh installation.
diff --git a/src/Cli/Arguments.ts b/src/Cli/Arguments.ts
index 22a3489..fdda64d 100644
--- a/src/Cli/Arguments.ts
+++ b/src/Cli/Arguments.ts
@@ -167,7 +167,7 @@ export class Arguments {
helpText(c: BashColors): string {
return `${c.lightBlue}Usage: nodejs index.js [PARAMETERS...]${c.reset}
- Convert Aerofly FS 4 main.mcf file into a custom_missions.tmc file.
+ Convert Aerofly FS 4 main.mcf file into a custom_missions_user.tmc file.
Parameters:
${c.lightBlue} -s, --source ${c.reset} Location of the main.mcf; defaults to \`${this.source}\`
diff --git a/src/Export/Markdown.ts b/src/Export/Markdown.ts
index 3555706..b372b22 100644
--- a/src/Export/Markdown.ts
+++ b/src/Export/Markdown.ts
@@ -26,7 +26,7 @@ export class Markdown extends Outputtable {
return fields;
}
- toString(filename = "custom_missions.tmc"): string {
+ toString(filename = "custom_missions_user.tmc"): string {
const m = this.mission;
const s = new SkyVector(m);
diff --git a/src/Web/ComponentsDownloadButtons.ts b/src/Web/ComponentsDownloadButtons.ts
index ec07295..072a59c 100644
--- a/src/Web/ComponentsDownloadButtons.ts
+++ b/src/Web/ComponentsDownloadButtons.ts
@@ -12,7 +12,7 @@ export class ComponentsDownloadButtons extends HTMLElement {
constructor() {
super();
- this.innerHTML = `
+ this.innerHTML = `