if that's how the events are implemented, then I'm encountering multiple bugs. Multiple events seemed to overlap each other, i.e. cops knocking, pregnant, tax evasion all run at once. The non special events, like pregnant and tax evasion, run back-to-back, i.e. after pregnant, then tax event. The special and non special though run simultaneously, i.e. the dialog on the bottom is for cops, and there's the dialog box for tax.
This kind of event overlap occurs fairly frequently for me. At least it doesn't crash the game.
Dunno why moving to real date system is problem, but I do know using real date systems is much more complex, esp if doing scheduling. The only way I know to do things safely is to have 2 representation of time, one is linear integer, like low level OS time interface (how many seconds has elapsed since 1970), and the other is the usual time format (day/month/year hour/min/sec). Scheduling is done with the linear integer, cos it is easier to pinpoint a specific time, rather than using the time format. This however requires more API to convert time between the 2 representation, and doing time math.
If there is some kind of communication device implemented (smartphone / pager), whenever problem arise and the player is not at home / studio, a notification can be sent. There might be a choice whether the player deals with the problem themselves, or let the PA in charge of production deals with it.
The problems can be time limited, i.e. only occurs when shooting a scene.
BTW, does STD only applied to the player, but not the stars?
Looking forward in seeing this feature.