icepik

Members
  • Posts

    17
  • Joined

  • Last visited

Converted

  • Gender
    Undisclosed

Recent Profile Visitors

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

icepik's Achievements

Newbie

Newbie (1/14)

3

Reputation

  1. Thanks. I got in contact with him and he had me use "294420 -beta Alpha20.3" without the quotes and that worked for me.
  2. Ich777, just wanted to check in with you regarding the 7D2D docker. I've been trying to deploy a clean Alpha 20.3 stable (I don't want to run the recently released Alpha 20.4 stable), and every time I set the options in the configuration, steamcmd still pulls down 20.4 release. This should be the correct syntax according to the instructions. Am I missing something here? Thanks!
  3. Thanks ich777. Tested and verified working!
  4. It's just one mod, Undead Legacy. ul.subquake.com. Here's what's included with the mod when you download it: All the required files to run the server with Undead Legacy are included in the archive: BepInEx Mods doorstop_libs doorstop_config.ini run_bepinex_server.sh (used to launch the server) It works perfectly fine launching it with a full Linux distro when you launch the 7d2d server using run_bepinex_server.sh, just doesn't work from the docker instance. The only thing I can think of is something in the that sh file is causing issues maybe.
  5. Here's my log below when I start the container. The 7dtd server log doesn't show BepInEx getting loaded though when the server starts and the mods fail to load. ---Starting...--- ---Update SteamCMD--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1639697740 -- type 'quit' to exit -- Loading Steam API...OK Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK ---Update Server--- Redirecting stderr to '/serverdata/Steam/logs/stderr.txt' [ 0%] Checking for available updates... [----] Verifying installation... Steam Console Client (c) Valve Corporation - version 1639697740 -- type 'quit' to exit -- Loading Steam API...OK Connecting anonymously to Steam Public...OK Waiting for client config...OK Waiting for user info...OK Success! App '294420' already up to date. ---Prepare Server--- ---SaveGameFolder location correct--- ---Savegame location found--- ---UserDataFolder location correct--- ---UserDataFolder location found--- ---BepInEx enabled!--- ---BepInEx Version Check--- ---https://github.com/BepInEx/BepInEx--- ---BepInEx v5.4.18 up-to-date--- ---Server ready--- ---Start Server--- ---with BepInEx--- ---https://github.com/BepInEx/BepInEx--- Found UnityPlayer, hooking into it instead Found path: /serverdata/serverfiles/7DaysToDieServer.x86_64
  6. Would it be possible to get the container updated for 7dtd again so that when the BepInEx value = true it will call run_bepinex_server.sh instead of run_bepinex.sh ? The mod author updated BepInEx to 5.4.18 for his mod and now it's not hooking it in before the server launches.
  7. Thanks ich777! That was fast. I'm seeing this now after following your instructions: Not seeing any BepInEx in the output_log.txt in 7DaysToDie_Data folder either. The screenshot above says it's hooking into UnityPlayer instead. Is that possibly why? *edit* - I am seeing some BepInEx in the log file...was just further into the log than I thought it would be :D. Looks like it's working! Thanks for the quick update on this! You're awesome!
  8. Sure. It's included with SubQuake's Undead Legacy mod for 7DtD. With his A20 release, he has switched most of his code over to BepInEx and the .sh file is included in his Mod which is here: https://ul.subquake.com/. The requirement is that the server needs to be launched using the run_bepinex.sh file. Instructions for his A20 server are as follows: https://ul.subquake.com/dedicated-servers
  9. Correct. I don't need Bepinex integrated. Having the option to specify what launches the server would be the ideal way to do this. Currently, you mentioned it just launches 7DaysToDieServer.x86_64. Is there a way to have this as a container value, then I could say switch it to run a script when the container is launched (run_bepinex.sh), which then calls the game server to start? Does that make sense? Attaching the script here that I need to launch, but like I said, it's only for one mod, so you wouldn't want to force this on everyone (just be optional). run_bepinex.sh
  10. Ok, thanks. I did get a response from @Spectral Force Modifying the Dockerfile is a bit beyond my skillset
  11. I am on his Discord and chatted with him yesterday. He wasn't sure about it and was going to talk to someone who knew more about containers than he did. I don't think anyone has done this yet for 7 Days to Die. Would be great if you could look into it as it'll likely become more of an issue if more mod creators decide to use Bepinex. Thanks!
  12. This wouldn't be a requirement for every version though. Maybe just an option for the container value that has the default 7DaysToDieServer.x86_64 with the option to change the value to something different? run_bepinex.sh would call 7DaysToDieServer.x86_64 to start anyway after that script runs. I'll check in on the Discord channel. Thanks
  13. @ich777 - Is there a way with the 7 Days To Die docker to specify the launch script for the dedicate server? Is it currently using startserver.sh? I have no problems with Vanilla, but using the latest UL mod for 7DtD, it requires the dedicated server be launched using run_bepinex.sh to load the correct DLLs for the mod. I've modified the startserver.sh to call run_bepinex.sh but it doesn't seem to be working to launch. Just wondering if the container is calling 7DaysToDieServer.x86_64 exclusively?
  14. That worked when I did a clean install of the docker container, the game log showed alpha 19.5. When I stopped and restarted the container, it's now showing alpha 19.6 even though my GAME_ID value still shows 294420 -beta alpha19.5 Is there a way to just prevent steamcmd from running when the docker starts up? It's not necessary after the initial install of 19.5 as I wouldn't need to run it again after the first time.