[FIXED] Queued scene events triggered at the same time

I think Jealous-Editor is not covering this particular case:

This is very specific, but it could be worth a try. Imagine you have the following:
1. A series of countdowns (1 or 2 min each), each one showing up a scene event when reaches zero (they are all interconnected with consecutive flags, so when the first clock ends, a first scene is shown + second countdown starts and so on)
2. Random scene events when your hero steps on a event.

Issue: There is a probability (not very low, since I have “nano clocks” so to speak) that a scene event from 1. and a scene event from 2. pup up at same time. The result is 2. seems to have priority and 1. is ignored.

Scene events are non interruptable even by other scene events. As such, you must pause the game in scene events type 2, so that the counter stops - making it impossible for scene events type 1 to trigger while in type 2.

You might also want to pause in type 1 so that other type 1 do not get triggered.

Sorry, I could have answered you yesterday since I’ve tried pausing every single scene event (1. and 2.) and the issue is no more (as now I see you have suggested wisely too). This thread only applies in case, for some reason (in my particular case, this option was dismissed), we need 1. and/or 2. scene-events in a non-pause mode.

When you play the Scenario, you will see I was trying not to use pause in 1. because I wanted to move an enemy unit (but pausing do it as well, not so cool as unpaused, but anyway, it works).

Seems extremely pedantic now… So perhaps you might want to send this into your newly created “Museum of WBC Bugs”.

I would call that bad mapping if you ask me, but I suppose I could create a queue of events waiting to be triggered as soon as the current one finishes.

Patrick_the_Winekiller wrote:

I would call that bad mapping if you ask me, but I suppose I could create a queue of events waiting to be triggered as soon as the current one finishes.

The scenario in question has 23 scene events ( ). Perhaps wait for it (next week I think) and you can see if this deserves more thinking.

EDIT: I have just finished all campaigns I want to do (just need some time with ACT and other files to test it in campaign mode). This map discussed here is also finished and tested. Do you want to take a look at it, so you can close this topic?

Nah, I'd rather not take more spoilers (the ship testing map was enough, I must know what it is all about now!). Albeit this is not really a bug, queuing scene events is not a bad suggestion.

I am not sure if this fits this category or not and did not found this on bugs already fixed: When you have two countdowns (at least two) working at the same time from the beginning, the smaller is ignored when reaches zero. I have to use a flag event to turn this around in other possible way, but it is no equal replacement. I think this is pertinent since you might want multiple countdowns working at the same time on their own ways (say one for a "give some armies" event to your team, another to an enemy, another to change AI, etc.).

I am assuming this has nothing to do with this already fixed bug?

Kharn on Wikia wrote:

9. A timed event that requires additional conditions that is triggered, but then has the conditions undone will still continue on. I.E. […]

Is this a bug? Is this still happening in 0.8.9?

As stated, this was already fixed (Sirian knows when). Topic closed.