[IDEA] Seperate packages for client and server packages

[BattleCh1cken]

Current Problem: The modpack in it's current form cannot be launched by a server out of the box, making it very annoying to use with tools like itzg's minecraft docker image.

https://github.com/itzg/docker-minecraft-server

Proposed Solution: My solution would be to create a separate download in Modrinth with a mrpack that contains just the mods required for a server to run. This would not only make it easier to start a server normally, but it would also mean that a Aged server could be started with this minimal docker-composes file, with no further work required:

version: "3.8"

services:
  mc:
    image: itzg/minecraft-server
    tty: true
    stdin_open: true
    ports:
      - "25565:25565"
    environment:
      EULA: "TRUE"
      MODRINTH_PROJECT: "https://modrinth.com/modpack/aged"
      MODRINTH_VERSION: "<version-id-of-the-server-package>"

    volumes:
      # attach the relative directory 'data' to the container's /data path
      - ./data:/data

[xR4YM0ND]

This will definetly come with future updates.

It annoyed me as well when i tried to automate server modpacks back then, so yeah i know how you feal.

Gimme some time, right now i go through hard times.

[BattleCh1cken]

No problem, thanks for maintaining this amazing modpack!

[xR4YM0ND]

Modrinth provides the mrpack for clients & servers.

You could download the server pack with mrpack-install Or use launchers like ATLauncher & install Aged as a server not as an instance.

If itzg docker minecraft supports this method, idk...