Goobaroo

Members
  • Posts

    233
  • Joined

  • Last visited

3 Followers

Recent Profile Visitors

The recent visitors block is disabled and is not being shown to other users.

Goobaroo's Achievements

Contributor

Contributor (5/14)

53

Reputation

  1. @michaelopolis You changed the Container Path to /appdata/. That needs to be reset back to /data/ The way a path works in Docker, is that the container path is where the Host Path will be mounted inside the container. Changing it to /appdata/ means that the scripts couldn't create any of the files on startup.
  2. Every template has a value named "Installed Location:" this has the path where the files are stored. Normally appdata is on the array under /mnt/user/appdata and a sub-directory is created there on start.
  3. 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"?
  4. @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.
  5. @PaddyZockt 0.2.52 doesn't have a server release, it is client only. The 0.2.51 server should be compatible with it.
  6. @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.
  7. @Larunda Which container is that? That is only part of the log, I'd need the full log to see what went wrong earlier.
  8. I can't be used to install a specific modpack. I publish dockers of certain modpacks for people to install.
  9. 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.
  10. @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.
  11. @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
  12. @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.
  13. @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.
  14. 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