Bazaar: shared repositories of systems, modules and packs

Explore, install, update and publish with versions what the community creates, propose changes, share with code links and report abuse.

The Bazaar is where the community publishes what it creates, with versions: systems, D&D modules, system modules, adventures, animation and dice packs, and maps. Each thing lives in a repository with its version history, its licence and its files in plain view; whoever installs it takes a copy of their own, and whoever wants to improve it proposes a change, which the author reviews. It also searches outside, in Homebrewery and in Foundry packages.

Where it is

In Bazaar, in the app header (the route is /forja; the Bazaar is called that in the interface and "forja" in the address). If the Bazaar does not respond, the app hides its entries.

Requirements and permissions

Any account with a session explores, installs and proposes changes. Publishing needs something to publish (a system or module of yours, or an exported package) and declaring a licence and that you have the right to do so. What you install is a copy of your own and counts like any other content in your account (Plans, limits and downgrading).

Exploring and installing

The tabs are Browse, Mine, Shared with me and Installed. In Search the Bazaar type what you want and filter by Type, System, Language and License; sort by stars, date or name. Search everywhere widens the search to Homebrewery and Foundry VTT, which are imported into your library (Importing books and homebrew: file, text and Homebrewery, Foundry VTT in Roliando: systems, modules and worlds).

Open a repository: it has a Overview, its Versions, its Files (they can be read and downloaded) and its Proposals.
Install brings the latest version; Choosing a version creates a new copy with it; yours is left untouched.
If the author publishes a new version, Update appears, or you can Pin this version to stay on a specific one, or Go back to another version.
Star marks a repository; with a code link (Redeem a code link) you open one that does not appear in searches.

Publishing

From a system or module of yours, the packages menu offers Publish to the Bazaar (the first time it creates the repository) and Export as package (.zip). You set the version (like 1.2.3), what changes, the author's name and the License, and tick that you have the right to publish it and accept the terms. Who sees it is chosen with Who can see it: Public (appears in searches), Unlisted (only with a code link) or Private (only whoever you invite). To make it public the package needs a licence.

In Sharing and permissions you invite people as Editor (publishes versions and decides proposals) or Reader, create code links with an expiry and a maximum number of uses, and decide whether files are visible and whether proposals are accepted.

Proposing a change

In a repository you have installed, edit your copy and press Propose a change: it is sent as a proposal with a title and an explanation. The author sees the changes (Side by side or Unified), the conversation and the For and Against votes, and decides: Merge or Close without merging. Merging moves the changes into the repository; the author publishes the new version.

Reporting

Report content is on each repository, for rights holders and for any abuse: you choose the reason (copyright, illegal, hate, personal data or other), explain it and declare it in good faith. The administration reviews each report and can hide the package, which becomes private without being deleted. See Moderation, blocking and reports.

Known limits

A new version of what you installed does not overwrite your copy: a new one is created.
A very large file is stored apart and downloaded on install; in the viewer it can be downloaded.
Deleting a repository deletes all its versions and cannot be undone.

Frequent problems

"I can't make my package public." The licence or the confirmation of the right to publish is missing.

"My code link does not open." It has expired, reached its maximum uses or been revoked.