Tags & Batch Operations

Last updated on

Tags and Groups

A package group gives each entry one source association and a deployment priority. Tags label entries independently: an entry can carry several tags whether it belongs to a modpack group, recipe group, collection, or the loose group. Use tags to filter and operate across groups without changing their membership or priority.

For example, Sodium might have:

performance  core  QoL  stability-watch

This 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

1. Select an instance and go to the Setup tab.
2. Each mod in the list has a tag field.
3. Type tags separated by commas or spaces. Tags are freeform — use whatever makes sense to you.

Tags are stored on each package entry in an instance. The same project can have different tags in different groups or 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:

1. Open the Bulk Update dialog.
2. Polymerium shows all mods with available updates.
3. Review each update and check/uncheck.
4. Exclude by tag — e.g. exclude all mods tagged stability-watch from the update batch.

This gives you fine-grained control over mass updates without losing the convenience of "update all."

For persistent per-package skip and hold decisions, see Bulk Updates.

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-only when deploying
• Redirect all mods tagged datapack to a custom path
• Normalize filenames for mods tagged legacy-name

See Deployment Rules → for the full rule syntax.