Update Failure with Vintage Story - Failure to update

CMDR_DrakeBD · September 10, 2023, 9:49pm

System Information

Field	Value
Operating System	Windows - Windows 11 Pro on x86_64
Product	AMP ‘Decadeus’ v2.4.6.4 (Mainline)
Virtualization	None
Application	Vintage Story
Module	GenericModule
Running in Container	No
Current State	Ready

Problem Description

Issue

Vintage Story will not update to the latest version 1.18.10 also there is alot of server configuration missing and world generation settings feel this should be done in the server browsers think as Vintage Story is becoming more popular now it needs some TLC

Reproduction Steps

Set server to 1.18.10
Start server so it downloads
Gets stuck in a boot loop of downloading the file and not installing then download again and again but nothing 404 error

Greelan · September 10, 2023, 9:56pm

The devs changed how the server is installed and run with 1.18.8. This has required a new template in AMP. Fetch Latest under Instance Deployment and you will see it in the list. You will have to create a new instance and transfer any save data across

VS is a community (me) made template. Anyone is welcome to contribute

Greelan · September 10, 2023, 10:59pm

I’ve also reminded myself that - aside from the sheer number of settings, which is tedious to put it in the template, especially when the documentation on some of them is poor - many of them have default null values, which AMP can’t handle. I have a long-standing request on GH for this to be fixed

github.com/CubeCoders/AMP

Allow Generic automap to tolerate null values in json configs

opened 11:22PM - 22 Jun 22 UTC

Greelan

enhancement Windows Linux generic-module

# This is not for requesting support for new games/applications To do this yo…u should go to https://github.com/CubeCoders/AMPTemplates and first attempt to build a configuration yourself - otherwise you can request a template from this repo. # Feature Request ## Feature Information:  Vintage Story has a default `serverconfig.json` file that is generated on first server start, which is used to configure various server settings. Some settings are set to `null`. If any of those settings are configured in AMP's `configmanifest.json`, AMP throws an error, complaining that the values cannot be null. Presumably when AMP reads the settings, it does not like the null value. Ideally AMP would still be able to read the settings, and then write whatever default value/value is set via `configmanifest.json`. I've looked at the option of supplying a `serverconfig.json` file as an update stage with the null values changed to some actual default value, but a number of aspects of the config file are generated by the server itself (mod paths, world configs) and are specific to the particular install, and so it is not feasible to supply a generic config file. ## I confirm: - [x] that I have searched for an existing feature request matching the description.

system · October 10, 2023, 11:00pm

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.