Merge branch 'main' into docs/gitbook-preprocessor

9 files changed, 85 insertions, 11 deletions

diff --git a/.github/.markdownlinkcheck.json b/.github/.markdownlinkcheck.json
index 3749dee..06df66b 100644
--- a/.github/.markdownlinkcheck.json
+++ b/.github/.markdownlinkcheck.json
@@ -10,6 +10,9 @@
             "pattern": "https://forum.manjaro.org/t/howto-troubleshoot-crackling-in-pipewire/82442"
         },
         {
+            "pattern": "https://taskinoz.com/northstar/"
+        },
+        {
             "pattern": "https://wiki.archlinux.org/title/PulseAudio/Troubleshooting#Glitches.2C\\_skips\\_or\\_crackling"
         }
     ]
diff --git a/.github/workflows/linkcheck.yml b/.github/workflows/linkcheck.yml
index e97f01e..2dcc5c9 100644
--- a/.github/workflows/linkcheck.yml
+++ b/.github/workflows/linkcheck.yml
@@ -6,7 +6,7 @@ jobs:
     runs-on: ubuntu-latest
     steps:
       - name: Checkout
-        uses: actions/checkout@v3
+        uses: actions/checkout@v4
       - name: md-linkcheck
         uses: gaurav-nelson/github-action-markdown-link-check@v1
         with:
diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md
index 0492653..bc359b2 100644
--- a/docs/SUMMARY.md
+++ b/docs/SUMMARY.md
@@ -39,6 +39,7 @@
   * [Best practices](hosting-a-server-with-northstar/dedicated-server/best-practices.md)
   * [Hosting on Windows](hosting-a-server-with-northstar/dedicated-server/hosting-on-windows.md)
   * [Hosting on Linux](hosting-a-server-with-northstar/dedicated-server/hosting-on-linux.md)
+* [Hosting a Local-only Server](hosting-a-server-with-northstar/local-only-server.md)
 * [Server settings](hosting-a-server-with-northstar/server-settings/README.md)
   * [Startup arguments](hosting-a-server-with-northstar/server-settings/startup-args.md)
   * [ConVars](hosting-a-server-with-northstar/server-settings/convars.md)
@@ -67,6 +68,7 @@
 
 ## Other
 
-* [Helping](helping.md)
-* [Discord moderation](other/moderation.md)
+* [Helping](other/helping.md)
+* [Discord moderation](other/moderation/README.md)
+  * [Rules](other/moderation/rules.md)
 * [Credits](other/credits.md)
diff --git a/docs/hosting-a-server-with-northstar/local-only-server.md b/docs/hosting-a-server-with-northstar/local-only-server.md
new file mode 100644
index 0000000..74ba815
--- /dev/null
+++ b/docs/hosting-a-server-with-northstar/local-only-server.md
@@ -0,0 +1,16 @@
+# Hosting a Local-Only Server
+
+If you just want to host server (listen or dedicated) for people in your local network (as in computer network, not the in-game Networks system), you can simply not enable port-forwarding and set `ns_auth_allow_insecure` to `1` in the `autoexec_ns_server.cfg`.
+
+This way players can connect to your server directly by using the `connect` command with the local IP of your server, e.g. `connect 192.168.420.500` (replace with actual local IP of your server).
+
+
+{% hint style="info" %}
+Loadouts are saved by the server and connecting to a server directly using `connect` means that the loadout is not loaded from masterserver. This means your loadouts will be reset while playing on said server.
+
+You should see your saved loadouts again when leaving the local-only server
+{% endhint %}
+
+{% hint style="info" %}
+Even with local-only servers you still need an internet connection to authenticate your account and game ownership with masterserver.
+{% endhint %}
diff --git a/docs/installing-northstar/troubleshooting.md b/docs/installing-northstar/troubleshooting.md
index 967e7ed..9fa10f3 100644
--- a/docs/installing-northstar/troubleshooting.md
+++ b/docs/installing-northstar/troubleshooting.md
@@ -77,12 +77,12 @@ On newer Intel CPUs you might see a message like this
 
 > "Contacting Respawn servers.../Data Center: Searching..."
 
-If you are seeing this in the main menu of TF|2 and have a 10th or 11th generation Intel CPU this is a bug which has a simple fix:
+If you are seeing this in the main menu of TF|2 and have a 10th generation or newer Intel CPU this is a bug which has a simple fix:
 
 In the Windows Start menu on the bottom left search for "Edit the system environment variables" and open the program. In the "advanced" tab click on "Environment Variables..." near the bottom.\
