Packages
A quiet overview of what you can install, what belongs to rules data, and what is still only a planned add-on.
Types
Downloads, rules data, add-ons, and ideas are different things. This page keeps those choices separate.
The build people install on a workstation, laptop, or travel machine.
Rules coverage and explanation data that changes what Chummer can show.
Table or campaign-specific amendments that must stay reviewed and reversible.
Briefings, primers, recaps, and media files that travel with a clear history.
A reviewed proposal that stays in Chummer until compatibility and moderation are clear.
Browse
Use Downloads for the app. Use rules data and add-ons only when you know they fit the character or table you are working on.
A file package for primers, briefings, recaps, and shared output bundles.
Works with: Compatibility depends on publication trust, the file page, and clear history.
Best for: Media and file packages may support a page, but they cannot replace route, install, or rules status.
Notes: The file library already shows that publication, recap, and preview outputs can stay inside Chummer.
Open detailsA table-scoped package for house rules, return notes, and reversible scope decisions.
Works with: Compatibility starts at table or campaign scope before broader community rollout.
Best for: KARMA FORGE discovery and campaign approvals must exist before a broader release promise.
Notes: KARMA FORGE and campaign continuity docs already point to the need for reviewed package limits.
Open detailsA proposal package for ideas that need clustering, compatibility review, and moderation before they become product work.
Works with: Compatibility stays advisory until Chummer review moves the proposal into a clearer package path.
Best for: Moderation, duplicate handling, privacy, and package compatibility must stay inside Chummer pages.
Notes: Participate already separates safe public signal from contact, installs, and account work.
Open detailsThe current desktop install path with the calmest first launch and account claim flow.
Works with: Matches the current release channels on Downloads: public installers and platform notes stay on the downloads page.
Best for: Public download starts at /downloads.
Notes: Downloads, Status, and account claim history already point here.
Open detailsThe current rules data for the SR5 coverage Chummer can explain today.
Works with: Works with Chummer's rules engine, explanation path, and current release status view.
Best for: Current status must be visible before broader parity language becomes public copy.
Notes: The current release status view already points to the explanation path and current rules state.
Open detailsNext step
Packages should clarify choices, not replace the install page or support path.