安装 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（越南语）
Українська（乌克兰语）
报告翻译问题
1 
举报此帖
I actually figured it out.
For those that are ever interested in hosting a dedicated PZ server. I wanted to share with you the issue that plagued us since adding the mods and explain why you needed to make a new character. There is nothing explicitly stating this in any of the wikis and honestly I am kind of shocked.
The Issue was daylength variable was working before adding mods, not working after I added Mods.
However the underlying issue was the following.
Findings: When you reset the map/start a new server. A unique .ini and sandbox are created. These values are set by ServerPlayerID and ResetID. It will also set random ports.
Issue: I was using the original map .ini file. Which was changing the values mentioned above. This was allowing players to connect to the server with previously created characters on a map that no longer existed forcing the settings to match that of the character. No Idea if this was because it was still running in memory. Is saved on the client connecting to the server. Or additional map saves are saved somewhere else on the server.
Solution: Ensure the changes being made are to tha map specific config files. Or if you reset the map/server make the changes to the .ini/sandbox the new map creates before a player connects to the server. Settings will stay.