Jump to content

tinbolw

Vintarian
  • Posts

    2
  • Joined

  • Last visited

tinbolw's Achievements

Wolf Bait

Wolf Bait (1/9)

2

Reputation

  1. Thought I'd contribute what worked for me on Linux Mint 22.1, as I managed to get a server up and running. I followed the guide posted by ChuckGlarman (thanks, by the way) but the server would not start with an error similar to this: VintagestoryServer.dll is not running. Error! User vintagestory could not start VintagestoryServer.dll! Please check /var/vintagestory/data/Logs. What worked for me was editing step five of his guide to be export DOTNET_ROOT=$HOME/.dotnet export PATH=$DOTNET_ROOT:$DOTNET_ROOT/tools:$PATH instead of export DOTNET_ROOT=$HOME/.dotnet export PATH=$PATH:$DOTNET_ROOT:$DOTNET_ROOT/tools which I believe allows server.sh to prefer using the dotnet SDK installed to ~/.dotnet instead of any version that may otherwise be installed on the system. Following the recent update to VintageStory 1.21.0, I had to also install version 8.0 of the dotnet SDK using ./dotnet-install.sh --channel 8.0 with the dotnet install script. Since I migrated my server from Windows, I also had to update the serverconfig.json in the server data folder to take the new correct mod paths and save file locations, along with converting the path styles from Windows to UNIX. Since I was copying files (world files, config, etc.) from a different mounted partition, I had to sudo cp the file, which by default makes root the owner of the copied file. To get around this, I just copied the file to a location owned by vintagestory (i.e. the server data folder) then copied it again as vintagestory without sudo, which I found was the easiest way of making vintagestory the owner of the file, in case that is also necessary. Hope this helps someone.
×
×
  • Create New...

Important Information

We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.