v1.2.1b

Changes

• Added a new /repopulate-integration command.
  • Looks for any players that should be banned and submits a ban request to the integration if no ban exists.
  • Useful for populating a ban list with bans that were added while the integration was disabled or not yet created.
• [Battlemetrics] Reverted support for more restrictive API permissions.
  • This was causing too many issues due to hard to predict behavior.
• [Battlemetrics] Improved error propagation

v1.2.1a

Bug Fixes

• Fixed an unexpected error occurring when creating a new integration
• Fixed various critical Battlemetrics permission issues
  • Due to some issues during testing the set of minimum permissions from previous release ended up being too strict. As a consequence, they have been loosened a little.
• Fixed invalid URLs being used to link to a Battlemetrics ban page

v1.2.1 - Improved Battlemetrics integration

This update brings a ton of enhancements to the Battlemetrics integration. If you are currently using a Battlemetrics integration, please read the upgrade instructions at the bottom.

Changes

• [Battlemetrics] Added initial support for Player Alerts
  - Will notify admins when a reported player joins any of your HLL servers
  - This is a feature previously exclusive to Community RCON
  - Alerts can be turned off on a per-server basis (wiki)

• [Battlemetrics] Added initial support for ban profile linking
  - Every day, Barricade will look if a banned player is known to your organization and link the ban to the profile of that player.
  - Once a ban is linked to a player's profile, that ban will be visible on that profile, and vice versa.

• [Battlemetrics] Added support for more restrictive API keys
  - This allows users to further narrow down the permissions granted to Barricade to strictly what is necessary
  - The error raised if permissions are missing is more descriptive (for both BM and CRCON)
  - See the guide for more details (wiki)

• Bug fixes
  - /config integrations does not respond and/or has excessive load times
  - Reports cannot be edited after an update pushed out by Google
  - "Item would not fit at row 0" error after two consecutive actions in Integration Management view
  - Updated credentials are not being propagated to websockets
  - Websockets are unintentionally restarted during certain operations
  - [Battlemetrics] Synchronization is consistently failing
  - [Battlemetrics] Synchronization skips the first 100 bans

Breaking changes to Battlemetrics integrations

For player alerts and profile linking to work, Barricade requires the View RCON information permission. Existing installations without this permission will stop working when the next synchronization cycle hits, sometime within the next 48 hours.

The wiki has a new guide that covers how to update the permissions of a Battlemetrics integration. Limiting the permissions as described is optional but recommended.

Furthermore, if you'd previously used a Community RCON integration alongside Battlemetrics to be able to have player alerts, you will want to disable either. You will receive alerts twice otherwise.

v1.2.0 - Expanded community configuration

In this update, various configuration options are split into several smaller options to provide more detailed customization of Barricade's behavior to match your community's needs and desires.

Changes

• Split up the "Reports feed" setting into "Reports feed", "Confirmations feed" and "Alerts feed"
  - By default, confirmations and alerts will be sent to the same channel as incoming reports
  - The confirmations feed can be removed to receive report confirmations via DMs instead
  - The alerts feed can be removed to stop receiving player alerts

• Split up the "Admin role" setting into "Admin role" and "Alerts role"
  - By default, alerts will use your admin role
  - The alerts role can be removed to not receive a push notification when an alert is received

• The config overview has been updated with the new settings
  - Run the /config view command to get an overview of all settings available

• Automatically dismiss submission URLs to avoid reports with duplicate tokens
  - Previously, generated URLs would have to be manually dismissed by the user
  - If the user reuses the same URL for multiple reports, only the first will be received
  - The message is now automatically dismissed to avoid the user accidentally reusing the same URL

• Bug fixes and other improvements
  - Made (un)ban failure reasons more descriptive
  - Added or removed various ellipses according to HCI standards
  - Updated an enrollment error message to clarify multi-platform community ownership
  - Fixed the report confirmation notification being suppressed
  - Fixed an issue with integrations that could cause the underlying connection to be silently closed
  - REST: Added a token field to /reports and /communities/me/reports endpoints

v1.1.0 - Report filters & overhauled controls

This update is aimed to address some of the initial feedback to Barricade, allowing you to select which categories of reports you want to receive, as well as some other quality of life features to make Barricade easier to use and understand.

Changes

• Added report filters
  - A report filter specifies which reasons a community wants to receive reports and player alerts for
  - Report filters can be configured using the /config reports-filter command

• Overhauled the report review view
  - Now displays the name of the admin that reviewed the report
  - Simplified button colors to better highlight whether any immediate action should be taken
  - If more than one player was reported, select the player using a dropdown instead of having multiple rows of buttons

• Added a "refresh" button to the report management view

• Simplified the form for setting up a CRCON integration
  - You can now submit any link to your CRCON website and Barricade will sanitize it

• Bug fixes
  - Fixed an issue with CRCON causing ban IDs to be stored incorrectly
  - Fixed an issue causing banlists/blacklists to be recreated every time an integration is reconfigured
  - Fixed an issue causing banlist/blacklist synchronization to consistently fail
  - Fixed an issue causing Integrations to open multiple connections, often with outdated settings
  - Fixed an issue causing pagination of the /reports command to behave unexpectedly
  - Improved logging to ease identification of certain issues going forward

A note about synchronization

This release fixes a few issues related to integration synchronization. This is the process of comparing the data Barricade has with that of CRCON and Battlemetrics, and making adjustments in case of a discrepancy. This process was previously not functional to correct some of the issues that were present on launch day, so you might see some warnings about it now.

Furthermore, there was another issue with Community RCON specifically that affected the way bans were persisted. An effort was made to update the storage with accurate information, but not all could be recovered at this time. The remaining data will be repaired automatically during synchronization, but this too will likely emit some warnings.

v1.0.0 - Initial release

Fix cannot delete report