I don't know if anyone else opened a thread about it, so dear mods, be free to just copy this into the existing thread, close or delete it... 
In EU2 there was a division between historical events and random ones, where the player was informed about the further via messages while the later were just known by the country who would get it. With the improved event engine of EU3 this division is obsolet and the player has only two choices regarding events happening to other countries: No messages at all or CK like message spam.
I'd recommend a little change to this, which would probably need some lines of code*. Why not adding a new attribute to events, which tells the messaging system, if the event is worth bothering the player? So the division between average and special events would be determined by the author of the event, not the engine itself. The message settings would then just tell the game how to handle those special events...
* I read the thread in the CK public beta forum about the "few lines of code", so I can't estimate how much "precious Johan time" would be needed to implement this idea.
In EU2 there was a division between historical events and random ones, where the player was informed about the further via messages while the later were just known by the country who would get it. With the improved event engine of EU3 this division is obsolet and the player has only two choices regarding events happening to other countries: No messages at all or CK like message spam.
I'd recommend a little change to this, which would probably need some lines of code*. Why not adding a new attribute to events, which tells the messaging system, if the event is worth bothering the player? So the division between average and special events would be determined by the author of the event, not the engine itself. The message settings would then just tell the game how to handle those special events...
* I read the thread in the CK public beta forum about the "few lines of code", so I can't estimate how much "precious Johan time" would be needed to implement this idea.