Bearger not spawning on day 30 when doing a summer start - bug or recent change?

[DinsdaleP]

I'm playing Wortox in the beta branch, setting the starting season to summer as usual. While this makes the early game harder, in previous games (half a year ago at least), the first giant spawn (besides Antlion) still happened on day 30, but it was Bearger instead of Deerclops. I also remember finding some snippets in the code beforehand, pointing to this as being intended behavior, though I can't for the life of me find it right now.

However, in my current game, I did not get a Bearger spawn on the night of day 30. Was something related to giant spawning mechanics been changed, or have I just ran into a bug?

 

edit: solved, it's just an old bug that poked it's ugly head out once again

[Debruh]

Isn't his spawning a random amount of days or smth? Though, this probably doesn't belong here.

[DinsdaleP]

Nope, beforehand the first giant always spawned on the night of day 30, be it Deerclops or Bearger, and the code indicated that is it intended behaviour. The reason I've posted it in the beta forums is easy, it might have been something (unintentionally?) broken by the current beta version.

[Arcwell]

57 minutes ago, DinsdaleP said:

in my current game, I did not get a Bearger spawn on the night of day 30. Was something related to giant spawning mechanics been changed, or have I just ran into a bug?

beargerspawner.lua was last modified in June of 2024 so it's not a change at least.

Did it spawn at a different time or not at all?

• If it was a different time, when?
• If not at all, are you positive it has not spawned? Have you ran a console command c_announce(c_countprefabs("bearger")) to check if bearger exists in the world?

[DinsdaleP]

4 minutes ago, Arcwell said:

Did it spawn at a different time or not at all?

Not at all, I've used insight to check even before day 30, there was no indication of his spawn timer popping up. Deerclops did pop up after that, early in winter.

Checked the exact dates, the last time I've played with him spawning on day 30 was at 2024 february, so more than a half years. beargerspawner.lua was a good idea, also checked that since I have a backups few backups of scripts.zip, it looks like only a typo was fixed in that file.

[Arcwell]

3 minutes ago, DinsdaleP said:

Not at all, I've used insight to check even before day 30, there was no indication of his spawn timer popping up. Deerclops did pop up after that, early in winter.

Checked the exact dates, the last time I've played with him spawning on day 30 was at 2024 february, so more than a half years. beargerspawner.lua was a good idea, also checked that since I have a backups few backups of scripts.zip, it looks like only a typo was fixed in that file.

Sounds like a bug then. Admittedly I am not sure what causes it (usually caves, ocean, or disconnecting that tends to mess with things) but I can tell you from reading the file and confirming with debug strings that Bearger spawns anywhere from 1.3125 - 2.1875 days after the start of day 29.

[DinsdaleP]

Cheers, thank you very much for checking!

Looked through beargerspawner.lua and tuning.lua , it seems like nothing has been changed, so I've just probably ran into a bug. Do you know by any chance when the spawn starts, does the spawn timer starts ticking down after day 26 (NO_BOSS_TIME)? I'm pretty sure I was in the caves around that, killing AFW, so that could easily have been the reason for the bug popping up.

[Arcwell]

7 minutes ago, DinsdaleP said:

Cheers, thank you very much for checking!

Looked through beargerspawner.lua and tuning.lua , it seems like nothing has been changed, so I've just probably ran into a bug. Do you know by any chance when the spawn starts, does the spawn timer starts ticking down after day 26 (NO_BOSS_TIME)? I'm pretty sure I was in the caves around that, killing AFW, so that could easily have been the reason for the bug popping up.

From testing it starts at the beginning of day 29.

By my own interpretation of the code it would start at day 28 (line 160, cycles > NO_BOSS_TIME when cycles = 27, which is day 28), but evidently I'm missing something there because checking beargerspawner with debug strings in game on day 28 indicates the timer has not started.

[DinsdaleP]

4 hours ago, Arcwell said:

From testing it starts at the beginning of day 29.

By my own interpretation of the code it would start at day 28 (line 160, cycles > NO_BOSS_TIME when cycles = 27, which is day 28), but evidently I'm missing something there because checking beargerspawner with debug strings in game on day 28 indicates the timer has not started.

Thanks! Hoping I can add something useful then, checked out previous saves (because in a beta, sane people make manual backups), and apparently, if I poke my head out to the surface on day 28, the timer starts instantly according to Insight. So the issue is solved it seems, it was just an old bug, caused by me being in the caves from day 26-29, fighting nightmare werepig and doing one last raid on the ruins before AFW regenerates it... so now, I only have to go back to an earlier save and redo the AFW fight, something which does not fill my heart with joy to say the least

[Arcwell]

3 minutes ago, DinsdaleP said:

Thanks! Hoping I can add something useful then, checked out previous saves (because in a beta, sane people make manual backups), and apparently, if I poke my head out to the surface on day 28, the timer starts instantly according to Insight. So the issue is solved it seems, it was just an old bug, caused by me being in the caves from day 26-29, fighting nightmare werepig and doing one last raid on the ruins before AFW regenerates it... so now, I only have to go back to an earlier save and redo the AFW fight, something which does not fill my heart with joy to say the least

Glad to hear it's resolved! And good to know day 28 is possible, so I'm not *entirely* wrong in thinking that. Best of luck with FW! c: