#fan-made-content

Checked May 28, 2026: the GM screen insert page lists Star Wars GM Inserts.pdf (6.6 MB), and the hazards page lists Savage-Worlds-Star-Wars-Hazards.pdf (12 MB).

Those are not campaign bibles. They are session tools. If a PDF only helps while preparing at home, keep it in the prep folder. If it helps while players are making decisions, it belongs in the table kit.

My Savage Worlds Star Wars table kit would have three layers:

1. Always visible: Bennies, wound reminders, chase procedure, Dramatic Task reminders, vehicle scale notes, and the Force ruling for this campaign.

2. Scene packet: two hazards, one obstacle, one social pressure, one combat wrinkle, and one escape route. This packet changes every session.

3. Source links: the companion page and official SWADE page, so the group can check the baseline without hunting down rehosted files.

The hazards PDF is strongest when it makes existing scenes sharper. A hangar fight becomes better with blast doors, smoke, unstable fuel, maintenance pits, panicked workers, and a launch countdown. A wilderness trek becomes better with heat, disease, sensor interference, a broken speeder, and an NPC who knows the safe route but has a price.

Practical prep rule: pick one hazard that changes movement, one that changes time pressure, and one that changes social cost. If all three only deal damage, the session will feel flatter than Star Wars usually should.

This source checklist compares two Star Wars Savage Worlds fan PDF pages checked May 28, 2026: Time of the Old Republic and Spirit of Rebellion are better treated as era commitments than as files to stack automatically.

Time of the Old Republic:

The page lists Star Wars TOTOR-Web.pdf (9.7 MB) and describes an expansion with edges, gear, vehicles, templates, and NPC material. That points toward a campaign where Force traditions, lightsaber visibility, old institutions, and large ideological conflict are not rare background details. If most player characters are adjacent to Jedi or Sith politics, start here.

Spirit of Rebellion:

The page lists StarWars_SpiritofRebellion_v1.01.pdf (13 MB) and frames the expansion around original-trilogy, Andor, Mandalorian, Book of Boba Fett, and broader EU-style material. That points toward cells, fugitives, patrol heat, irregular gear, intelligence work, and ugly consequences after the job.

Do not begin by asking which book has more stats. Ask these four table questions:

1. Who has institutional power in the campaign's opening session?
2. How visible is Force use, and what happens when it is detected?
3. Are ships a home base, a chase tool, a military asset, or a debt problem?
4. What does failure look like: capture, exposure, occupation, corruption, exile, or civilian harm?

The main companion and Planetary Guide can support either direction, but they should not erase the era choice.

Practical recommendation: choose one era expansion as the campaign spine for the first arc. Bring in the other only when the table has a clear reason, such as lost technology, a historical force site, a faction inheritance, or a flashback session.

Checked May 28, 2026: Daremo's Star Wars: Planetary Guide page lists SWPlanets-Web.pdf (17 MB) as an expansion for the fan-made companion.

Use it as a landing-brief tool. The weak version of planet prep is three pages of setting lore that never changes a roll. The useful version gives the party an immediate Savage Worlds problem: a chase route, a hazard, a local authority, a social obstacle, and one reason the job cannot wait.

For each planet stop, I would prep five lines:

1. Approach pressure: what makes arrival unsafe, watched, expensive, or politically loaded?
2. Ground texture: one weather, terrain, crowd, or infrastructure detail that changes positioning.
3. Local authority: who can make the crew's day worse without becoming the final villain?
4. Play procedure: chase, Dramatic Task, Quick Encounter, social conflict, combat, or interlude.
5. Exit consequence: what follows the crew when they lift off?

The Hazards PDF page is the next useful source because it points at obstacles, traps, diseases, and environmental risks that can plug directly into those procedures.

The GM screen insert page is the table-facing pair. Use it for the references you expect to touch mid-scene, not as a trophy PDF.

Practical example: if the Planetary Guide gives you a refinery world, do not start with a two-page gazetteer. Start with a toxic loading platform, a corrupt port inspector, a timed cargo transfer, and a chase route through maintenance gantries. That turns the PDF into a session, not a wiki reading assignment.

Checked May 28, 2026: the clean starting point is the creator page for Daremo Publishing's Star Wars: Savage Worlds Companion, not a rehosted PDF mirror.

That page lists the current companion download as Star Wars Companion 5.0-Web.pdf (28 MB) and says the game requires the Savage Worlds Adventure Edition core book. Treat that requirement as the first table boundary. If one player is reading an older Savage Worlds Deluxe conversion and another is reading the SWADE companion, the GM will spend the first session reconciling assumptions instead of running the opening scene.

My first-pass setup would be:

1. Put the companion page and the official SWADE rules page in the campaign notes.

2. Write one paragraph for how the table handles the Force before anyone builds a character. Decide whether Force use is common, rare, dangerous, institutional, outlawed, or mostly off-screen.

3. Pick the campaign scale before touching gear. Street-level fugitives, squad missions, Jedi-era duels, and starfighter war stories need different equipment limits even when the same PDF has stats for all of them.

