Goobaroo

Members
  • Posts

    233
  • Joined

  • Last visited

Posts posted by Goobaroo

  1. 14 hours ago, michaelopolis said:

    Where are the server files stored? I installed atm7tothesky and it made a folder in appdata, but nothing is in that folder. i did have to change the installed location container path to /appdata in order to get it to start at all, so I don't know if that changed things.

     

    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.

  2. On 1/7/2024 at 3:43 PM, KL1998 said:

    I am trying to run the VaultHunters3rdEdition docker but when having anyone in the OP variable I get the below prior to the server crashing:

     

    FAILED TO START THE SERVER AFTER ACCOUNT CONVERSION!

     

    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.

  3. @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 :)  

    Quote

    Changelog

    2.8.3

    Minor hotfix for servers

    Fixed

    Embedium will no longer attempt to load on servers

     

    • Like 1
  4. 15 hours ago, Killersplace said:

    hi

     

    after update of ATM9 to 9-0.2.19 i get this error on startup

     

    [main/ERROR] [minecraft/FlatLevelGeneratorSettings]: Unknown biome, defaulting to plains
    [main/WARN] [minecraft/Main]: Failed to load datapacks, can't proceed with server load. You can either fix your datapacks or reset to vanilla with --safeMode

     

    @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.

     

    2 hours ago, Carltonrp said:

    @Goobaroo Love your work on these. 

    Any chance we could get a config for https://feed-the-beast.com/modpacks/120-ftb-genesis ?

    Thanks in advance!

     

    @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.

    • Like 2
  5. @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.

  6. 8 hours ago, madson007 said:

    Hey Goobaroo,

    Just wanted to say thanks for the server configs for all these modpacks.

     

    I was wondering if it was possible for you to change your launch.sh script to include a variable to define the version of the server. That way you don't always have to update the script when a new version comes out. Then we just pass the variable along with the docker launch.

     

     

    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.

  7. 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.  

     

    1 hour ago, smashup1337 said:

    Hey,

     

     

    I updated docker to 0.2.14... and since then it has been checking the wrong version.

     

    I can´t start the server... :(

     

    Starting version check at https://files.minecraftforge.net/net/minecraftforge/forge/promotions_slim.json On the website there is the wrong Forge version that he is checking

     

     

    [12:44:56] [modloading-worker-0/INFO] [ne.mi.co.ForgeMod/FORGEMOD]: Forge mod loading, version 47.1.3, for MC 1.20.1 with MCP 20230612.114412
    [12:44:56] [modloading-worker-0/INFO] [ne.mi.co.MinecraftForge/FORGE]: MinecraftForge v47.1.3 Initialized
    [12:44:56] [Forge Version Check/INFO] [ne.mi.fm.VersionChecker/]: [forge] Starting version check at https://files.minecraftforge.net/net/minecraftforge/forge/promotions_slim.json
    [12:44:56] [Forge Version Check/INFO] [ne.mi.fm.VersionChecker/]: [forge] Found status: OUTDATED Current: 47.1.3 Target: 47.2.0

     

     

    ATM9_0.2.14.txt 12.52 kB · 0 downloads

     

    • Like 1