Issue installing server via Pterodactyl

[KRDucky]

Modpack

FTB Evolution

Modpack version

1.7.0

Launcher

Other...

Has the pack been modified

No

Log Files

1dbfcd74-4a1a-49d2-8846-27aec78a67a9.log

Describe the bug

pterodactyl script asks for Modpack ID, Modpack Version and Modpack Version ID. Setting Modpack ID to 125, Modpack version to 1.7.0 and Modpack Version ID to 100018 outputs the following: "Error fetching modpack: version does not exist"

Steps to reproduce

1: Use the pterodactyl FTB egg
2: input the Modpack ID
3: input the Modpack Version
4: input the Modpack Version ID
5: select the java version to 21
6: run the installer script
7: errors

Expected behaviour

complete the install and launch the server

Screenshots

No response

Additional information

The script expects me to somehow conjure up the modpack version Id from: "The modpack api version ID. needed if not using the string for the version. Example FTB Revelations version id for version "2.0.2" is 86. which would come out as: https://api.modpacks.ch/public/modpack/5/86"

[phit]

whatever script you use is outdated and broken, that API is no longer being updated, not FTB's problem

[KRDucky]

I understand that FTB doesnt have direct control of it but I am wondering what the new API is and how it should be used so I can submit a pull on the Pelican/Pterodactyl and AMP githubs to get their scripts updated with the new API.

…

On Sun, Jan 12, 2025 at 9:13 AM Philip T. ***@***.***> wrote: whatever script you use is outdated and broken, that API is no longer being updated, not FTB's problem — Reply to this email directly, view it on GitHub <#6578 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAMXT2Y4XNH6PYE4FVDVO6D2KKA73AVCNFSM6AAAAABU62THHOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKOBVG43TEMRZGQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[KRDucky]

This is a link to the script on github: https://github.com/pelican-eggs/minecraft/blob/main/java/ftb/egg-f-t-b-modpacks-ch-server.json

And this seems to be the relevant part of the above script that needs to be changed to the new API and method:

JSON_DATA=$(curl -sSL https:\/\/api.modpacks.ch\/public\/modpack\/search\/8?term=\"${encoded_search_term}\")\r\n \r\n # grabs the first modpack in array.\r\n FTB_MODPACK_ID=$(echo -e ${JSON_DATA} | jq -r \".packs[0]\")\r\n fi\r\n \r\n if [ -z ${FTB_MODPACK_VERSION_ID} ] && [ ! -z ${FTB_VERSION_STRING} ]; then\r\n # grabs the correct version id matching the string.\r\n FTB_MODPACK_VERSION_ID=$(curl -sSL https:\/\/api.modpacks.ch\/public\/modpack\/${FTB_MODPACK_ID} | jq -r --arg VSTRING ${FTB_VERSION_STRING} '.versions[] | select(.name == $VSTRING) | .id')\r\n fi\r\n}\r\n\r\nfunction run_installer {\r\n # get architecture for installer\r\n INSTALLER_TYPE=$([ \"$(uname -m)\" == \"x86_64\" ] && echo \"linux\" || echo \"arm\/linux\")\r\n echo \"ModpackID: ${FTB_MODPACK_ID} VersionID: ${FTB_MODPACK_VERSION_ID} InstallerType: ${INSTALLER_TYPE}\"\r\n\r\n # download installer\r\n curl -L https:\/\/api.modpacks.ch\/public\/modpack\/0\/0\/server\/${INSTALLER_TYPE} --output serversetup\r\n chmod +x .\/serversetup\r\n \r\n # remove old forge files (to allow updating)\r\n rm -rf libraries\/net\/minecraftforge\/forge\r\n rm -rf libraries\/net\/neoforged\/forge\r\n rm -f unix_args.txt\r\n \r\n # run installer\r\n

[phit]

as far as I know the new API has no public information and wasn't even announced, however some other third parties have implemented it

ATLauncher/ATLauncher@bbd1fab#diff-c3bf7d38ec5b939e788272094c1a305b109e618b67753b7e8a2a57881c2d8a6e