Tags & Batch Operations
Organize mods with flexible tags instead of rigid categories. Filter, batch-update, and exclude with precision.
Last updated on
Tags vs. Categories
Most launchers let you put a mod in one category. Polymerium uses tags — a mod can have as many tags as you want.
For example, Sodium might have:
performance core QoL stability-watchThis lets you filter and operate on mods from multiple angles:
- "Show me all performance mods"
- "Update everything except stability-watch mods"
- "Disable all QoL mods for testing"
Adding Tags
- Select an instance and go to the Setup tab.
- Each mod in the list has a tag field.
- Type tags separated by commas or spaces. Tags are freeform — use whatever makes sense to you.
Tags are stored per-instance, per-package. The same mod can have different tags in different instances.
Filtering by Tag
Use the tag filter in the mod list to narrow down what's visible. You can stack multiple tag filters to find exactly what you need.
Batch Updates
When new mod versions are available:
- Open the Bulk Update dialog.
- Polymerium shows all mods with available updates.
- Review each update and check/uncheck.
- Exclude by tag — e.g. exclude all mods tagged
stability-watchfrom the update batch.
This gives you fine-grained control over mass updates without losing the convenience of "update all."
Using Tags in Deployment Rules
Tags aren't just for organization — they integrate with the deployment rules engine. You can create rules like:
- Skip all mods tagged
server-onlywhen deploying - Redirect all mods tagged
datapackto a custom path - Normalize filenames for mods tagged
legacy-name
See Deployment Rules → for the full rule syntax.