-In System Variables (not user variables) click "New..." and add a new system variable where the variable name is `OPENSSL_ia32cap` and the value is `~0x200000200000000`. Make sure to click OK to apply the changes. Finally restart your device and you should be good to go.
+In System Variables (not user variables) click "New..." and add a new system variable where the variable name is `OPENSSL_ia32cap` and the value is `0x200000200000000`. Make sure to click OK to apply the changes. Finally restart your device and you should be good to go.
 
-If you're on Linux, you can set the appropriate environment variable via `env OPENSSL_ia32cap=~0x20000000 %command%`.
+If you're on Linux, you can set the appropriate environment variable via `env OPENSSL_ia32cap=0x20000000 %command%`.
 
 **Note:** This issue is not exclusive to Northstar client but also affects the vanilla version, so if you only get it on Northstar there might be a different problem at hand as well. In fact it's not even unique to Titanfall 2 either.
 
diff --git a/docs/helping.md b/docs/other/helping.md
index e12bb4e..86a8900 100644
--- a/docs/helping.md
+++ b/docs/other/helping.md
@@ -1,7 +1,7 @@
 # Helping
 
 This section is meant mostly for those that will be actively helping others in the Northstar Discord server or otherwise.
-If you've somehow stumbled upon this page trying to fix an issue for yourself, you should try checking the [troubleshooting page](installing-northstar/troubleshooting.md) instead. 
+If you've somehow stumbled upon this page trying to fix an issue for yourself, you should try checking the [troubleshooting page](../installing-northstar/troubleshooting.md) instead. 
 If you're a helper, it also isn't a bad idea to look at this page a few times and try to have a rough idea of the things that are on it.
 
 When helping a user, please try to move them to the `#help` channel to create a ticket in order to keep public channels less cluttered. 
@@ -34,13 +34,13 @@ This entire section only applies to users with `ticket-staff`+ roles who can see
 
 The tickets have a fairly straightforward way of operating.
 When a user clicks on a button to open a ticket they're greeted with the following screen:\
-![The information fields for opening a ticket](images/ticket-information-popup.png)
+![The information fields for opening a ticket](../images/ticket-information-popup.png)
 
 If you or the end user are curious about the difference, a staff ticket can be viewed by anyone with the helper role or above, while a public ticket can be viewed by anyone with the ticket-staff role or above
 
 Once they hit a button to open a ticket, they will fill out the popup with information which will later be shared in their ticket as a message sent as an embed by the ticket bot. 
 This will be the first message in the channel and will look something similar to this:\
-![The embed sent in a ticket with the information filled out by the user](images/ticket-open-message.png)
+![The embed sent in a ticket with the information filled out by the user](../images/ticket-open-message.png)
 
 Note the buttons below the embed.\
 Hitting `Close` will close the ticket without a reason for closing it.\
