An Introduction to Bazaar Packages

This guide assumes that you have already gone through the process to be approved as a Bazaar creator. If you want to begin selling content on The Bazaar, we recommend referencing the linked post first.

The Bazaar supports many different forms of content on its service! In this guide, we will explain packages on The Bazaar, and what kind of package your content might be categorized as.

What is a package?

A Bazaar package is any single specific bundle of content distributed on The Bazaar. A package can vary wildly in content. A software module adding a new sheet to a Foundry game system is a package. A ready-made adventure for Foundry is also a package. Even a collection of tokens, sold together on The Bazaar can be a package.

Basically, think of a package as any one product (paid or not) that is offered on The Bazaar.

On the Forge, we have four different kinds of packages- module packages, world packages, system packages, and asset packages.

What kind of package should my content be?

Below, we explain some common Bazaar content, and what kind of package form they should take. There may be some overlap between the examples below. When in doubt, reach out to Forge staff on our Discord for help.

You should distribute your content as an asset package when:

  • You are distributing images, audio, or video files compatible with Foundry and…
  • They are not bundled with Foundry data like scenes or characters and…
  • The media is not packaged alongside content that is.

For example, if you are distributing map images without preparing them as a scene within Foundry Virtual Tabletop, you would contain them within an assets package. It will then be up to users to set up the content themselves. This applies in general- if the media is compatible with Foundry Virtual Tabletop, but not configured with an associated entity (actor, journal, scene, etc.), you would distribute the media within an asset package. You can see what media files are compatible with Foundry here.

The exception to this, generally, is when you wish to distribute assets within existing bundled content. For instance, some mapmakers will distribute map packs with pre-configured dynamic lighting on a scene, which can be accessed through a Foundry compendium. In addition, they might also include related assets for a gamemaster to place on a map (as a tile) to enhance that map, or other maps. In these cases, even if the primary purpose of the package is to provide assets, if the content is associated with a compendium module, it should be distributed as a module package.

You should distribute your content as a world package when:

  • You are distributing an adventure with pre-configured scenes/journals/actors, and want users to access the content via an installable Foundry world.
  • You are otherwise distributing content within a Foundry world, and have some creative/desired reason for distributing the content packaged within a world, rather than a compendium or other distribution method.

Worlds, sometimes known as “adventures” on other VTTs/platforms when referring to RPG products, are usually intended to be feature-complete campaigns or mini-campaigns, ready to run within a single Foundry world. Clash at Kobold Cauldron is one example, containing everything a gamemaster needs to run the adventure, already set up for their usage. The content within Clash at Kobold Cauldron is self-contained within the distributed Foundry world, and has a central purpose as a self-contained world. It is distributed on The Bazaar as a world package.

If the content can only be reasonably distributed as a Foundry world, it should be bundled within a world, and distributed as a world package. If you are unable to distribute your content within a Foundry world, it would not be considered a world package.

If you want your content to be importable into existing worlds, is a small one shot, or an add-on intended for a larger adventure, then it would be better suited as a module package.

You should distribute your content as a module package when:

  • You wish to distribute media such as images/audio/video files, already prepared for usage within Foundry Virtual Tabletop. You wish to distribute this content in a way that allows users to access the content without importing a world.
  • You wish to distribute Foundry entities such as actors, items, journals, etc., without being bundled together into a world. Media files may or may not be associated with this content.
  • Your content is prepared as a typical software mod, adding/changing/removing features or behaviors of Foundry Virtual Tabletop in a method different from creating a system.
  • You wish to do some combination of the three use cases mentioned above.

Modules are the broadest type of package within The Forge, encompassing a shocking variety of content. Compendium modules are the most common form of this- modules that exist to store entities (items, actors, playlists, journals, etc.). Map packs are often distributed in compendium modules, where a map image is readied for use with scene data, ready to drag and drop into a user’s game immediately.

If this sounds complex, it really isn’t! It just means that media content is often distributed with associated Foundry data, making it easier for a user to drop and use within Foundry Virtual Tabletop.

Software modules provide changes to Foundry or Foundry system behavior. A module could add a dice tray to the bottom of Foundry’s chat, improving base Foundry functionality, or it could provide a new character sheet, changing a Foundry system’s functionality. They are one of the most common forms of community contribution to Foundry, and trying to list every possible example is difficult. But if you are distributing a software module, you are likely aware of whether your content belongs as a module package.

If your content does not fit into any of these specified use cases, it does not belong as a module package.

You should distribute your content as a system package when:

  • Your content is a developed game system for Foundry Virtual Tabletop.

Foundry Virtual Tabletop uses systems to define how a world/game is played within the software. Without a system, a world cannot be used, or even created on Foundry Virtual Tabletop. Most packages are not systems. If you have created/are distributing a system on The Bazaar, you are likely aware of whether your content belongs as a system package. If your content is not a Foundry system, it is not a system package.

Why does it matter what kind of package my content is?

As will be explained in a guide to publishing on The Bazaar, a Bazaar Creator must submit their content as a type of package, selecting from categories in a dropdown menu pictured below:

If you submit your content under the wrong category to The Bazaar, The Bazaar will be unable to process it, and you will need to contact Forge Support to fix the package.

Related Articles

As we release further guides to creating and managing Foundry packages, we will link them below.

How to create a compendium module