-
Notifications
You must be signed in to change notification settings - Fork 20
Sheets & Features
TLDR
The SW5e Module helps actor and item sheets support Star Wars 5e play more naturally inside the DND5e system.
You will feel that most clearly in:
- character and NPC sheet use
- powers and point-based resources, including Force/Tech discounts in the 1.4.0 feature set
- Force and Tech powercasting configuration
- credits-only Galactic Credits wallets
- blaster reload and activity-based ammo use
- body modification systems
- maneuvers and superiority-style play
- item behavior and SW5E-facing equipment support
- stock Foundry chrome with retained SW5E branding (selectable themes removed)
Once you understand those areas, the rest of the module becomes much easier to learn.
This page explains the main sheet-facing features of the SW5e Module for FoundryVTT.
If you are a GM or player, this is one of the most important pages in the wiki. It is where the module becomes practical. Instead of talking about the project at a high level, this page focuses on how the module supports play on the sheets you actually use.
This page is mainly about character sheets, NPC sheets, powers and resources, maneuvers, body-mod systems, and item-facing support. If you are looking for starship-specific guidance, use Starship Sheet Guide.
This page will help you understand:
- how the SW5e Module fits into sheet use on top of the DND5e system
- what kinds of SW5E features you are likely to see on character and NPC sheets
- how powers and power resources are supported
- how the blaster reload workflow behaves on supported sheets and in chat
- how themes and appearance work on SW5E-supported surfaces
- how cybernetics and droid customizations are separated
- what kind of questions belong here versus in outside Foundry resources
The SW5e Module does not replace FoundryVTT, and it does not replace the DND5e system from the ground up.
Instead, it helps DND5e sheets behave in ways that better support Star Wars 5e play. That means some parts of the sheet experience are:
- standard DND5e behavior
- SW5e Module support layered onto DND5e
- or a mix of both
You do not need to know the technical side of that to use the module well, but it helps to remember that not every field or button you see is being created by the module itself.
For most groups, the character sheet is where the module feels most important.
On character sheets, the SW5e Module helps present Star Wars 5e concepts in a way that fits actual play better than default DND5e assumptions would on their own. This includes support for SW5E-friendly terminology, powers, related resources, item categories, and other gameplay-facing features that players and GMs rely on during sessions.
You do not need to think of the character sheet as “a completely different sheet.” It is more helpful to think of it as a DND5e-based sheet that has been adapted to better support SW5e use.
In day-to-day play, that usually means the module matters most in these areas:
- power use
- resource tracking
- item setup and item display
- maneuver-related play
- SW5E terminology and categorization
NPC sheets follow the same general idea, but with a different play goal.
Players usually live on their own character sheets. GMs often move between several NPC sheets, sometimes quickly, and need them to stay readable and useful without a lot of extra setup. The SW5e Module helps support that by carrying SW5E concepts into NPC-facing workflows as well.
If you use Force-using or Tech-using NPCs, maneuver-driven stat blocks, or SW5E-specific equipment and features, the NPC sheet side of the module is especially important. It helps those actors feel like part of the same system instead of feeling like a partial workaround.
Supported NPCs can also participate in the managed blaster reload workflow when their weapons are set up the same way as supported character weapons.
One of the clearest SW5E feature areas on sheets is power support.
The module helps support Force powers and Tech powers inside the DND5e framework so that powercasting workflows make more sense for Star Wars 5e play. This matters because powers are not just names on a list. For powers to feel usable in play, the sheet needs to support the right categories, the right resource expectations, and a workflow that feels natural for the system.
For most users, the practical takeaway is simple:
- powers should not feel like a completely manual add-on
- power use should connect to the sheet in a way that makes sense
- the module is there to reduce friction between SW5E rules expectations and DND5e structure
Powers are closely tied to Force Points and Tech Points, and these resources are a major part of sheet usability.
It is one thing to list powers on a sheet. It is another thing to make resource tracking feel practical during play. The SW5e Module supports these point-based resources so that power-using characters and NPCs are easier to run in actual sessions.
From a user standpoint, the important thing is not the technical model behind the sheet. The important thing is understanding that resource support is part of the intended SW5e workflow.
Some actors need more control than the default DND5e assumptions provide.
The current SW5E workflow includes a Configure Powercasting path for supported actors. In practice, this means a GM or builder can adjust how certain Force-school casting abilities and point abilities are chosen, rather than being locked into a single default setup. In 1.3.9, the same dialog also supports tech casting ability overrides.
The practical reason this exists is simple:
- some characters need Light, Dark, and Universal handling to work differently
- some tables want the points ability and the casting ability to follow different logic
- some Tech users need an explicit casting-ability override
- some homebrew builds need a clearer override surface instead of hidden assumptions
If your actor’s power math does not match what you expect, this is one of the first things worth checking. For a more focused explanation, use Powercasting Configuration and Overrides.
Maneuver users also get clearer sheet controls in 1.3.9.
In Edit mode, supported character sheets expose Superiority cogs on the Powers tab and the sidebar tracker. Those dialogs are meant for type ability overrides and Superiority Dice resource settings, so you do not have to treat superiority as a purely hidden data field.
For the focused superiority explanation, continue to Maneuvers & Superiority.
The stock dnd5e Special Traits tab remains the Special Traits tab. The module cleans up SW5E-facing wording and localization for that surface, including section labels and the Original Class block, without replacing the stock tab itself.
If you see raw SW5E.* keys there, check Compatibility & Limitations and confirm your module version and locale files loaded correctly.
Supported managed blasters now use a magazine-style workflow based on item uses.
In practical terms, that means:
- supported blasters track their magazine through
system.uses - Attack, Rapid, and Burst activities can consume those shots
- if the weapon is empty, or does not have enough shots for the chosen activity, the activity is stopped before use
- owners and GMs receive a private Reload card in chat
- supported weapon rows also show a Reload control directly on the sheet
This is meant to reduce table friction. The player gets a clear answer about why the use did not proceed, and the GM can see the same private reminder if they need to help troubleshoot the setup.
If you copied a weapon into your world a long time ago and it does not behave like a newer example, compare it to a fresh compendium item. Older copied items may need a refresh or re-import to pick up newer reload or activity setup.
In the 1.4.0 feature set, selectable SW5E theme modes are removed. Application chrome follows stock Foundry / DND5e presentation. Core SW5E branding remains (Pause, lightsaber headers, logos). See Themes and Appearance.
Character and NPC wallets and price denomination UIs show Galactic Credits (gc) only. Orphan PHB coin amounts on older actors can be folded into gc by world migration on supported builds. See Attribute and Active Effect Keys.
The module supports both Cybernetic Augmentations and Droid Customizations, but they are not meant to be treated as the same workflow.
That matters because tables often want the sheet to answer two different questions:
- what is installed on this character as a cybernetic system?
- what is installed on this droid as a customization system?
The module keeps those workflows separate so the actor stays easier to reason about, especially for GMs who manage mixed parties. If you are working with body-mod-heavy characters, use Cybernetic Augmentations and Droid Customizations alongside this page.
The SW5e Module also supports maneuvers and related superiority-style resource workflows.
For groups that use maneuver-based classes, archetypes, or NPCs, this is a valuable part of the sheet experience. It helps those features live on the sheet in a more usable way instead of forcing everything into awkward manual tracking.
Not every group will interact with this feature often, but for tables that do, it can be one of the difference-makers between “the sheet technically holds the data” and “the sheet actually supports play.”
The sheet experience is not only about actors. It is also shaped by the items attached to them.
The SW5e Module helps support SW5E-style item behavior and presentation, including equipment categories, weapon properties, and other item-facing features that matter in play. Some of this support is about showing the right kind of information in the right place. Some of it is about helping items behave in a way that matches SW5E expectations more closely.
A simple way to think about this is:
- if an item is meant to carry important SW5e rules information, the module is trying to help that information survive contact with the sheet
- if an item seems wrong, it may be a data/setup issue instead of a pure sheet issue
- item behavior is often easier to understand when you check both the actor sheet and the item itself
If you want a more focused breakdown of how SW5E weapon properties are handled, see Weapon Properties Support.
A lot of sheet-related confusion comes from a few very normal misunderstandings.
“I expected the module to change everything.” It does not. The module helps DND5e support SW5e better, but you are still working inside the DND5e system.
“I do not know whether this is a sheet issue or an item issue.” That is common. If something looks wrong, check the attached item or feature data before assuming the sheet is at fault.
“I expected every SW5E rule element to be fully automated.” Some support is about structure, visibility, or playability rather than complete automation.
“Why did my Attack, Rapid, or Burst use open a private Reload card?” Because the weapon was empty or did not have enough remaining shots for that activity cost. The use was stopped before consumption.
“What happened to the SW5E theme setting?” Selectable SW5E themes are removed in the 1.4.0 feature set. Use Foundry’s own appearance settings and see Themes and Appearance.
“Where is the Tech casting override?” Use Configure Powercasting from the Powers tab Edit-mode cog. Tech is part of that dialog in 1.3.9.
“Where do I set Force/Tech point discounts?” Use the Force / Tech Points configuration dialogs. Paths are documented on Attribute and Active Effect Keys.
“This actor is showing something I did not expect.” Check the actor type, attached items, and version compatibility first. A surprising result is often caused by setup or a release change rather than a random failure.
If a sheet is not behaving the way you expect, try these checks first:
- confirm that your Foundry version, DND5e version, and module version are compatible
- check the actor type you are working with
- confirm the relevant items or features are actually attached to the actor
- compare the behavior to a newer compendium-backed example if you can
- check whether the behavior belongs to the sheet, the item, or a separate workflow
- review Troubleshooting for common issues before reporting a bug
If the problem is specifically about starship sheets, go to Starship Sheet Guide.
If the problem is specifically about weapon property behavior, go to Weapon Properties Support.
Use the next page based on what you need:
- Blaster Reload and Ammo Use if your table uses reloadable blasters
- Themes and Appearance for branding after theme removal
- Attribute and Active Effect Keys for attribute path lookup
- Powercasting Configuration and Overrides if you need Force or Tech casting overrides
- Maneuvers & Superiority if you need Superiority Dice controls
- Starship Sheet Guide if you are working with ship play or starship actors
- Weapon Properties Support if you want a clearer picture of property support on items
- Homebrew and Content Authoring if you want to build or adapt your own SW5E content
- Troubleshooting if something on a sheet does not look right
- FAQ if you want quick answers to common questions
SW5e Module Wiki Start here: Home · Getting Started · Feature Overview · Sheets & Features
Popular topics: Blaster Reload and Ammo Use · Themes and Appearance · Starship Sheet Guide · Powercasting Configuration and Overrides
Need help? Troubleshooting · FAQ · Compatibility & Limitations
Working on the module? Developer Guide · Developer Reference · Local Setup and Workflow · Testing & Contribution
For general FoundryVTT help, please use the Foundry VTT Discord, Baileywiki’s Foundry VTT playlist, or Encounter Library’s Foundry VTT Basics playlist.
SW5e Module Wiki
Start here: Home · Getting Started · Feature Overview · Sheets & Features
Popular topics: Blaster Reload and Ammo Use · Themes and Appearance · Starship Sheet Guide · Powercasting Configuration and Overrides
Need help? Troubleshooting · FAQ · Compatibility & Limitations
Working on the module? Developer Guide · Developer Reference · Local Setup and Workflow · Testing & Contribution
For general FoundryVTT help, please use the Foundry VTT Discord, Baileywiki’s Foundry VTT playlist, or Encounter Library’s Foundry VTT Basics playlist.