Install Steam
login
|
language
简体中文 (Simplified Chinese)
繁體中文 (Traditional Chinese)
日本語 (Japanese)
한국어 (Korean)
ไทย (Thai)
Български (Bulgarian)
Čeština (Czech)
Dansk (Danish)
Deutsch (German)
Español - España (Spanish - Spain)
Español - Latinoamérica (Spanish - Latin America)
Ελληνικά (Greek)
Français (French)
Italiano (Italian)
Bahasa Indonesia (Indonesian)
Magyar (Hungarian)
Nederlands (Dutch)
Norsk (Norwegian)
Polski (Polish)
Português (Portuguese - Portugal)
Português - Brasil (Portuguese - Brazil)
Română (Romanian)
Русский (Russian)
Suomi (Finnish)
Svenska (Swedish)
Türkçe (Turkish)
Tiếng Việt (Vietnamese)
Українська (Ukrainian)
Report a translation problem
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.