Skip to content
Tutorials

Public Build Requirements

Publish a read-only requirements page so members can browse what the guild expects before they submit a GearCheck.

Builds and Evidence
Who uses it
Guild owners, managers, build editors
Where it lives
Dashboard > Game Packs > Pack > Public requirements link
Goal
Members get a clean pack/activity/build reference without needing dashboard access or a separate spreadsheet.
On This Page5 sections

Before You Start

  • A configured pack with at least one build.
  • Permission to edit the pack.
  • A plan for where the link will be shared, such as Discord channels, pins, docs, or onboarding.

Steps

  1. Enable the link from the pack page

    Open the pack, enable the public requirements link, and preview it before sharing. Disabled links return a not-found page so old shared links stop working immediately.

  2. Review the activity and role structure

    The page mirrors the pack's activity, role, spec, and build requirements. If the page feels disorganized, fix the pack/build model instead of editing the public page directly.

  3. Regenerate only when needed

    Regenerate the token if a link was shared somewhere it should not be. Normal build edits update the page because it reads the current pack data.

  4. Use external references when available

    Game adapters can attach item or set references where reliable catalog matches exist. Treat those links as helper context, not the scoring source of truth.

Check It Worked

  • Preview opens without requiring dashboard login.
  • The link shows the current pack, activities, builds, and role/spec labels.
  • The shared link is copied from the enabled pack, not guessed manually.
  • Regenerating the token invalidates older shared URLs.

Common Pitfalls

  • Sharing the dashboard build editor URL instead of the public requirements URL.
  • Using the requirements page as the only onboarding material for complex evidence exports.
  • Forgetting to disable or rotate the link after a major pack restructure.