There's some information missing from your OP
2) Event A data is entered into the code (Start at 1709615040, interval 3600 and event time 240)
3) Event B (Start at 1709629200, interval 21600 (6 hours) and event time 7200 (2 hours))
|
A guess at what you want:
Event B Starts at 1709629200, lasts for 6 hours. During that 6 hours, the time between the events is 2 hours (instead of 1).
and what's missing:
Does event B occur once a day? If not what is the interval between repeats? 6 hours Event B followed by 6 hours Event A then repeat? Or something different (6 Hours B, 3 hours A, 6 Hours B...).
Is the actual event time (the one this process is tracking) still the same duration during Event A and B (240 or whatever) and just the interval between is varied (1/2 hours)?
The 3.93333333 hours between your start times would cause some strange timings to the actual event going into/out of these A/B sessions (like suddenly adding 2 hours to the start time just minutes before the countdown display said it was supposed to start etc.).
Maybe figuring out
ALL the actual mechanics (6 hours session B, 4.9333333 hours session A maybe?) before starting would help decide if the addon itself is "sensible" (no offence intended).