Using the settime command doesn't spawn hordes?

[Son Of Mowgef]

I haven't played A17 that much since release so I was trying some "new" base defence ideas I had, but after using the settime to skip to day 14 no horde appeared.
Anyone know what I did wrong here?
NOTE: Didn't want to post this in the bugs section since I'm sure it's me doing it wrong in some way, this is literally the first I've used commands like this.

[SylenThunder]

Using the settime command is a good way to bork your save and screw up horde spawns.

[Green777]

if you want a horde in game open the console and type in spawnwanderinghorde or spawnscouts

[Lost Carrot]

We ran into this problem. Once you let a horde night pass, you can no longer have it run again by rewinding time. The server records when when was the last HN and then calculates the next one based on your settings.

We had it set to 10 days.
- Ran first HN and then rewind time to have the horde again on day 10. No horde
- Changed HN from 10 days to 7 days. Now the server sees that we had HN on day 10 and sees that the config is set for 7 days so sets the next HN to day 17.
- Leaving the setting on 7 days now the server will just keep adding 7 days to the last HN number so 17 + 7 is day 24 an so forth.

How do I know this? When starting up your dedicated server after a shutdown, open the console or web console in my case for my host. It will show you when was the last horde night and when is the next.

In order to get my HN back to the normal 7 days on every seventh day counting from 1 without wiping my server:
- It was now day 10 and I need horde to show up on day 14.
- I set HN to 4 days. Server now sees this and calculates that my next HN should be day 14.
- Ran HN on day 14 and got a horde. We shut down around 11pm on that day for just so that the server would record that we had HN on day 14.
- Stopped server and restarted looking at the console to make sure that the server recorded that we had a horde on day 14.
- Shut down and set server to HN every 7 days and started it up looking at console
- Server now sees that we had a HN on day 14 and our settings are at 7 days so calculates and tells me in the console output that the next night is day 21.

There is a small bug after rewinding time and trying to mess with the settings. As seen above, HN was going to show up on day 20 but we rewind time to have it again on day 10. Once day 10 came after our rewind, we got the red sky and music for HN (horde night) but no horde. So part of the server thinks that day 10 should be horde night and plays the music and turns the sky red but another part of the server thinks that HN should be on day 20 so no zombies were spawned. Zombies would have only spawned on day 20 if we let it run as is.

I do not know if it was intentional to have the server not allow you to do over a horde night by rewinding time or if it is a bug.

Feel free to check us out at the post below. We are looking to expand :)

https://steamcommunity.com/app/251570/discussions/2/1836811737987618264/

[Son Of Mowgef]

Originally posted by Neel Authorious:

you can no longer have it run again by rewinding time.

Yup that was my problem right there, no big deal here, I just set the time to the next horde night.
Thanks for the info.

[gamenmetal]

Apparently settime even messes things up if it is going forwards in time. Not just rewinds.

[SylenThunder]

Originally posted by gamenmetal:

Apparently settime even messes things up if it is going forwards in time. Not just rewinds.

Yeah, any time you use it is going to break things.

[lilSebastian]

Originally posted by Neel Authorious:

We ran into this problem. Once you let a horde night pass, you can no longer have it run again by rewinding time. The server records when when was the last HN and then calculates the next one based on your settings.

Do you know where on the server the hoard days are logged? I'm looking all up in there, but can't find it. I wonder if there's a way to edit the log. I too have been having issues re-doing hoard days.

[SylenThunder]

You can't re-do hoard days. Once the horde happens, it sets the date for the next one. Going back won't get you anywhere except a broken game.

The next scheduled BM is posted in the log at the end of a horde, and at the start of the server.

And again I will state this.

Using settime command WILL BREAK your world.

[Lelo Mariin]

A hoard is stacks of objects
Horde is what comes every 7 night

