Modpacks are first-class in Dylaris, in both directions: you can run one, and you can build and publish one, without leaving the panel.

Running a modpack as a server

Point the panel at a pack and it becomes a running server. No manual unpacking, no matching the loader version by hand, no separate install step.

A pack can come from:

Modrinth - browse it in the panel, or use a .mrpack
Your own packs - the ones you built, under My modpacks and the library
Technic packs
A backup you restore
An uploaded server-pack zip - the loader is detected automatically, so a CurseForge "Server Pack" works this way

CurseForge has no browser in the panel; upload its server pack instead.

Browsing and installing mods

The Modrinth browser is built into the panel. Search, pick a version, install it into a server. It resolves what it needs rather than dropping a jar and hoping.

The builder

The builder is the part most panels do not have. You assemble a modpack in the panel - mods, versions, configs - and it produces a real, distributable pack.

From there you can:

Publish to Modrinth directly, with your own credentials
Keep beta channels separate from stable
Freeze a release so an existing pack keeps working while you keep editing
Let collaborators work on the same pack and stay in sync

The cross-check tells you when a mod in your pack does not match the loader or Minecraft version you are targeting, before your players find out.

The library

Shared storage for jars, modpacks and assets, so the same file is not uploaded once per server. It can sit on local disk across several paths, or on S3-compatible object storage.