#Modpack version update taking forever to appear on Bisect Hosting JAR Menu?

1 messages · Page 1 of 1 (latest)

cunning scroll
#

First time I needed to update my server, it took about 1½ hours before the update was visible... not great, but workable.

Today, I pushed out an update for my modpack, andit has been 5 hours now. Ideally, I would be able to see this as soon as they are available on Modrinth, which is usually a couple minutes after I submit an update. I maintaint the modpack that I also run on the server, and ideally, I don't have to keep checking the dashboard in case it should become available.

Is this process manually, does it happen at set times during the day, or what is going on here?

It causes a lot of confusion from players, as I have to explicitly state whenever an update is out, but not available, and then again when it actually is. Ideally, I can just push the update, and update the server right away to avoid all this, something that is rather crucial if I need to push out a hotfix.

Sure, I could manually manage the server files, but then I can't test if the install through the dashboard works as intended.

image.png image.png
lament bison
#

All the installs from our JAR menu are handled by our support staff as they come in, typically it takes at most a few hours - I can give them a poke to give yours a look however!

#

To note while I get waiting for the update to come out on the JAR menu; we test to make sure the update starts up as intended on our end before pushing it yesyes

cunning scroll
#

Ah right, that modder still hasn't fixed their mod setup, that is my mistake. I forgot I have to manually change the manifest file before uploading to Modrinth.... Every time I update the pack 🙄

Will I normally get a heads-up if something like this happens in the future again?

#

For transparency sake, this is the culprit, in the "modrinth.index.json" file when uploading a new build.

All the other Roughly Enough Item mods are listed as unsupported, but this 1 mod is not, hence any modpack using Roughly Enough Professions will have this issue by default.

image.png
#

Sorry for the trouble @lament bison - I uploaded a fixed modpack update with the same version numbering, and installed a fresh test server on my end, just to be sure. It starts fine now, just as expected.

I just doublechecked the Git repo for the mod in question, as I filed this as an issue report a while back, but the author has seemingly not done what is required to fix it.

lament bison
lament bison
#

yeup! #🗒mod-updates message