Cool! So, how did you save the day and month into variables? :O
I did not. idk if this even is possible tbh, and anyway it wouldn't help much.
What I did was fire a repeat_event that fires each day, until it finds a new month.
e.g.:
Fires at gamestart - I currently don't know the date, but I can check which month it is.
Let's say it's March "the X-th". Then I fire a repeat_event every day, and have it check whether it's still March when it fires.
Day X+1 : Still March
Day X+2 : Still March
Day X+3 : It's April
Then I know that day X+3 must be the 1st of April, because every previous day was March.
From that on, I can fire delayed events to any point of the year.
In my code, I fire another event that is delayed so much that from any 1st of Month I might land with this method, it fires on the 1st of January of the next year. From there on, it repeats itself every year, and allows me to e.g. fire another event from it with whatever delay is needed to address a specific day.
For example, the delay from there on until Christmas Eve (December 24th) would be 347 days delay from the 1st of January.
The downside with this method is that you have period at gamestart until you know the first day, and then have to fire a global event (hint: use a province event, those don't die) every year to be able to scope to any specific date. Not terrible on performance, but not efficient either.
I can post you my code if you really want to see it, but I have more things inter-weaved in it so tbh I think it would just confuse you.
Better to figure this out on your own if you
really want to use this method.