:( :( :( :( :( :(

[LittleBlueDuneBuggy]

Originally posted by Lelo Mariin:

A hoard is stacks of objects
Horde is what comes every 7 night

:( :( :( :( :( :(

You're responding to a thread from last decade. Just let it rest, man!!

[Midget Porn]

So I need help in Alpha 18.3 (b4) so basically, I did the settime command not knowing how to fix it and whenever I load onto the game and press f1 I the command menu and I see "BloodMoon SetDay: day 56, last day 49, freq 7, range 0" then under it says" BloodMoon SetDay: day 41667, last day 49, freq, range 0" So Now I do not know how to fix that.. Please, someone, help me!!

[SylenThunder]

Originally posted by Pulse:

So I need help in Alpha 18.3 (b4) so basically, I did the settime command not knowing how to fix it and whenever I load onto the game and press f1 I the command menu and I see "BloodMoon SetDay: day 56, last day 49, freq 7, range 0" then under it says" BloodMoon SetDay: day 41667, last day 49, freq, range 0" So Now I do not know how to fix that.. Please, someone, help me!!

I covered that in this thread already.

Originally posted by SylenThunder:

Using the settime command is a good way to bork your save and screw up horde spawns.

Originally posted by SylenThunder:

Originally posted by gamenmetal:

Apparently settime even messes things up if it is going forwards in time. Not just rewinds.

Yeah, any time you use it is going to break things.

Originally posted by SylenThunder:

You can't re-do hoard days. Once the horde happens, it sets the date for the next one. Going back won't get you anywhere except a broken game.

The next scheduled BM is posted in the log at the end of a horde, and at the start of the server.

And again I will state this.

Using settime command WILL BREAK your world.

You broke it. To fix it you will need to start over, and not play around with this command any more.

[Midget Porn]

Originally posted by SylenThunder:

Originally posted by Pulse:

So I need help in Alpha 18.3 (b4) so basically, I did the settime command not knowing how to fix it and whenever I load onto the game and press f1 I the command menu and I see "BloodMoon SetDay: day 56, last day 49, freq 7, range 0" then under it says" BloodMoon SetDay: day 41667, last day 49, freq, range 0" So Now I do not know how to fix that.. Please, someone, help me!!

I covered that in this thread already.

Originally posted by SylenThunder:

Using the settime command is a good way to bork your save and screw up horde spawns.

Originally posted by SylenThunder:

Yeah, any time you use it is going to break things.

Originally posted by SylenThunder:

You can't re-do hoard days. Once the horde happens, it sets the date for the next one. Going back won't get you anywhere except a broken game.

The next scheduled BM is posted in the log at the end of a horde, and at the start of the server.

And again I will state this.

Using settime command WILL BREAK your world.

You broke it. To fix it you will need to start over, and not play around with this command any more.

So On mine thing, I would basically have to restart or go to day 41667?!?! I need an answer to understand what has happened

[Shurenai]

Originally posted by Pulse:

So On mine thing, I would basically have to restart or go to day 41667?!?! I need an answer to understand what has happened

Essentially, Yes. And using settime to get to day 41667 is liable to break the save even further- And even if it didn't break it further, it's possible even when reaching that day that it may not start the horde as normal.

The settime command is a developer level command and isn't really intended for use by players (But isnt exactly blocked off from them either) -- Likewise with the time slider in the debug menu.

In both cases, improper use can ruin a save in minor or catastrophic ways, breaking anything from the horde counter and crops to never seeing an air drop again, zombies stop spawning entirely, make it so looted containers never respawn, etc...

Generally speaking, If you're going to use the command, just dont ever change time outside of the current day, and don't ever add time or reverse time beyond the following breakpoints: 4:30am, 12:05, and 10:00. Basically, Morning when the morning music plays, Just after noon when the ambience shifts into afternoon, and when night falls playing the nightfall jingle- Accelerating or rewinding past these times will often break one or more things in your game, as these are the times that many checks are performed at.

Even keeping your use constrained like that though, it's generally still a bad idea to play with the command in a world you care about, as even proper use can sometimes break things.

[Midget Porn]

Originally posted by Shurenai:

Originally posted by Pulse:

So On mine thing, I would basically have to restart or go to day 41667?!?! I need an answer to understand what has happened

Essentially, Yes. And using settime to get to day 41667 is liable to break the save even further- And even if it didn't break it further, it's possible even when reaching that day that it may not start the horde as normal.

The settime command is a developer level command and isn't really intended for use by players (But isnt exactly blocked off from them either) -- Likewise with the time slider in the debug menu.

In both cases, improper use can ruin a save in minor or catastrophic ways, breaking anything from the horde counter and crops to never seeing an air drop again, zombies stop spawning entirely, make it so looted containers never respawn, etc...

Generally speaking, If you're going to use the command, just dont ever change time outside of the current day, and don't ever add time or reverse time beyond the following breakpoints: 4:30am, 12:05, and 10:00. Basically, Morning when the morning music plays, Just after noon when the ambience shifts into afternoon, and when night falls playing the nightfall jingle- Accelerating or rewinding past these times will often break one or more things in your game, as these are the times that many checks are performed at.

Even keeping your use constrained like that though, it's generally still a bad idea to play with the command in a world you care about, as even proper use can sometimes break things.

So am I gonna have to restart my game