Cài đặt Steam
Đăng nhập
|
Ngôn ngữ
简体中文 (Hán giản thể)
繁體中文 (Hán phồn thể)
日本語 (Nhật)
한국어 (Hàn Quốc)
ไทย (Thái)
Български (Bungari)
Čeština (CH Séc)
Dansk (Đan Mạch)
Deutsch (Đức)
English (Anh)
Español - España (Tây Ban Nha - TBN)
Español - Latinoamérica (Tây Ban Nha cho Mỹ Latin)
Ελληνικά (Hy Lạp)
Français (Pháp)
Italiano (Ý)
Bahasa Indonesia (tiếng Indonesia)
Magyar (Hungary)
Nederlands (Hà Lan)
Norsk (Na Uy)
Polski (Ba Lan)
Português (Tiếng Bồ Đào Nha - BĐN)
Português - Brasil (Bồ Đào Nha - Brazil)
Română (Rumani)
Русский (Nga)
Suomi (Phần Lan)
Svenska (Thụy Điển)
Türkçe (Thổ Nhĩ Kỳ)
Українська (Ukraine)
Báo cáo lỗi dịch thuật
1 - The link to your youtube doesn't work
2 - There have been changes to where character/world saves are located. If you have cloud saves enabled the saves go into the steam user data folders (not appdata) I think saving to the appdata folders is still valid but not sure. Maybe that the server looks in appdata but if you have a world saved with cloud it will not be in there. ?
3 - FYI for those that don't know, the Valheim Dedicated Server download does include a pdf doc with some of this info...
4 - In the documentation pdf that comes with Valheim Dedicated Server download it mentions there are default settings that will save the world periodically. Includes 4 backups and you can change that number along with the timing of the saves (2 hours, 12 hours, etc)
I'm still trying to get a Virtual machine setup to run the valheim server and this guide is helping with all that. :)
Thanks
- Jebbalon
[code]
Get-ChildItem -Path "$targetRootPath" |
Where{$_.Attributes -like '*Directory*'}|
Sort-Object -Property {$_.Name} -Descending |
Select -Skip 14 |
Remove-Item -Force -Recurse [/code]
Sadly the task scheduler can't handle PS-files by default, so you need another script to run the powershell-script.
E.g. execValbak.bat (there are other ways to do this, but this seems to be the easiest)
[code]
powershell.exe -ExecutionPolicy Bypass -File "D:\Temp\valheim Backup\valbak.ps1" [/code]
If this doesn't work, you might need the full path of the powershell.exe
The "ExecutionPolicy" is needed to allow the script's execution, by default Microsoft considers this as a possible thread. (Thanks for not letting me execute my own scripts...)
Now use the .bat file in your task scheduler and you're done
... of course modify the target-directories first
Feel free to use any of this stuff .. or not :)
(Whoops, this got a "little" longer than expected - so I had to split it up)