4. Do not upload the PDF to TopicFolio as an attachment. Link the creator page, note the file name, and let the creator page remain the download source.

The licensing page matters here because Star Wars and Savage Worlds are separate rights problems. Pinnacle's page explains the Savage Worlds fan and community-content paths, but it also reminds creators that other IP owners still matter.

Practical table packet: one companion link, one SWADE core link, a one-page campaign premise, a short Force-use ruling, and a short gear availability note. That is enough to make session zero useful without pretending the fan PDF is an official Star Wars RPG line.

The licensing checklist starts by deciding whether the Traveller 2e fan aid is free, TAS commercial content, or a generic compatibility project. Checked May 25, 2026: Mongoose's Traveller Licensing page is the first stop before posting or selling fan-made Traveller 2e material.

The simple version:

If it is free, small, and non-commercial, read the Fair Use Policy section first. That is the lane for many table aids, spreadsheets, and downloadable modules that are not being sold.

If it is commercial and uses the current Mongoose Traveller rules or Charted Space material, read the TAS Programme section before building the product page, cover, art plan, or credits.

If it is a generic Traveller-compatible work in your own setting, look at the Traveller Compatibility Licence path instead of assuming Charted Space is available.

The practical checklist:

1. Write down whether the aid is free or paid.
2. Write down whether it uses Charted Space names, places, organisations, trade dress, or logos.
3. Remove anything copied from Mongoose art or book layout unless the programme you are using explicitly permits it.
4. Link back to official tools or downloads when a table only needs a form, map, or worksheet.

For this group, the most useful fan-made content is probably not a full book first. Start with one clean artifact: a subsector prep sheet, a patron worksheet, a route pack, a ship-job tracker, or a character-lifepath audit sheet. The smaller the artifact, the easier it is to keep useful, legal, and table-tested.

The online-session checklist starts with the active Foundry package, its source repo, one Traveller Map route, and only the Mongoose downloads players will touch. Checked May 25, 2026: the package page describes a Mongoose Traveller 2e system with support for Traveller, NPC, creature, spacecraft, vehicle, and world sheets.

The source repository is here:

For a small crew, I would set expectations this way:

Use Foundry for repeatable structure: character sheets, NPC sheets, world records, attack rolls, and the campaign objects you actually touch every session.

Use Traveller Map outside the VTT until you know the campaign needs deeper integration:

The map is faster for route thinking, jump range conversation, and "what is nearby?" questions. Foundry is better once the party has committed to a scene, ship problem, contact, or world record.

One caution: do not confuse a VTT system with a content library. The package page describes system support and notes the current content limits. That is healthy. It keeps the table from assuming every book, equipment entry, and campaign handout has appeared automatically.

My minimum prep bundle would be: one Traveller Map route link, one world sheet, one ship or vehicle sheet if it matters this session, and only the official Mongoose downloads that players will need to write on.

Character sheet checklist: use Mark Munson's Mongoose 2nd Edition generator as an audit aid, then copy the keeper onto a current official Mongoose 2022 character sheet. Checked May 25, 2026: the Traveller Character Generator page links to the Mongoose 2nd Edition tool.

The best use case is not "press a button and accept the Traveller." The best use case is speed plus auditability.

For player characters, still let the table see the lifepath:

1. Roll or choose the term structure together.
2. Use the generator as a second pass to catch bookkeeping mistakes.
3. Copy the final character to a current Mongoose sheet from the official downloads page.

That keeps the important Traveller moments in the room: failed survival rolls, strange career turns, unexpected contacts, debt, benefits, and the argument over whether the group actually needs another gunner.

For Referees, the generator is stronger as an NPC and backup-character tool. Generate three candidates, keep the one with the clearest table problem, and rewrite the rest into contacts, patrons, rivals, or crew applicants. A Traveller who looks imperfect on paper is often more useful than one optimized for a fight.

Practical check before play: read the character aloud as a job history, not as stats. If the group cannot hear why this person would take shipboard work, fix that before adding another skill package.

The route worksheet starts with Traveller Map, Traveller Worlds, and Mongoose's free downloads before any Mongoose Traveller 2e patron gets written. Checked May 25, 2026: this is a table-use stack, not a replacement for the Mongoose Traveller 2e books.

Start with Mongoose's Traveller Tools page:

That page matters because it is not just a random link dump. Mongoose points players and Referees toward tools that are already useful around Charted Space play, including Traveller Map and Traveller Worlds.

For a session, I would use the fan tools in this order:

1. Pick the route in Traveller Map.

Do this before writing the patron. Jump distance, fuel assumptions, red or amber zones, border pressure, and the shape of nearby alternatives are all better adventure constraints than another generic job offer.

2. Open the destination in Traveller Worlds.

Use the generator to turn the world data into landing-site texture: weather, terrain, a map cue, and one local inconvenience. Do not let the generator write the whole session. The Referee's job is still to decide what matters when the crew arrives.

3. Pull only the official forms you need from Mongoose's free downloads.

The useful fan-made layer is the handoff between those sources: a route note, a world brief, one cargo or patron pressure, and a clean sheet for the thing players will actually touch. If the handout does not change a decision at the table, leave it out.