-
Notifications
You must be signed in to change notification settings - Fork 278
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Back to old version of the game #590
Comments
Hi, Made it work with passing an additional ENV You'll also have to revert the game itself to a "default_old - previous stable" as you've mentioned before. Hope that'll help you in any way. |
Oky thank, where i have to put that command line? |
To your docker-compose file or docker run command line depends on how you deploy your server container can't tell how exactly it should be done on synoology. On usual linux installation it's done like this:
|
Hi, i have the two same problems, my english is very awful and my Docker Valheim Server doesnt work for same problem. I use mods and Bepinex, and when i use the same parameters on my stack like pwntfrag said, my Valheim comes to 0.213.4 version, but when valheim-updater runs (that it works like a little children, undercontrolled), my server comes to 0.214.2 version and doesnt work with Bepinex anymore. I hope that i can explain my problem... thx for your time |
Pues al final he conseguido bajar la version en el server, tu donde estas usando la imagen, yo uso docker pero en un server xpenology |
Pues yo tengo montado un OMV con un Portainer, y tengo metida esta imagen, pero no hay manera de detener el auto updater, el último Stack que he probado sin éxito ha sido este: `version: "3" services: y, nada, salta todo el rato el Valheim-updater y me vuelve a la última versión que no funciona el Bepinex con ella... |
vale te cuento yo ademas del los STEAMCMD_ARGS tambien he puesto SERVER_ARGS="default_old -previous stable" y me ha funcionado, por probar que no sea,pero en los STEAM_ARGS no tengo puesto "-validate" |
leí a lloesche (no recuerdo en dónde, pero lo leí por ahí), que si utilizas el STEAMCMD_ARGS, tiene el validate por defecto, si hace el validate es cuando actualiza el código, que si no se quiere utilizar había que añadir el "-validate" con cadena vacía, por eso lo tenía en el Stack, pero vamos, que pasaba de mi culo. He probado con lo que me has comentado y me sigue fallando, no sé qué es lo que tendré mal, de todas maneras he visto que ya están trabajando en un Fix del ValheimPlus, que a mi es el que me está dando guerra y creo que ya esperaré a que me funcione la última versión con todo (valheimPlus/ValheimPlus#793) Gracias por echarme una mano @SpanisHammer |
perdona que he andado liado, tienes abierto el puerto 9001 para entrar pot html a las opcines de Supervisor hay tiene una opcion que es para detener el update de valheim yo tambien le dia a Stop y luego reinicie con la opcion que tiene |
First of all, congratulate you on your work, I think I am one of the thousands who use it and we are happy to have people like you, who do things like this. Sorry for the english i used google translate hahaha...
Now I will tell you about my question/query/, I am using the image "valheim-server:debian10" on a Synology server using Docker, I have the BepInEx option enabled, but I have problems every time the server updates the game version, since some mods are no l compatible with the new version, and can´t login in the server or take a lot of error for the mods, but if i using the Steam console can go back to a previous version, in Manage/properties/beta you can choose "default_old - previous stable" which makes it possible to play locally, but in The server it's impossible because the game versions are different.
Is there any way to install a previous version of Valheim to be able to play until there is a mod update? .
or some way to make the updates be manually?
The text was updated successfully, but these errors were encountered: