安装 Steam
登录
|
语言
繁體中文(繁体中文)
日本語(日语)
한국어(韩语)
ไทย(泰语)
български(保加利亚语)
Čeština(捷克语)
Dansk(丹麦语)
Deutsch(德语)
English(英语)
Español-España(西班牙语 - 西班牙)
Español - Latinoamérica(西班牙语 - 拉丁美洲)
Ελληνικά(希腊语)
Français(法语)
Italiano(意大利语)
Bahasa Indonesia(印度尼西亚语)
Magyar(匈牙利语)
Nederlands(荷兰语)
Norsk(挪威语)
Polski(波兰语)
Português(葡萄牙语 - 葡萄牙)
Português-Brasil(葡萄牙语 - 巴西)
Română(罗马尼亚语)
Русский(俄语)
Suomi(芬兰语)
Svenska(瑞典语)
Türkçe(土耳其语)
Tiếng Việt(越南语)
Українська(乌克兰语)
报告翻译问题


To activate a scenario you just need to edit the dedicated yaml after you have imported scenario folders.
If you are trying to load a BP scenerio, then it can be quite a bit more difficult. Not hard really, just a lot of precise steps.
Which Scenerio are you wanting to run?
Many thanks
1. subscribe to the BP.
2. run it a moment in SP, to make sure its downloaded (may not be required.
3. locate the folder where the BP is loaded.
Steam/steamapps/workshop/content/383120/xxxxxx/ where xxxxxx is a number. you can look into that folder and verify the description,preview.
4. Load FileZilla or other FTP program on your system, so you can upload the scenerio to the server.
5. upload the scenerio.
6. stop the server
7. edit the dedicated.yaml file to tell the server to use that scenerio.
8. start the server and try and get in.
If you need specific help, friend me, or google "empyrion Nitrado dedicated" and you should find a more detailed list.
Thank you for all these details, this helps a lot. Just one question about point n°7. What exactly am I supposed to edit in the yaml file, what is the text I should replace with and where is the part to be edited situated in the file? (Sorry that's 3 questions !)
Many thanks for your help
Also important is GameName: mygame (this will be the name of the save in the save file folder. You MUST change names or delete the folder each time you start a new game, so it recreates it.
you will find it in \Emperion\Saves\mygame. This is what the server will use to load the save, so to wipe a server, just rename it, or delete the folder.
There is a fancy settings configuration program that comes with the server, but under certain conditions, I found that it corrupts the dedicated.yaml file. It took me a while to sort it all out. Editing the file manually with the file edit function works fine.