[Issue] Plugin start issues (cold start) and shortest path integration possible bug

[paulpawe]

Had two events come up today. Attempted to turn plugin on, since the answer wasn't showing, but was gray and stayed off. Removed plugin, reinstalled, can't see it in plugin menu. Repeated several times, still not seen. Restarted app finally seen but still grayed and turned off.

Looked at "Shortest Path" plugin - was disabled. Remembered a quick notification during the initial install.
Turned on "SP" plugin - Random event helper plugin is now able to be turned on. Waiting for next event to verify function.

Why does the "SP" plugin need to be enabled to enable a disabled "REH" plugin?

[Infinitay]

Sorry you had some troubles with the plugin. Bear with me as I try to following a long because I'm a bit confused.

Had two events come up today. Attempted to turn plugin on,

Was the plugin disabled or uninstalled before you entered those events? There are some known issues where there isn't proper support for fresh installing the plugin while inside the event or turning the plugin or module on within the event. I've been slowly attempting to add support for it where it pops up such as last week or two with Freaky Forester. Do you remember what two events you had that gave you this issue?

Removed plugin, reinstalled, can't see it in plugin menu.

That's an odd issue. Since later you said that the problem fixed when you restarted RuneLite, I can only assume it was a client issue and not plugin related? If you still have your log file from that day and share it with me, I can attempt to review it and see if I can spot what had happened.

Why does the "SP" plugin need to be enabled to enable a disabled "REH" plugin?

It shouldn't. The Shortest Path plugin should only be required to enable the Maze Helper module and not any other module, or the plugin itself. Also, to clarify, when I say module, I really mean the different available random event options. Although, I will look into this again. Maybe the changes I made before releasing the plugin (I was asked to rework the shortest plugin notification) messed something up which I didn't catch - I'll look into this again and see if I can recreate what you experienced

Have you had any other issues since using the plugin?