CK II - [2.8.1.1 beta] Death of spy target silently prevents successful spying on next target

[jruderman]

One line summary of your issue
[2.8.1.1 beta] Death of spy target silently prevents successful spying on next target

Game Version
2.8.1.1 beta

What expansions do you have installed?
Jade Dragon,
The Reapers Due,
Conclave,
Horse Lords,
Way of Life,
Charlemagne,
Rajas of India,
Sons of Abraham,
The Old Gods,
The Republic,
Legacy of Rome,
Sword of Islam

Do you have mods enabled?
Yes

Please explain your issue is in as much detail as possible.
If I imprison+execute my heir and start spying on my next son the following day, I never get any spy events against my new target.

This is similar to an old bug report https://forum.paradoxplaza.com/foru...ue-focus-cannot-spy-on-if-target-dies.900712/ but some of the things in that report are fixed.

As Yxklyx hinted at in the other thread, this happens because the delayed tombola event (WoL.2060) is still in flight for my first target. It sees that he's dead, shows a message that he's dead (WoL.2061), and calls the event to "clear out flags, etc" (WoL.2069). This event does "clear_delayed_event = { id = WoL.2060 }" which breaks spying on my second target.

Can be worked around by either:
* Stop spying before executing, or
* (Re)start spying on the second character after the message appears

Could be fixed by either:
* Making WoL.2069 not clear the delayed event and instead clearing the delayed event directly from `stop_spy_on_decision` and `stop_spy_on_decision_target`
* Making `decision_spy_on should` clear the delayed event before setting up a new one

Steps to reproduce the issue.
1. Intrigue focus
2. Spy on character A
3. Wait a few days
4. Kill character A using a different method
5. Spy on character B

A message appears about A's death negating the spying against A, but no spying events trigger for B.

Upload Attachment

 

[jruderman]

Save file

 

[Dracko81]

Could be fixed by either:
* Making WoL.2069 not clear the delayed event and instead clearing the delayed event directly from `stop_spy_on_decision` and `stop_spy_on_decision_target`
* Making `decision_spy_on should` clear the delayed event before setting up a new one

Would not a better solution be to add a cool down to stop you from spying on the next target. It would have the added bonus of slightly weakening the focus too, which wouldn't affect too much considering how strong it is already.