Goobaroo

Members
  • Posts

    231
  • Joined

  • Last visited

Everything posted by Goobaroo

  1. I'm not sure I understand the question as written. It sounds like your port forwarding isn't working possibly? What do you mean that your "server didn't communicate via internet"?
  2. @PaddyZockt Hmm, there is not a server pack up for the 0.2.52 on curseforge, without one I can't publish one. Maybe it will show up a bit later.
  3. @PaddyZockt 0.2.52 doesn't have a server release, it is client only. The 0.2.51 server should be compatible with it.
  4. @Mofarocker33 It's still on the store, it just has spaces in the name. If you search by my name you'll see it too.
  5. @Larunda Which container is that? That is only part of the log, I'd need the full log to see what went wrong earlier.
  6. I can't be used to install a specific modpack. I publish dockers of certain modpacks for people to install.
  7. What is in your ops.txt file? It may be called ops.txt.converted if it has already been processed by the game. It should be in the vaulthunters3 appdata directory.
  8. @SimpleEnigma331 Oh, right. I was working on that. I'm, uhh... still working on it? I'll see if I can find some time later this week.
  9. @skiiwee29 I'm just producing wrappers for installing the modded servers. I'm not going to manage issues related to the packs themselves. I'm sure they will get fixed on the FTB side. I monitor for new releases and push out updates as they go live. Update: They did fix it
  10. @skiiwee29 seems to be a problem with the pack itself. The error I got was for the mod `embeddium-0.2.12+mc1.19.2.jar` Removing it got the server to start.
  11. @obiwog I'm not sure what happened in your install. That error there looks like an incomplete jar file trying to be loaded. But I just upgraded mine from 0.2.14 to 0.2.34 and it worked fine. The only issue I saw was that the old `packmenu` directory wasn't being updated, so I've pushed a fixed 0.2.34 image.
  12. Are you sad that there is a new version? There is a new docker with the latest 9-0.2.31. It was pushed 2 days ago. https://hub.docker.com/repository/docker/goobaroo/allthemods9/general
  13. @jsgilly20 in the docker settings for Pixelmon, you can add a version tag to the end. When there is no version, docker defaults to grabbing the tag labeled latest. You can see all the tags on dockerHub goobaroo/pixelmon -> goobaroo/pixelmon:9.1.7
  14. It appears that the application list has not been updated in a few days. Last update Dec 1, 2023 18:05. Is this a pipeline that runs somewhere?
  15. Weird. Thanks, I've reverted it, the latest tag should be 3.12.4 again.
  16. @smashup1337 Roguelike-Adventures-and-Dungeons-2 is up.
  17. @Killersplace Does it start up? That error shouldn't prevent startup, it is just a mod error that is then taking a default value. So it should be fine. @Carltonrp Sure, should be up in the morning. @smashup1337 I can take a look when I get a free moment. Curse packs are a bit more work than FTB packs.
  18. @waggs15 If there is a memory leak with forge generate, it is only going to persist for as long as the container is up. Pre-generating chunks can help when there is a lot of exploring going on with multiple players. That initial generation of a chunk as a player explores can cause a lag spike. All the Mods 8 is a pretty large pack, I think it has 332 mods? Java Minecraft is primarily affected by Single Threaded Performance. There can also be a minor hit to performance for assigning too much memory, 12gb is probably fine. The performance hit happens during garbage collection and having to process so much memory.
  19. There are a few issues with that approach. Just having the version does not inform the URL to the server files that need to be downloaded to install. An incorrect version, could further confuse an installation by not being able to get the files. Not all versions have corresponding server releases, some are client side only. There are also sometimes fixes and changes to the launch.sh file that need to be fixed in order for the server to launch at all. The Java version can potentially change between versions which is core to the docker container. It's really a java version, that happens to install a java application being the Minecraft server. Edit: I forgot the best one... Minecraft modpack development is not all equal. Version numbers can be all over the place and hard to interpret. Some pack publishers have semfor versions (v1.2.3) some just make up version numbers (v 2-40i). It's kind of a hot mess. Really, it would be nice if instead of shipping modded server files as installs the hosting sites distributed docker containers on their own.
  20. That is just an information message stating there is a newer version. The release nodes for ATM9 0.2.14 states Forge Version is 47.1.3. The log you provided has no errors. I was able to start this version of ATM9 on my server and join with the client.
  21. ATM 9-0.2.12 should be there now. Looks like part of the process for building the containers was being blocked on Curseforge's side.
  22. Are people still experiencing an issue with ATM9? I just updated my server to 0.1.12 and it is working fine for me.
  23. That's unfortunate, but they didn't post a server pack on curse. You could probably manually patch that particular mod or wait for their next update. Unless it is a breaking change that needs to be fixed.