Jump to content


Very Important Vintarian
  • Content Count

  • Joined

  • Last visited

  • Days Won


skol last won the day on January 13

skol had the most liked content!

Community Reputation

28 Excellent

About skol

  • Rank
    Bronze Caster

Recent Profile Visitors

964 profile views
  1. I like the idea and the way how it is presented! Thanks!
  2. I really want to support this discussion topic by describing some possible specs/solutions. In particular I have two favorite solutions that could easily coexist (without further preference, except the point that 1. is probably faster/easier to implement) 1. Linen stacks are stackable when empty (lets say up to 16) and are placeable/pickable on the ground when full (same mechanics as beehives). A placed linen sack should occupy 1/4 blocks as Yukihira suggested (0,5 x 0,5 x 1,0), per default oriented like 1/4 block pillars. In this orientation it should be easy to pick them up, but it should not be allowed to place other blocks on top of them. 2. Dropped items of an irregular "rounded" shape (ore chunks, coal, stones, nuggets, etc.) will add to a loose irregular pyramidal "pile-of" (multi-block) structure of given type with a constant 36° angle of slope (2/5 block height for each block width, means a pile of 2 block height has a with of 5 blocks). The area of the pile grows with the number piled items the (8 items covering each block, times 8 for nuggets). The length of piles can of course become greater than the width, forming kind of rampart. Solid structures should be able to stabilize the side of a pile, forming a kind of bank. Getting items from a pile means "digging" block by block, causing loose material to slide. This could be part of general block physics where (uncompressed) sand, gravel, and soil would behave the same way. This could also be part of world generation, forming talus slopes and crees.
  3. Distro / Kernel release : Ubuntu Mate 18.04 LTS / 4.15.0-22-generic Mono / .NET package version : mono-complete Graphics driver version : NVIDIA binary driver 390.48 (proprietary) Works for client, mp server or both : client + multiplayer server Installation method used : server.sh Hacks (if needed) : none
  4. As we have a decent number of Linux users in the community, I would be great to collect the experience, for which distros/configurations it could be managed to run VintageStory. Please share in the comments your working VS linux configuration in the following way: Distro / Kernel release : Ubuntu Studio 16.04 LTS / 4.4.0-127-lowlatency Mono / .NET package version : mono-complete Graphics driver version : NVIDIA binary driver 384.130 (proprietary) Works for client, mp server or both : client + multiplayer server Installation method used : server.sh Hacks (if needed) : server.sh needs at least wget version 1.17.9 (not in the standard repo of Ubuntu 16.04) Update as of 8th of March 2020: From a bug report it looks like mono 4.2.1 is not sufficent any more, even for a server only!
  5. The root certicates were also the root cause for the connect issue with wine. In Ubuntu, mono comes with certificates. Good to know how to handle this in Gentoo!
  6. The last time I got this connect issue was when I tried to install/run VS with wine (this was version 1.0.2 - there was no installation tarball at this time). I never had this issue with mono. Which mono version do you have installed?
  7. @tony Liberatto Maybe you and the other mods want to disclose their personal info to the friendly community, too. This would allow to communicate at the same level of information.
  8. #metoo please I already joined after setup but that was before the whitelist was set up Vintage Story Player name: skol Age: 100/2 - 1 boring old-fashioned IT-Professional from Germany Do you agree to follow the server rules?: of course
  9. Yes, that's the scope. And it is of course a console interface and not a fully flegded and feature-rich GUI. But as Tyron mentioned, the script should be, let's say, encapsulated, being at least possible to handle multiple instances/installations. But I think the script already is encapsulated this way and I only need to test and describe how to separate the custom options that were chosen for each install. This documentation should prevent experiments of users to end with frustration and complains.
  10. @TyronYour wish is my command. Uploaded the current script with some tweaks and provided documentation, see https://github.com/zkol/vsadmin The documentation should explain e.g. how to run multiple instances on different ports in parallel. Documentation how to install different versions in parallel will follow. After this I'm going to split the script to create a basic (aka "more minimal") version that uses per default a data path relative to the script location as Tryon suggested (using internally the --dataPath arg to make this happen). home/vintagestory/1.5.2 server => here should reside the script of v1.5.2 data => this would be derived from script location: ../data /home/vintagestory/1.5.1 server => here should reside the script of v1.5.1 data => this would be derived from script location: ../data I think the basic script could maybe offer a stable backend interface for other tools like the more powerful remote web GUI that @Milo Christiansen announced. I think it would be helpful if this basic script would pass every invocation parameter transparently to VintagestoryServer.exe in a way that overrides the default parameters.
  11. @Milo Christiansen Don't get what you mean with big fuss. @Tyron seems to think about changing the datapath logic again. That's his choice. I he wants to keep the mentioned benefits of the --datapath option or not is his choice. I'm just waiting patiently for his decision and not part of any fuss.
  12. @Tyron In the comments above you asked about having packages for linux distros. With a distro package it would be impossible to have multiple versions of the same package installed - so you would force the package maintainer to create a new package for each version.
  13. @Tyron I know this of course. I left this detail out because it is not crucial for the decision. Before: Relative datapath per default. Now: independent datapath configurable. Point to discuss: Relative datapath per default. One argument for the discussion: By switching back to relative datapath, you are forced to install the full software for each instance you want to run.
  14. @TyronIn principle, thats where we came from before configurable datapath was introduced. Of course you can roll back this with all the consequences regarding backward compatiblity. But maybe it is less trouble to keep this approach and have a start/stop that is capable to handle this.
  15. Good to hear that this works for you! I understood that you installed the server tarfiles manually and managed your own folder structure, right? How do you start the server? Does "shortcut" mean a mini-script like "mono VintagestoryServer.exe --datapath whatever" ?
  • 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.