From 34abfc553a5e26e49d421c4d24c8b44829bce4e8 Mon Sep 17 00:00:00 2001 From: GeckoEidechse <40122905+GeckoEidechse@users.noreply.github.com> Date: Sat, 10 Feb 2024 21:02:03 +0100 Subject: Bump actions/checkout to v4 (#284) v3 uses Node 16 which is slated for deprecation by GitHub Actions --- .github/workflows/linkcheck.yml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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: -- cgit v1.2.3 From c8bfe1b91f08a62fafc650b2a5c1a1c705e72506 Mon Sep 17 00:00:00 2001 From: GeckoEidechse <40122905+GeckoEidechse@users.noreply.github.com> Date: Fri, 10 May 2024 15:58:19 +0200 Subject: Mention newer Intel CPUs on troubleshooting page (#286) Previously only mentioned 10th and 11th gen Intel CPUs but since then 12th and 13th gen have also released. --- docs/installing-northstar/troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/installing-northstar/troubleshooting.md b/docs/installing-northstar/troubleshooting.md index 967e7ed..91dd8e5 100644 --- a/docs/installing-northstar/troubleshooting.md +++ b/docs/installing-northstar/troubleshooting.md @@ -77,7 +77,7 @@ 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. -- cgit v1.2.3 From a5deecda16b167a857b86d6bf995e51f72b5b05f Mon Sep 17 00:00:00 2001 From: GeckoEidechse Date: Fri, 7 Jun 2024 15:48:50 +0200 Subject: Fix typo --- docs/steamdeck-and-linux/linux-troubleshooting.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) 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 -- cgit v1.2.3 From bfcaf444f6c4636f97a4b97640f6eb6d2b808c22 Mon Sep 17 00:00:00 2001 From: GeckoEidechse <40122905+GeckoEidechse@users.noreply.github.com> Date: Wed, 3 Jul 2024 15:15:13 +0200 Subject: Add basic page explaining how to host a local-only server (#287) --- docs/SUMMARY.md | 1 + .../hosting-a-server-with-northstar/local-only-server.md | 16 ++++++++++++++++ 2 files changed, 17 insertions(+) create mode 100644 docs/hosting-a-server-with-northstar/local-only-server.md diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md index 0492653..3c25df8 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) 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 %} -- cgit v1.2.3 From a69afc51e709c24f1fd22a16f89ac36e0c1a136f Mon Sep 17 00:00:00 2001 From: JMM889901 <41163714+JMM889901@users.noreply.github.com> Date: Sat, 6 Jul 2024 22:27:16 +0100 Subject: Remove ~ that people keep putting in the system variable (#224) For the record, `~0x20000000` clears the 29th bit of the result from cpuid, while `0x20000000` replaces the result with one with just the 29th bit set (OPENSSL_ia32cap.3). The 29th bit represents the Intel SHA Extensions. As such, if the second one (without the ~) works, the actual solution has nothing to do with the 29th bit; it's one of the others. --- docs/installing-northstar/troubleshooting.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/docs/installing-northstar/troubleshooting.md b/docs/installing-northstar/troubleshooting.md index 91dd8e5..9fa10f3 100644 --- a/docs/installing-northstar/troubleshooting.md +++ b/docs/installing-northstar/troubleshooting.md @@ -80,9 +80,9 @@ On newer Intel CPUs you might see a message like this 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. -- cgit v1.2.3 From fe578fc21011321b7e3f249a132df0889cf1aa6c Mon Sep 17 00:00:00 2001 From: GeckoEidechse <40122905+GeckoEidechse@users.noreply.github.com> Date: Sun, 14 Jul 2024 14:44:27 +0200 Subject: Move moderation page to subfolder (#288) to facilitate adding more pages in the future --- docs/SUMMARY.md | 2 +- docs/other/moderation.md | 18 ------------------ docs/other/moderation/README.md | 18 ++++++++++++++++++ 3 files changed, 19 insertions(+), 19 deletions(-) delete mode 100644 docs/other/moderation.md create mode 100644 docs/other/moderation/README.md diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md index 3c25df8..2af323f 100644 --- a/docs/SUMMARY.md +++ b/docs/SUMMARY.md @@ -69,5 +69,5 @@ ## Other * [Helping](helping.md) -* [Discord moderation](other/moderation.md) +* [Discord moderation](other/moderation/README.md) * [Credits](other/credits.md) diff --git a/docs/other/moderation.md b/docs/other/moderation.md deleted file mode 100644 index 2280845..0000000 --- a/docs/other/moderation.md +++ /dev/null @@ -1,18 +0,0 @@ -# Moderation - -{% hint style="info" %} -This page contains information targetted at Discord moderators. -{% endhint %} - - -## General stuff - -- **Communication:** Communication is key. Any changes and actions should be discussed with other moderators unless they are very obvious (e.g. scambans). - Any changes to permissions etc should be discussed first in `#staff-suggestions`. Any changes performed should also be manually written down in `#changelog` so that everyone is on the same page. -- **Use Dyno:** Use dyno commands to perform actions like mutes and bans. Dyno log is way easier to search than Discord's native audit log and helps us keep track of who did what. -- **Staff tickets:** User requests like receiving _Contributor_/_Modder_ role should be handled via staff ticket. This way other moderators can chime in and public channels are not clogged with unnecessary info. -- **Warn liberally:** User warns are stored in Dyno log. They should be performed as a first measure on misconduct. It's better to warn once too many times than ban someone without warning. - -## Useful commands - -- `!scamban UID`: Bans a user with a message telling them that their account has been compromised and has been spreading scam. diff --git a/docs/other/moderation/README.md b/docs/other/moderation/README.md new file mode 100644 index 0000000..2280845 --- /dev/null +++ b/docs/other/moderation/README.md @@ -0,0 +1,18 @@ +# Moderation + +{% hint style="info" %} +This page contains information targetted at Discord moderators. +{% endhint %} + + +## General stuff + +- **Communication:** Communication is key. Any changes and actions should be discussed with other moderators unless they are very obvious (e.g. scambans). + Any changes to permissions etc should be discussed first in `#staff-suggestions`. Any changes performed should also be manually written down in `#changelog` so that everyone is on the same page. +- **Use Dyno:** Use dyno commands to perform actions like mutes and bans. Dyno log is way easier to search than Discord's native audit log and helps us keep track of who did what. +- **Staff tickets:** User requests like receiving _Contributor_/_Modder_ role should be handled via staff ticket. This way other moderators can chime in and public channels are not clogged with unnecessary info. +- **Warn liberally:** User warns are stored in Dyno log. They should be performed as a first measure on misconduct. It's better to warn once too many times than ban someone without warning. + +## Useful commands + +- `!scamban UID`: Bans a user with a message telling them that their account has been compromised and has been spreading scam. -- cgit v1.2.3 From 49bc5c27c9e8f45462a436278da7fbaf8c59b2e4 Mon Sep 17 00:00:00 2001 From: GeckoEidechse <40122905+GeckoEidechse@users.noreply.github.com> Date: Sun, 14 Jul 2024 14:52:18 +0200 Subject: Move helping page to subfolder (#289) to match the structure in the sidebar and update any relative links --- docs/SUMMARY.md | 2 +- docs/helping.md | 92 --------------------------------------------------- docs/other/helping.md | 92 +++++++++++++++++++++++++++++++++++++++++++++++++++ 3 files changed, 93 insertions(+), 93 deletions(-) delete mode 100644 docs/helping.md create mode 100644 docs/other/helping.md diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md index 2af323f..ada0b78 100644 --- a/docs/SUMMARY.md +++ b/docs/SUMMARY.md @@ -68,6 +68,6 @@ ## Other -* [Helping](helping.md) +* [Helping](other/helping.md) * [Discord moderation](other/moderation/README.md) * [Credits](other/credits.md) diff --git a/docs/helping.md b/docs/helping.md deleted file mode 100644 index e12bb4e..0000000 --- a/docs/helping.md +++ /dev/null @@ -1,92 +0,0 @@ -# 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'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. - -If they really don't want to open a ticket or you don't want to deal with a ticket, ask them to move to `#northstar-chat`. -There, not only can they embed things, but it'll be slightly more focused on helping than other channels would be. - -Arguably the most important things to know as a helper are the ability to read logs and deal with users that don't read the wiki (90% of tickets are solutions solvable by checking the wiki. -There is a pretty high chance that even if the user claims they read the wiki they didn't actually do so or didn't manage to find their issue on there) - -The first section will go over extremely common issues and their tags, then the basics of using the ticket bot for commands inside tickets - -Additionally, please don't be afraid to ask for help. The entirety of `#volunteers-chat` in the Discord server is specifically for those that help/sometimes help users and there's no shame it not knowing. - -## Common issues and their tags - -In the Northstar Discord server, a massively used device to help end users is the tickets bot. A lot of the common issues and questions that come up have tags for them on the Discord server. - -Tags are bits of information that you can easily access by using a slash command. -We use them mostly for common questions (such as the tag explaining how you can spawn the double barrel shotgun and that you can't spawn it in most servers), and for linking directly to specific pages on the wiki (such as the section about [Intel gen 10+ cpus](https://r2northstar.gitbook.io/r2northstar-wiki/installing-northstar/troubleshooting#intel)). - -The tag command for the tickets bot is `/tag`, and you can either type `/tag id:{TAG ID HERE}` or let the bot autofill the tag for you after typing `/tag` and selecting the tag id from the list (make sure you select the ticket bot, and not Dyno!). -Note, you can't reply to a user while using a slash command, so try to reply to the bot's message after sending the tag command while pinging the person it's directed at and informing them that they should follow the provided solution. - -You can find a list of these tags on the [tag dashboard for the help bot](https://panel.ticketsbot.net/manage/920776187884732556/tags), so long as you sign in using your Discord account and have access to it with the roles that you have. - -## Ticket channel commands - -This entire section only applies to users with `ticket-staff`+ roles who can see the ticket channels in the Discord server - -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) - -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) - -Note the buttons below the embed.\ -Hitting `Close` will close the ticket without a reason for closing it.\ -`Close with reason` will let you give a reason as to why you closed the ticket.\ -`Claim` allows you to "claim" a ticket and lets other helpers know that you'll be solving the ticket. -This doesn't usually get used for Northstar, however other helpers can still message in the channel even after it's claimed so don't worry if you accidentally claim a ticket/end up not being able to solve it. - -These buttons, however, are not always easy to scroll back up to, especially if the ticket has been open for a while. This is where slash commands come in. - -There are 3 major slash commands used for tickets. These are `/close`, `/closerequest`, and `/add`. - -`/close` by itself will close the ticket immediately, without a reason. Because it's a slash command however, you can give a reason for closing using the `reason` option when typing the slash command. - -`/add` will add a normal (non ticket-viewing) user to a ticket. This is useful if, for example, someone who created a mod and can't see the tickets has one of their mods cause an error for a user and you can't diagnose it. This is also useful for cases where someone opens a ticket for someone else. - -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) - -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. - -To _use_ the `/closerequest` command, there are a few "ways" to use it.\ -Note that `close_delay` is a number, meaning the time in hours before the ticket autocloses.\ -`reason` is a box to input the reason for a close request.\ -Using "ac" as described later lets other people know how long until the ticket will close ("ac" meaning **A**uto **C**lose). This helps yourself and others when looking at tickets because the tickets bot doesn't show when a ticket is set to auto close. - -If the ticket seems resolved/the user has said they have no issues, use `/closerequest` with `close_delay` set to `12` and the `reason` set to "resolved, ac 12hr" - -For tickets where the end user that opened the ticket _never_ responded, we usually wait a couple days, ping them a few times, and if they continue to be inactve, set a close request with `close_delay` set to 24 and the `reason` set to "no response, ac 24hr" -For inactive tickets (when it's the _user_ not responding, not us!) we usually give them a few days and then start pinging them once a day. -If they continue to not respond for 2-3 days, we tend to set a close request with `close_delay` set to `48` and the `reason` set to "inactive ticket, ac 48hr" - -You can also use `/closerequest` without giving a `close_delay` or a `reason`, however you should always try to give a reason for closing a ticket, and if you don't give a `close_delay` there's a high chance that the ticket doesn't get closed (quite a few end users don't accept or see the close request) - -You can view information on the closed tickets, such as open and close date, who opened the ticket, who closed the ticket, and the reason for closing the ticket in the `#transcripts` channel. -The bot also provides an online log of the entire ticket connected to the embed when a ticket is closed. - -## Miscellaneous - -### Northstar Servers - -A Discord bot created by birb and rewritten by H0L0 which allows you to run commands like `.status` and see how many people are currently online on Northstar, as well as commands such as `.search region aus` (which would search for Northstar servers with the region set to Australia). -You can check the [GitHub repo](https://github.com/hummusbird/northstar-bot) for more info on Northstar Servers. - -### Spectre - -A Discord bot created by Cyn with help from multiple people designed to automatically reply to specific errors messages, screenshots of error messages, and some more quality of life features for helpers. -You can check the [GitHub repo](https://github.com/itscynxx/Spectre) for more info on Spectre. diff --git a/docs/other/helping.md b/docs/other/helping.md new file mode 100644 index 0000000..86a8900 --- /dev/null +++ b/docs/other/helping.md @@ -0,0 +1,92 @@ +# 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'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. + +If they really don't want to open a ticket or you don't want to deal with a ticket, ask them to move to `#northstar-chat`. +There, not only can they embed things, but it'll be slightly more focused on helping than other channels would be. + +Arguably the most important things to know as a helper are the ability to read logs and deal with users that don't read the wiki (90% of tickets are solutions solvable by checking the wiki. +There is a pretty high chance that even if the user claims they read the wiki they didn't actually do so or didn't manage to find their issue on there) + +The first section will go over extremely common issues and their tags, then the basics of using the ticket bot for commands inside tickets + +Additionally, please don't be afraid to ask for help. The entirety of `#volunteers-chat` in the Discord server is specifically for those that help/sometimes help users and there's no shame it not knowing. + +## Common issues and their tags + +In the Northstar Discord server, a massively used device to help end users is the tickets bot. A lot of the common issues and questions that come up have tags for them on the Discord server. + +Tags are bits of information that you can easily access by using a slash command. +We use them mostly for common questions (such as the tag explaining how you can spawn the double barrel shotgun and that you can't spawn it in most servers), and for linking directly to specific pages on the wiki (such as the section about [Intel gen 10+ cpus](https://r2northstar.gitbook.io/r2northstar-wiki/installing-northstar/troubleshooting#intel)). + +The tag command for the tickets bot is `/tag`, and you can either type `/tag id:{TAG ID HERE}` or let the bot autofill the tag for you after typing `/tag` and selecting the tag id from the list (make sure you select the ticket bot, and not Dyno!). +Note, you can't reply to a user while using a slash command, so try to reply to the bot's message after sending the tag command while pinging the person it's directed at and informing them that they should follow the provided solution. + +You can find a list of these tags on the [tag dashboard for the help bot](https://panel.ticketsbot.net/manage/920776187884732556/tags), so long as you sign in using your Discord account and have access to it with the roles that you have. + +## Ticket channel commands + +This entire section only applies to users with `ticket-staff`+ roles who can see the ticket channels in the Discord server + +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) + +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) + +Note the buttons below the embed.\ +Hitting `Close` will close the ticket without a reason for closing it.\ +`Close with reason` will let you give a reason as to why you closed the ticket.\ +`Claim` allows you to "claim" a ticket and lets other helpers know that you'll be solving the ticket. +This doesn't usually get used for Northstar, however other helpers can still message in the channel even after it's claimed so don't worry if you accidentally claim a ticket/end up not being able to solve it. + +These buttons, however, are not always easy to scroll back up to, especially if the ticket has been open for a while. This is where slash commands come in. + +There are 3 major slash commands used for tickets. These are `/close`, `/closerequest`, and `/add`. + +`/close` by itself will close the ticket immediately, without a reason. Because it's a slash command however, you can give a reason for closing using the `reason` option when typing the slash command. + +`/add` will add a normal (non ticket-viewing) user to a ticket. This is useful if, for example, someone who created a mod and can't see the tickets has one of their mods cause an error for a user and you can't diagnose it. This is also useful for cases where someone opens a ticket for someone else. + +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) + +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. + +To _use_ the `/closerequest` command, there are a few "ways" to use it.\ +Note that `close_delay` is a number, meaning the time in hours before the ticket autocloses.\ +`reason` is a box to input the reason for a close request.\ +Using "ac" as described later lets other people know how long until the ticket will close ("ac" meaning **A**uto **C**lose). This helps yourself and others when looking at tickets because the tickets bot doesn't show when a ticket is set to auto close. + +If the ticket seems resolved/the user has said they have no issues, use `/closerequest` with `close_delay` set to `12` and the `reason` set to "resolved, ac 12hr" + +For tickets where the end user that opened the ticket _never_ responded, we usually wait a couple days, ping them a few times, and if they continue to be inactve, set a close request with `close_delay` set to 24 and the `reason` set to "no response, ac 24hr" +For inactive tickets (when it's the _user_ not responding, not us!) we usually give them a few days and then start pinging them once a day. +If they continue to not respond for 2-3 days, we tend to set a close request with `close_delay` set to `48` and the `reason` set to "inactive ticket, ac 48hr" + +You can also use `/closerequest` without giving a `close_delay` or a `reason`, however you should always try to give a reason for closing a ticket, and if you don't give a `close_delay` there's a high chance that the ticket doesn't get closed (quite a few end users don't accept or see the close request) + +You can view information on the closed tickets, such as open and close date, who opened the ticket, who closed the ticket, and the reason for closing the ticket in the `#transcripts` channel. +The bot also provides an online log of the entire ticket connected to the embed when a ticket is closed. + +## Miscellaneous + +### Northstar Servers + +A Discord bot created by birb and rewritten by H0L0 which allows you to run commands like `.status` and see how many people are currently online on Northstar, as well as commands such as `.search region aus` (which would search for Northstar servers with the region set to Australia). +You can check the [GitHub repo](https://github.com/hummusbird/northstar-bot) for more info on Northstar Servers. + +### Spectre + +A Discord bot created by Cyn with help from multiple people designed to automatically reply to specific errors messages, screenshots of error messages, and some more quality of life features for helpers. +You can check the [GitHub repo](https://github.com/itscynxx/Spectre) for more info on Spectre. -- cgit v1.2.3 From e802cdd2d7fb1eba0762062e7a46d428fd8306e8 Mon Sep 17 00:00:00 2001 From: GeckoEidechse <40122905+GeckoEidechse@users.noreply.github.com> Date: Sun, 14 Jul 2024 15:08:18 +0200 Subject: Add initial empty page tracking moderation rules (#290) Current rules will be added in separate PR so that they can be properly attributed to their original author. --- docs/SUMMARY.md | 1 + docs/other/moderation/rules.md | 7 +++++++ 2 files changed, 8 insertions(+) create mode 100644 docs/other/moderation/rules.md diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md index ada0b78..bc359b2 100644 --- a/docs/SUMMARY.md +++ b/docs/SUMMARY.md @@ -70,4 +70,5 @@ * [Helping](other/helping.md) * [Discord moderation](other/moderation/README.md) + * [Rules](other/moderation/rules.md) * [Credits](other/credits.md) diff --git a/docs/other/moderation/rules.md b/docs/other/moderation/rules.md new file mode 100644 index 0000000..e2de706 --- /dev/null +++ b/docs/other/moderation/rules.md @@ -0,0 +1,7 @@ +# 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. + +```markdown +``` -- cgit v1.2.3 From 0e2f35f7b48a3351f82b80a7a5e598cf2ff80892 Mon Sep 17 00:00:00 2001 From: GeckoEidechse <40122905+GeckoEidechse@users.noreply.github.com> Date: Sun, 14 Jul 2024 18:48:13 +0200 Subject: Add current rules from Discord (#291) The rules where committed under @xamionex's name as they were the last person to post them in the `#rules` channel and exact attribution is quite difficult at this time as the message is over two years old now. Co-authored-by: amione <57235791+xamionex@users.noreply.github.com> --- docs/other/moderation/rules.md | 44 ++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 44 insertions(+) diff --git a/docs/other/moderation/rules.md b/docs/other/moderation/rules.md index e2de706..3d00585 100644 --- a/docs/other/moderation/rules.md +++ b/docs/other/moderation/rules.md @@ -4,4 +4,48 @@ 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. ```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) ``` -- cgit v1.2.3 From b35a4dec3ac328863f4e7964867c3a88b8046e56 Mon Sep 17 00:00:00 2001 From: GeckoEidechse <40122905+GeckoEidechse@users.noreply.github.com> Date: Sun, 14 Jul 2024 18:51:17 +0200 Subject: Ignore Taskinoz' server browser for linkcheck (#292) https://taskinoz.com/northstar/ seems to occasionally either take too long to respond or falsely detect us as spam so easiest is to just skip it during linkcheck --- .github/.markdownlinkcheck.json | 3 +++ 1 file changed, 3 insertions(+) diff --git a/.github/.markdownlinkcheck.json b/.github/.markdownlinkcheck.json index 3749dee..06df66b 100644 --- a/.github/.markdownlinkcheck.json +++ b/.github/.markdownlinkcheck.json @@ -9,6 +9,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" } -- cgit v1.2.3 From ccb4e66c6f319ed83e954c43935c05e50b4142ba Mon Sep 17 00:00:00 2001 From: GeckoEidechse <40122905+GeckoEidechse@users.noreply.github.com> Date: Sun, 14 Jul 2024 18:55:34 +0200 Subject: Add link that shows changes to rules (#293) Adds a link which shows the history of the rules page on GitHub --- docs/other/moderation/rules.md | 2 ++ 1 file changed, 2 insertions(+) diff --git a/docs/other/moderation/rules.md b/docs/other/moderation/rules.md index 3d00585..59d25f7 100644 --- a/docs/other/moderation/rules.md +++ b/docs/other/moderation/rules.md @@ -3,6 +3,8 @@ 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. ────────────────────────────────────────────────────────────────────────────────────────────────────── -- cgit v1.2.3