Already active events

Hello! 

I'm following up on comments I made in the Discussion section in March with an issue that has not been resolved or addressed at all:

May 6

May 13

I did a quick console search for events that the plugin attempted to start, but the plugin prevented the event from ending and then restarting. This is just from the last week.

07/16/2025 07:30:04 | [SatDishEvent] This event is active now. To finish this event (satdishstop), then to start the next one
07/16/2025 05:51:03 | [Sputnik] This event is active now. Finish the current event! (/sputikstop)!
07/16/2025 03:21:02 | [SatDishEvent] This event is active now. To finish this event (satdishstop), then to start the next one
07/16/2025 02:31:02 | [Sputnik] This event is active now. Finish the current event! (/sputikstop)!
07/16/2025 00:10:00 | [SatDishEvent] This event is active now. To finish this event (satdishstop), then to start the next one
07/15/2025 16:20:04 | [Sputnik] This event is active now. Finish the current event! (/sputikstop)!
07/15/2025 14:44:03 | [Sputnik] This event is active now. Finish the current event! (/sputikstop)!
07/15/2025 09:48:08 | [Sputnik] This event is active now. Finish the current event! (/sputikstop)!
07/15/2025 06:59:05 | [Sputnik] This event is active now. Finish the current event! (/sputikstop)!
07/15/2025 02:30:02 | [Sputnik] This event is active now. Finish the current event! (/sputikstop)!
07/15/2025 00:20:01 | [SatDishEvent] This event is active now. To finish this event (satdishstop), then to start the next one
07/14/2025 15:25:04 | [JunkyardEvent] This event is active now. To finish this event (jstop), then to start the next one
07/14/2025 02:27:05 | [Sputnik] This event is active now. Finish the current event! (/sputikstop)!
07/13/2025 14:10:05 | [JunkyardEvent] This event is active now. To finish this event (jstop), then to start the next one
07/12/2025 05:31:01 | [ArcticBaseEvent] This event is active now. To finish this event (abstop), then to start the next one
07/12/2025 02:12:04 | [Sputnik] This event is active now. Finish the current event! (/sputikstop)!
07/11/2025 22:38:02 | [ArcticBaseEvent] This event is active now. To finish this event (abstop), then to start the next one
07/11/2025 11:05:01 | [ArcticBaseEvent] This event is active now. To finish this event (abstop), then to start the next one
07/10/2025 22:38:08 | [Sputnik] This event is active now. Finish the current event! (/sputikstop)!
07/10/2025 13:38:02 | [Sputnik] This event is active now. Finish the current event! (/sputikstop)!
07/08/2025 22:15:04 | [ArcticBaseEvent] This event is active now. To finish this event (abstop), then to start the next one
07/08/2025 14:38:08 | [SatDishEvent] This event is active now. To finish this event (satdishstop), then to start the next one
07/08/2025 10:07:03 | [SatDishEvent] This event is active now. To finish this event (satdishstop), then to start the next one
07/08/2025 08:09:01 | [Sputnik] This event is active now. Finish the current event! (/sputikstop)!

Can you please take a look? Thanks!

hello, I’m sorry I didn’t reply for a long time. Lost your message 
 

Check your event schedules in /em - increase the interval between events and add random offsetMin/offsetMax delays to prevent timing conflicts. Short intervals can cause events to interfere with each other.

I bought this plugin to avoid having to do this manual work of trying to time events though?

The "already active events" messages occur because EventsManager tries to start events that are still running from previous sessions. Each event plugin protects itself from duplicate starts.

Quick Fix:

- Open /em and increase the intervals between your events

- Add random offset delays (5-15 minutes) in your time settings

- Ensure your intervals are longer than your events typically run

This prevents timing conflicts while keeping automatic scheduling working properly.

Best regards

I understand what you are saying, but like I said, I specifically purchased this plugin to avoid having to time events like you are suggesting. Also some plugins do not protect against duplicate starts, as I stated in the Discussion section. I've asked the dev of some of the events I use to add the feature, but there might be other devs/events as well that I don't have. 

The plugin description says 

Quote

The plugin handles the scheduling and starting of events, so having autostart enabled could cause conflicts or unexpected behavior.

If it handles the scheduling and starting of events, why do I have to manually set the scheduling and starting of the events? You're basically asking me to act as if I don't even have this plugin and adjust the intervals and delays individually, which I can do in each event's config file.

It sounds like you are saying this not going to be considered as a bug or something that needs to be fixed, is that correct?