DSTUser Posted March 28 Share Posted March 28 Basically just the one they used in the Stream Link to comment Share on other sites More sharing options...
Arcwell Posted March 28 Share Posted March 28 TheWorld.components.forestdaywalkerspawner:TryToSetDayWalkerJunkPile() Disclaimer: might have unintended consequences in long-term worlds. Use at your own risk. 1 1 1 1 Link to comment Share on other sites More sharing options...
DSTUser Posted March 28 Author Share Posted March 28 Now im curious, what kind of unintended Consequences are we talking about here. Like a second daywalker spawning or the world file just corrupting? Link to comment Share on other sites More sharing options...
Arcwell Posted March 28 Share Posted March 28 49 minutes ago, DSTUser said: Now im curious, what kind of unintended Consequences are we talking about here. Like a second daywalker spawning or the world file just corrupting? From testing it appears to just temporarily mess with the caves-to-surface-to-caves cycle. When you defeat either daywalker, the shard for the next daywalker spawn changes regardless of which shard it was defeated in. So for example if you use this command to defeat daywalker on the surface before beating him in the caves, it will then spawn again on the surface 10 days later, and after THAT it will try to spawn one in the caves, which it can't, because there already is one. 1 Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now