# Getting content

**Content** (the tab at the top) is where routers, scenarios, Experiences, addons and Devices come in.
They come from two places:

- **The content hub**: steonmod.com's list of signed packages. Fusion reads it at start and every
  hour. You can add other hubs in **Settings → Content hubs**.
- **Package files** (`.fusion`): everything in your Downloads folder, plus files you open
  (**Open a package file...**), double-click or drop on Fusion's window.

## Before you install

Each package shows:

- **What's inside** and what installing does with each piece.
- **What it needs**: already installed, in the package, or from another package file (installed
  first).
- **Whether you own the games** ("You own 1 of the 2 games this needs").
- **Who signed it**: Official, Verified, Community or Unsigned. A community or unsigned package
  can't carry program files (`.dll`, `.exe`...): Fusion refuses to install one that does.

A package that was changed after it was signed can't be read at all.

## Versions and rolling back

Fusion keeps every version you installed. If an update breaks something:

- **Roll back to …** goes back to the version before.
- **Keep this version** stops updates for it; **Allow updates** turns them back on.
- **Uninstall** takes it out again.

## Taken down

If a router or package is taken down (at a game publisher's request, or because it was harmful),
the hub's signed feed says so. Fusion then won't install it, and scenarios that use it say why
they can't be played. This is how SteonMod stays online for everyone: one router can go without
the rest going.

## Share your own

**Share** on an item's page in the Library saves a scenario or Experience as one file. Fusion signs it with your own
key (`%LOCALAPPDATA%\Fusion\keys\me.key`, made the first time: back it up) and checks it carries no
files from your games. Routers are published by their makers: [Publishing](https://steonmod.com/docs/publishing).