@@ -59,7 +59,7 @@ There are 3 major slash commands used for tickets. These are `/close`, `/closere
 You may have noticed that `/closerequest` has been skipped. That's because there's sort of a "etiquette" surrounding it.
 
 Generally, you _should_ use `/closerequest` for closing a ticket. There's much less chance the end user gets upset, and it can be denied last minute if another issue comes up.\
-![What using the `/closerequest` command looks like](images/closerequest.png)
+![What using the `/closerequest` command looks like](../images/closerequest.png)
 
 From here, the user can accept the close request, which in turn closes the ticket, or deny the close request, while results in an edited embed telling you they denied it.
 
diff --git a/docs/other/moderation.md b/docs/other/moderation/README.md
index 2280845..2280845 100644
--- a/docs/other/moderation.md
+++ b/docs/other/moderation/README.md
diff --git a/docs/other/moderation/rules.md b/docs/other/moderation/rules.md
new file mode 100644
index 0000000..59d25f7
--- /dev/null
+++ b/docs/other/moderation/rules.md
@@ -0,0 +1,53 @@
+# Rules
+
+This is a copy of the current list of rules on the Northstar Discord server.
+They are copied here for transparency reasons so any change to them can be tracked and easily observed.
+
+In particular you can check changes to the rules on GitHub using the following link: https://github.com/R2Northstar/NorthstarWiki/commits/main/docs/other/moderation/rules.md
+
+```markdown
+This is a public server that anyone is welcome to join. As such, we expect everybody who participates to keep things civil. To that end, we've established some guidelines for this server. Failing to follow these rules may result in your posts being removed, limitations of your permissions in channels, or removal from this server. ──────────────────────────────────────────────────────────────────────────────────────────────────────
+
+**1. Be respectful.** This includes insults, harassment, or otherwise hateful conduct. If you disagree with somebody, don't be uncivilized about it.
+**2. No NSF(W/L) content.** We all have to sleep at night. If you post content that would get you fired at work, you're going to get the boot.
+**3. No illicit activity.** This includes account trading / selling, piracy, witch hunting, or any discussion of illegal or otherwise unseemly activity.
+**4. No spam.** This includes but is not limited to brigading, link-spamming, or general rapid-fire spam.
+**5. Keep profanity to a minimum.** If you wouldn't say it in front of police, you should avoid saying it here.
+**6. Limit self-promotion.** Refrain from sharing your content outside of applicable conversation or dedicated channels.
+**7. Stay on-topic.** We know conversations will take their own route, but please try to keep discussion to the appropriate channels.
+**8. No politics.** This includes hot-button social subjects. While some commentary on politics and society is unavoidable, this is not the platform for those discussions.
+**9. No sharing private information.** Content that includes someone's personally identifiable information or private messages should be anonymized or they may be deleted.
+**10. Don't break anything.** Do not share, take advantage of, or demonstrate exploits or bugs in this server. For security vulnerabilities, you can report them to any of the staff.
+**11. No mudslinging.** Constructive criticism and critical discussion is welcome, but personal attacks or defamatory and disparaging statements about individuals or entities are not.
+**12. No unnecessary pinging.** Ping if absolutely necessary, especially if you're going to ping staff.
+**13. Please use English.** It's known as the most used international language.
+**14. Good manners.** This means strictly no topics that would divert or derail the current conversation being held, especially those of sexual innuendos.
+**15. No hating/flaming about moderation decisions**. If you want to discuss moderation decisions (bans, mutes, changes, ...) please open a staff only ticket in ⁠help . Harassing a mod will get you banned.
+**16. Follow discord ToS**. We don't enforce it as much but if we find you worthy of a ban we won't hesitate. ──────────────────────────────────────────────────────────────────────────────────────────────────────
+
+**Ban Guidelines**
+
+> 1) If you don't follow the rules we will first warn you using Dyno. This creates a modlog of your user on this server.
+> 2) After 3 warnings this will result into a 24 hour mute. In that time we kindly ask you to reflect on your messages/actions and hope you will be back after your timeout.
+> 3) If you insist on not following the rules we will then proceed to ban you.
+> 4) If you think your ban is not justified or reflected on your behaviour, you can file a ban appeal so we can overthink your permanent ban.
+
+**Immediate Bans**
+
+> 1) NSFW (Not Safe For Work) or NSFL (Not Safe For Life*).
+>    * NSFL: Wishing for death, watching people die, jokes about people getting harmed, suicide.
+> 2) Scam links / your account got hacked (please file an appeal after your account has 2FA enabled/passwords changed).
+> 3) Harassing a moderator about decisions (see rule 15).
+> 4) Ban evading
+
+Please note:
+
+> **These rules are not comprehensive.** Moderators and staff may remove content, administer reprimands, or warn users for violations not codified here at their discretion. If a moderator or staff member asks you to stop doing something, please respect their request.
+**Staff and Other VIPs may be exempt** (to some extent) from any of these rules due to their reputation in the community, if you feel like they should be warned for a violation you should report to staff
+
+For questions regarding Discord's Privacy Policy or Terms of Use, please refer to the documents here (https://discord.com/terms)
+`Last Updated` 6 July 2022 17:52`, All rights reserved`
+https://discord.gg/northstar
+New users, **you can go to #⁠installation to find out how to install Northstar** as well as read the FAQ if you have any questions
+**If you get an issue whilst installing/playing please open a ticket in ⁠#help** (Do not go to ⁠#general to fix it)
+```
diff --git a/docs/steamdeck-and-linux/linux-troubleshooting.md b/docs/steamdeck-and-linux/linux-troubleshooting.md
index 2accfbd..eeb5493 100644
--- a/docs/steamdeck-and-linux/linux-troubleshooting.md
+++ b/docs/steamdeck-and-linux/linux-troubleshooting.md
@@ -133,7 +133,7 @@ It's also possible to create command aliases to type something short, such as tf
 
 ## Reshade adding incompatible DXVK version for Northstar
 
-If you ever used ReShade together with Titanfall2 in the past it will have created a bunch of DXVK DLLs that are incompatible with Northstar. If Northstar fails to fully initialize with an exeption and you have previously installed ReShade on Windows delete the following files from `Titanfall2/bin/x64_retail/`:
+If you ever used ReShade together with Titanfall2 in the past it will have created a bunch of DXVK DLLs that are incompatible with Northstar. If Northstar fails to fully initialize with an exception and you have previously installed ReShade on Windows delete the following files from `Titanfall2/bin/x64_retail/`:
 
 * D3D8.DLL
 * D3D9.DLL