Possible spawn_conditions bug

[John Adams]

(con't)

And finally, the remainder of the log looks something like this:

[10.29. - 18:38:18] Unable to convert EQ opcode 0x6a5f to an Application opcode.
[10.29. - 18:38:18] [CLIENT__NET_ERR] Jak: Unhandled incoming opcode: [OpCode OP_Unknown (0x6a5f) Size=8]
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Event 1: Executing. Setting condition 1 to 1.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Local Condition update requested for 1 with value 1, which is what we already have.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Event 1: Will trigger again in 720 EQ minutes at 01/04/3100 06:00.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Next event determined to be event 2
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Event 2: Executing. Setting condition 1 to 0.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Local Condition update requested for 1 with value 0
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Zone notified that spawn condition 1 has changed from 1 to 0. Notifying all spawn points.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Spawn2 378215: Notified that our spawn condition 1 has changed from 1 to 0. Our min value is 1.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Spawn2 378215: Our condition is now disabled. Preforming a repop.
[10.29. - 18:39:19] [SPAWNS__MAIN] Spawn2 378215: Spawn reset, repop immediately.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Event 2: Will trigger again in 720 EQ minutes at 01/04/3100 06:00.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Next event determined to be event 3
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Event 3: Executing. Setting condition 2 to 1.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Local Condition update requested for 2 with value 1
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Zone notified that spawn condition 2 has changed from 0 to 1. Notifying all spawn points.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Spawn2 378216: Notified that our spawn condition 2 has changed from 0 to 1. Our min value is 1.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Spawn2 378216: Our condition is now enabed. Preforming a repop.
[10.29. - 18:39:19] [SPAWNS__MAIN] Spawn2 378216: Spawn reset, repop immediately.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Event 3: Will trigger again in 720 EQ minutes at 01/04/3100 06:00.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Next event determined to be event 4
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Event 4: Executing. Setting condition 2 to 0.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Local Condition update requested for 2 with value 0
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Zone notified that spawn condition 2 has changed from 1 to 0. Notifying all spawn points.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Spawn2 378216: Notified that our spawn condition 2 has changed from 1 to 0. Our min value is 1.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Spawn2 378216: Our condition is now disabled. Preforming a repop.
[10.29. - 18:39:19] [SPAWNS__MAIN] Spawn2 378216: Spawn reset, repop immediately.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Event 4: Will trigger again in 720 EQ minutes at 01/04/3100 06:00.
[10.29. - 18:39:19] [SPAWNS__CONDITIONS] Next event determined to be event 1
[10.29. - 18:39:20] [SPAWNS__MAIN] Spawn2 378216: Timer has triggered
[10.29. - 18:39:20] [SPAWNS__CONDITIONS] Spawn2 378216: spawning prevented by spawn condition 2
[10.29. - 18:39:20] [SPAWNS__MAIN] Spawn2 378216: Spawn reset, repop in 1200000 ms
[10.29. - 18:39:20] [SPAWNS__MAIN] Spawn2 378215: Timer has triggered
[10.29. - 18:39:20] [SPAWNS__CONDITIONS] Spawn2 378215: spawning prevented by spawn condition 1
[10.29. - 18:39:20] [SPAWNS__MAIN] Spawn2 378215: Spawn reset, repop in 1200000 ms

Sorry for the length, I just wanted to provide as much detail as possible. This functionality is something many ask about, and I thought I understood. Maybe I am still missing something. Has anyone else seen a problem using this system?

Thanks in advance,
J

[Striat]

sorry for reviving an old thread, but just to clarify for anyone else, I believe the problem you're having is that a period of 720 is used. Thats 12 hours. So, basically, your first event would work. However, it would change the next hour for the "day spawn" event to occur in the database occur at the same time as the "night spawn" event. So ultimately, your events are occuring as they should, but since ALL 4 events would then occur at 18:00, they're ultimately cancelling each other out.

Based on that, I believe the simple fix is to just change period for each event to 24 hours or 1440.

[Sakrateri]

bumping an old one again...anyone got this working yet?

[John Adams]

I must have missed this in my time of absence. Thanks for the bump, Sakrateri. That theory makes perfect sense. And you're right, the 720 would bump the "next spawn time" into the next cycle. Seems clear to me now. I'll have to try it. I want my night/day shifts working, dammit!