LjProdigy18

With doors being able to be tied to keys triggers to escape pois, usually at the end of the dungeon crawl, will we see uses of them being tied to other triggers to close on the player. Say a switch that opens a vault loot room, but have a roll door shut down behind and close the player in and zombies spawning? Maybe they open back up once the triggered spawn is dead, or on a short timer to have a kill room trap for players to encounter.

Can we please have added options in the base game to adjust wandering/roaming hordes? Size/Frequency. I know there are some mods/modlets out there that do this, however a lot of people also do not like to run mods. (especially on the server I run). I have seen many forum posts and comments on reddit looking for this option and some attempts at xml editing to do this. However, it is a giant pita and not a lot of information out there on how to do it. It would be great to be able to see a couple slider options like we now have for the blood moon settings. This would then allow us to be able to set up worlds with Blood Moon disabled, but with high zombie count wandering hordes that frequently visit instead. (Another commonly requested feature).

Our server since 20.4 (Not have this problem with 20.3) We played 2 days in game, and a horde night. After horde night we had this error occur. We stopped/started the server. All progress got reset to prior horde night as far as player experience, levels, inventory, equipped gear. World day, in game storages/items/vehicles all saved state. All player data appears not to be saving properly. We reinstalled the server again, clean install with 20.4. Game appears to work normally so far for some players. For others this error still pops up and will cause players not to be able to interact with things, and cause zombies to not see/sense you anymore. Relogging causes you to revent back in time a few minutes and lose progress again. 1 player, gets this error on login screen and cannot even get into the game. They get stuck on creating player. Other players see them logged in, location, etc...But cannot see them. Attempting to revert back to 20.3 has fixed things for all but the 1 player who still cannot log into the world. They can log in with a new profile, but their original profile is a no go. Can't keep having to restart the server and player data on stable versions like this.... 2022-04-27T20:20:45 210.176 INF Created player with id=171 2022-04-27T20:20:50 215.335 ERR NCSimple_Serializer (cl=EOS_0002328efcce4f44aefee9c26b75410d, ch=0): 2022-04-27T20:20:50 215.349 EXC Memory stream is not expandable. at System.IO.MemoryStream.set_Capacity (System.Int32 value) [0x0003d] in <695d1cc93cca45069c528c15c9fdd749>:0 at System.IO.MemoryStream.EnsureCapacity (System.Int32 value) [0x00061] in <695d1cc93cca45069c528c15c9fdd749>:0 at System.IO.MemoryStream.Write (System.Byte[] buffer, System.Int32 offset, System.Int32 count) [0x000b3] in <695d1cc93cca45069c528c15c9fdd749>:0 at StreamUtils.StreamCopy (System.IO.Stream _source, System.IO.Stream _destination, System.Byte[] _tempBuf, System.Boolean _bFlush) [0x00029] in :0 at PlayerDataFile.Write (PooledBinaryWriter _bw) [0x003b3] in :0 at NetPackagePlayerId.write (PooledBinaryWriter _writer) [0x00020] in :0 at NetConnectionSimple.taskSerialize (ThreadManager+ThreadInfo _threadInfo) [0x004f3] in :0 UnityEngine.StackTraceUtility:ExtractStringFromException(Object) Log:Exception(Exception) NetConnectionSimple:taskSerialize(ThreadInfo) ThreadManager:myThreadInvoke(Object) System.Threading.ThreadHelper:ThreadStart_Context(Object) System.Threading.ExecutionContext:RunInternal(ExecutionContext, ContextCallback, Object, Boolean) System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object, Boolean) System.Threading.ExecutionContext:Run(ExecutionContext, ContextCallback, Object) System.Threading.ThreadHelper:ThreadStart(Object) 2022-04-27T20:20:50 215.352 INF Exited thread NCS_Writer_0_0 2022-04-27T20:20:50 215.352 INF Exited thread NCS_Reader_0_0