[Feature]: Automatic CurseForge mod management (auto-download + smart updates) #38

New Issue

OVERLORD · 2026-02-05T16:40:13+03:00

OVERLORD commented

2026-02-05 16:40:13 +03:00

Originally created by @Varmolord on GitHub (Jan 25, 2026).

Panel Type

Both Pelican and Pterodactyl

Feature Type

New configuration option

Feature Description

I would like to request automatic CurseForge mod management for the Hytale Pterodactyl Egg.

The feature would allow server owners to define CurseForge mods (Project ID / File ID or version rules), which would then be automatically downloaded and updated during server startup.

The goal is to remove manual mod uploads and make modpack maintenance significantly easier, similar to how hytale-server-docker handles mod management.

Problem or Use Case

Currently, managing Hytale mods requires manual downloading, uploading, and updating of mod files. Or using ModSync mod.

This becomes time-consuming and error-prone, especially when:

Running multiple servers
Maintaining modpacks
Updating mods frequently
Reinstalling or migrating servers

Automatic CurseForge mod management would:

Reduce human error
Speed up server setup
Make updates predictable and reproducible
Improve overall server administration experience

Proposed Solution

Add optional CurseForge mod management support directly into the Hytale Egg startup process.

Suggested implementation:

New environment variables:
- CURSEFORGE_API_KEY (user-provided)
- CURSEFORGE_MODS_FILE (e.g. mods.json)
A mod definition file (JSON/YAML), for example:
[
{
"projectId": 123456,
"fileId": 987654
}
]
On server startup:
- Read mod definitions
- Query CurseForge API
- Download missing mods
- Compare hashes / file IDs
- Update only changed mods
- Skip unchanged mods
Optional behavior:
- Auto-remove mods not listed
- Dry-run / update-only mode
- Logging of downloaded / updated / skipped mods

This logic could be implemented as a startup script inside the Egg and does not require changes to the core Pterodactyl panel.

A similar approach is already proven in:
https://github.com/Hybrowse/hytale-server-docker

Additional Context

This feature would be fully optional and backwards-compatible.

Server owners who prefer manual mod management can simply ignore it.

The approach respects CurseForge ToS by requiring users to supply their own API key.

This would significantly improve quality-of-life for Hytale server hosting on Pterodactyl or Pelican.

Pre-submission Checklist

I have searched existing issues to make sure this feature hasn't already been requested

Originally created by @Varmolord on GitHub (Jan 25, 2026). ### Panel Type Both Pelican and Pterodactyl ### Feature Type New configuration option ### Feature Description I would like to request automatic CurseForge mod management for the Hytale Pterodactyl Egg. The feature would allow server owners to define CurseForge mods (Project ID / File ID or version rules), which would then be automatically downloaded and updated during server startup. The goal is to remove manual mod uploads and make modpack maintenance significantly easier, similar to how [hytale-server-docker ](https://github.com/Hybrowse/hytale-server-docker) handles mod management. ### Problem or Use Case Currently, managing Hytale mods requires manual downloading, uploading, and updating of mod files. Or using [ModSync](https://www.curseforge.com/hytale/mods/modsync) mod. This becomes time-consuming and error-prone, especially when: - Running multiple servers - Maintaining modpacks - Updating mods frequently - Reinstalling or migrating servers Automatic CurseForge mod management would: - Reduce human error - Speed up server setup - Make updates predictable and reproducible - Improve overall server administration experience ### Proposed Solution Add optional CurseForge mod management support directly into the Hytale Egg startup process. Suggested implementation: 1) New environment variables: - CURSEFORGE_API_KEY (user-provided) - CURSEFORGE_MODS_FILE (e.g. mods.json) 2) A mod definition file (JSON/YAML), for example: [ { "projectId": 123456, "fileId": 987654 } ] 3) On server startup: - Read mod definitions - Query CurseForge API - Download missing mods - Compare hashes / file IDs - Update only changed mods - Skip unchanged mods 4) Optional behavior: - Auto-remove mods not listed - Dry-run / update-only mode - Logging of downloaded / updated / skipped mods This logic could be implemented as a startup script inside the Egg and does not require changes to the core Pterodactyl panel. A similar approach is already proven in: https://github.com/Hybrowse/hytale-server-docker ### Additional Context This feature would be fully optional and backwards-compatible. Server owners who prefer manual mod management can simply ignore it. The approach respects CurseForge ToS by requiring users to supply their own API key. This would significantly improve quality-of-life for Hytale server hosting on Pterodactyl or Pelican. ### Pre-submission Checklist - [x] I have searched existing issues to make sure this feature hasn't already been requested

OVERLORD added the enhancement label 2026-02-05 16:40:13 +03:00

OVERLORD closed this issue

2026-02-05 16:40:14 +03:00

OVERLORD commented

2026-02-05 16:40:15 +03:00

@NATroutter commented on GitHub (Jan 28, 2026):

Thats a cool idea but also a lot of work, i have to take a look at it when i have more time

@NATroutter commented on GitHub (Jan 28, 2026): Thats a cool idea but also a lot of work, i have to take a look at it when i have more time

OVERLORD commented

2026-02-05 16:40:16 +03:00

@scotthowson commented on GitHub (Jan 28, 2026):

https://github.com/scotthowson/hytale-server-pelican

I did it.

@scotthowson commented on GitHub (Jan 28, 2026): https://github.com/scotthowson/hytale-server-pelican I did it.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: starred/egg-hytale#38