Skip to content

5ET-1357 Add functionality to allowlist content or otherwise automatically exclude new sources #1370

@crawltracker

Description

@crawltracker

Information
We have blocklist functionality which is incredibly useful. However, when you are running a local copy of the site and are trying to guide your players into only using available sources, each time the site is updated it assumes that you want to add all the newly available "official" sources to your content. It confuses players, surfaces or features that players don't actually have access to in the game (e.g. mid-campaign changes), and would be nice to exclude them if I don't actually own them.

The only way to make sure that you've blocked new sources today is to keep tabs on what sources have been added when updating the site (since you still want to get content updates and fixes and new sources), then make sure to add new ones to the blocklist. You can use the bulk exclude in the blocklist page then remove sources you want to keep, but it's a time consuming process.

Who would use it?
DMs running local copies of the site that are mid-campaign and want to prevent player confusion.

How would it work?

Ideal case (rough idea)

  1. Add an "allowlist" section to content-blocklist.json that can be specified in the /homebrew folder.
  2. If enabled, the site only adds the core rulebooks by default based on the rules version selected in your Settings.
  3. If the allowlist object is present, that would include any sources you specify from both official/core sources and homebrew sources.
  4. This could stack with blocklist for additional filtering specificity (e.g. include Tasha's but exclude all the Species).
  5. Duplicate the UI sections from the Blocklist page in the site to display and bulk add/remove Allowlist sources just like with the blocklist source selectors.

Alternative approaches (simpler)

A. Add a setting to the blocklist JSON to automatically exclude official sources added after a specific date, however it doesn't look like this data is stored in the official sources today.
B. Add a column to the blocklist page with the source type (Official / Homebrew) sorted in chronological order (or move Official/Homebrew sources to separate tables) so that you can quickly remove or block newer official sources.

Why should this be added?

  1. Lets you pare down the increasingly complex mix of settings and sources.
  2. New official sources are being added at a much more rapid pace than they used to.
  3. It would be easier to limit content to only sources that you own.
  • hightouch (hightouch)

Upvote - alternerdtive (alterNERDtive)

Indifferent - thandul (Thandul)

Indifferent - spap (Spappz)

Upvote - _emzee (EmZee)

Upvote - spudems (Spudems)

Upvote - hareblix (Hare Blix)

Upvote - teccamtheturtle (Teccam)

Upvote - pelichicken (Jordan)

Upvote - atthnei (Atthnei)

Upvote - darthrevan3994bby (Wabbajackal)

Upvote - georgijh (Georgi)

Upvote - ajp5581 (Aj)

Upvote - sqeed (Sqeed)

Indifferent - meifl (Luis)

Upvote - lavisciouslemon (grapitygrape)

Upvote - _kimura (Kimura)

Upvote - earlofham (EarlOfHam)

Votes: +14 / -0 / ±3

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions