Guides

This page contains a number of descriptions of common user tasks. If certain terminology is unclear, have a look at the glossary! It might be explained there.

Reporting a player

Reports are the driving factor behind Barricade. Communities need to create reports to help each other protect themselves from troublemakers. These steps assume you've gained access to the Bunker, either by enrolling as a Server Owner or by being invited as a Server Admin.

If you do not have access to the Bunker yet, but are part of a community that owns a server, reach out to your community owner or head admin: They may be able to grant you access. If you are the community owner or head admin and your community is yet to sign up, refer to the Quickstart page.

With access to Bunker, you can now access the #report-pc-player or #report-console-player channel depending on your community's platform(s). Click the "Get submission URL" button in the channel to generate a unique link that takes you to a Google form that you use to provide all the details for your report.

Important

Reports should only be created for offenses that take place on your Hell Let Loose servers. Furthermore, players should only be reported after you have permanently banned them from your own server.

Caution

This link can only be used for a single report. Every time you want to create a new report, you have to generate a new link. Links expire after a report is created or after one day has passed.

After submitting the form, as long as the URL was valid and there were no unexpected issues, your report should appear in the #pc-player-reports or #console-player-reports channel. This is a confirmation that your report was successfully received and is now being forwarded to all communities.

At the same time, you should receive a notification from Barricade. Included is a message similar to the one seen in the public channels above, but this one includes a couple of buttons to either edit or delete the report. The message will be sent in the same channel your community receives its reports in. If no (valid) channel is configured, it will attempt to send you a direct message instead.

Editing a report

Editing a report is similar to submitting a new report. To get started, click the "Edit Report" button underneath the report. You can edit any report as long as you have the admin role of the community that created the report.

Note

If you're having trouble finding the report, or just want to search for reports by player ID in general, you can use the /reports command.

Just like when creating a report, you are given a link to a Google Form. This time however, it comes prefilled with all of the report's details. You can make changes, and then resubmit the form.

The changes should be propagated to the original message in the #report-pc-player or #report-consoleplayer channel rather quickly. It might take a little longer for changes to appear in your community's private report feed.

Any players that are removed from a report will be immediately unbanned. Any new players added to the report will require review from communities before being banned. Barricade does not know the difference between correcting a player ID and removing a player ID in favor of another. In this case, it will assume the latter.

Deleting a report

To delete a report, see the instructions for editing a report, but press the "Delete Report" button underneath a report instead of the "Edit Report" button. The same conditions apply.

When a report is deleted, the players are automatically unbanned from all communities that had decided to ban them as a result of the report.

Reports can also be indirectly deleted by other communities. Namely, if enough communities decide to not ban or unban a player. The exact conditions required for this to happen are yet to be decided.

Battlemetrics: Advanced permission configuration

Important

This feature is currently disabled due to an issue

This guide assumes you have gone through the Quickstart and have set up a Battlemetrics integration. After your Battlemetrics integration is enabled and Barricade will create a ban list, you can narrow down the permisisons even further, by limiting Barricade's access strictly to that ban list and/or your organization.

This is not necessary for Barricade to function properly, however, it is more secure: Should the API key be compromised, stricter scopes will mean less damage an attacker can do.

The process will be comparable to the original setup, but with a few notable differences: We will be more specific with the scopes we require, and instead of creating a new integration, we will modify the token of the existing one.

1. Go to the Battlemetrics Developers page
2. Click on the New Token button next to Personal Access Tokens
3. Grant all of the permissions listed in the FAQ and be sure to limit them by organization or ban list where applicable!

Important

Only limit scopes by organization or ban list if the FAQ explicitly mentions you can do so for any given scope. Unexpected use of scope limits will lead to validation errors later.

4. Click on the Create Token button at the bottom
5. Copy your newly generated token
6. In Discord, run the /config integrations command
7. Click on the Reconfigure... button next to your Battlemetrics integration
8. Replace the API Key with the key from step 5
9. Submit the form
10. Go back to the Battlemetrics Developers page and delete the old API key

Battlemetrics: Disabling player alerts for individual servers

Important

This feature is currently disabled due to an issue

Note

If you want to disable player alerts altogether, use the /config disable alerts-channel command instead. Disabling player alerts for individual servers is currently not possible with Community RCON integrations.

Barricade will monitor your Hell Let Loose servers for connected players. If a player joins that has been reported, you will receive an alert to review the evidence. However, in some cases, you may want to exclude servers from this behavior to not receive any alerts from them, for instance event servers.

To do this, you need to limit which servers you grant Barricade access to: If Barricade doesn't have access to a server, it won't be monitoring it either. The guide above explains how to limit permissions. You want to limit the View RCON information permission ("scope") to the subset of servers you want to receive alerts from.