Goobaroo

Members
  • Posts

    234
  • Joined

  • Last visited

Everything posted by Goobaroo

  1. @BearBearian Actually, the latest server version Pre-Release 25 for The Decursio Project does not start on its own. They shipped an incompatible version of forge. I've opened a bug with the pack maintainers. Hopefully there will be a 26 with a fix. If you want to install my current one that installs the buggy v25, I can give you the fix. After you've run it for the first time and it has crashed. Go into /mnt/user/appdata/decursioprojectexpert and delete the forge files: rm -vf forge* Edit the start.sh and change FORGE="36.2.33" to FORGE="36.2.34" Start the container again in Unraid. It will download the correct forge version and start.
  2. @Schicksal The mods should be all activated. The container downloads and installs the server pack on first run. So if the container is running, it should be good. Startup can take a few minutes for all the mods to load and for the world to be ready to join with the client. Authentication servers are managed by Mojang/Microsoft. You'll need to make sure that you are logged into the Minecraft account (I think they are all Microsoft accounts now) in the Curse launcher before starting the modpack instance.
  3. @thunfischbaum Can you delete Server-Files-1.0.8.zip out of your /mnt/user/appdata/allthemods8 directory? It will restart the install, it looks like it did not complete for some reason. I'm playing this pack right now on my server and know it should work.
  4. @aoffan16 Direwolf20 1.18 will work if you force the container to update and get latest. I fixed the issue. @thunfischbaum Can you provide the whole log? It looks like it didn't download the server install for some reason.
  5. @Schicksal No bother. So there are many ways to play Minecraft, these containers are specific to modded Minecraft. Meaning other developers have released mods that modify how Minecraft runs and behaves. Modded Minecraft still uses the vanilla Minecraft that is shipped by Mojang/Microsoft. If he wanted to run All the Mods 8, he would also have to run the All the Mods 8 client install with all of the supporting mods. The easiest way to do this is to use a 3rd party Minecraft loader. It will download all the necessary files required. CurseForge has their own loader, you should be able to find it here: https://www.curseforge.com/minecraft/modpacks. Modpacks vary widely, with the versions of Forge, and mods used and all need to match in order for things to work as expected. But the CurseForge Launcher https://download.curseforge.com will handily setup everything you need. Modded Minecraft is also incredibly deep, with lots of interesting items, blocks and mechanics added to the game. It's a lot of fun, and usually a let's play is the best way to learn a pack. I can recommend ChosenArchetect, he is kid friendly and he is doing a play through of All the Mods 8 right now, here is the playlist. Hope that makes sense. If I can clarify further or you have questions just reach out, I'd be happy to help. Edit: There really isn't anything to configure with the server. The latest version of the Modpack the server is built for should be the default install. You just need to install the same client version and you should be good to go.
  6. @Tietge86 Done. Let me know if you run into problems. Please check the 1st post for FAQs.
  7. What server are you asking about? Can you provide the full log? Is this an upgrade or a new install?
  8. Fixed. Just delete the 5.0 server install zip and force update the docker image.
  9. @MVLP Yep, just force an update to pull the new latest. I fixed the 1.5.0 release, it was skipping the install. Should be all good now. @djmulder Direwolf20 1.19 should be available as soon as the app store syncs.
  10. Just an FYI if you came here because it looks like the version of your container was removed. I was attempting to rename some of these so they were a little nicer, but apparently that breaks everything. I've reverted my changes and I'm waiting for unraid community apps to re-sync to my stuff. I think it is every 6 hours or something from this post.
  11. @Georg2U I've added it, let me know if there are any issues. @BuB3944 I've added FTB Revelation too.
  12. @AusNaminator Should be fixed. Pull the latest version again, and delete the install zip that is there for update-4.1. That will force a re-install. Or don't update, delete the mods folder and the zip for update-4.1 and start the container, it will re-install.
  13. @xstefanx Thanks for the heads up. It should be available as update-4
  14. @xstefanx thanks for letting me know. This is all automated on my end. I built pipelines that call the Curseforge APIs to help build out the server containers. So if it's not on CurseForge or FTB, then the system doesn't know about it and it doesn't get updated. Vault Hunters 3rd edition is in alpha, not even beta, so as they work through their issues things will stabilize with time. I don't have the time beyond maintaining the automated workflow. Hunting down individual packs that require manual changes simply isn't an option. I'm sure when they get closer to release they will have a more stable release and server updates. I hope that helps.
  15. @Taiwendo I've fixed it. You need to do 3 things In your docker menu click the advanced in the top right. And then click the force update for the ATM8 application. Delete the Server-files-1.0.6b.zip file in /mnt/user/appdata/allthemods8 start the server, it will update. @CleverError Templates that contain those lists don't always update automatically. This is a long fight in the application development community for Unraid. If ever in doubt, look at the docker hub. https://hub.docker.com/repository/docker/goobaroo/stoneblock3
  16. @Siggz Probably because you're still pointing to the siggz tag I made for you that is the previous version. Just remove the tag, or replace it with latest and it will get the latest build. goobaroo/ftbdirewolf20_118:siggz -> goobaroo/ftbdirewolf20_118
  17. It's beginning to sound like you may have some bad RAM and this container is hitting it with your current running config.
  18. Vault hunter 0.0.2 was a client side update only, there was no server for that release. They don't always release a new server for each version.
  19. When docker stops a container it does send a shutdown signal to the process. After 10 seconds it will send a kill. I can take a look at improving that within docker, but it shouldn’t matter that much. Are you running into an issue? You can stop the server in game if you have added yourself to the OPS variable in the server config in Unraid. Then just run /stop in game.
  20. @DarthLlama TLDR; Changing the server properties port will break the container and is not necessary to access it on another port. See here for a longer explanation:
  21. @sportsziggy Thanks. Did need some work but should be available as soon as unraid syncs up with my list of apps. Edit: Vault Hunters 3rd Edition 1.18.2 is available.
  22. @sportsziggy I don't see a vault hunters release on curseforge and that is where the server pack gets installed from. When there is an actual release I can update it.
  23. @CRDark That wasn't quite ready for release. But I have fixed it up properly now, so it should work if you force an update or remove and completely re-install. You'll have to wipe out the files in the rlcraft appdata directory in order for it to install properly. To answer your other question about a guide, I don't have one. Fundamentally the containers are an install/update script. That downloads the version of the server files needed for a particular mod pack and exposes the environment variables from the unraid application config to allow it all to run. Each server has its particular version of Java as the parent container that runs the server. For some packs it is easy, there is an install script. For others, like RLCraft no help is given other than some server requirements and I had to write an installer to take care of it.
  24. @Marik900 That's a problem with the pack, not the container. But I can suggest some solutions. You can delete the serverinstall_100_2295 file and the mods directory and restart the container. That should redo the install, probably fix the problem.