SkBee loading before Skript [solution]

[WizardWoodland]

if you have a plugin installed that changes the loading order installed,
(for example, multiverse core)
then skbee may load before skript and therefore be disabled.

BUG solution:

In the .jar archive of the skbee plugin in the file plugin.yml

Replace

softdepend:
  - Skript
  - FastAsyncWorldEdit
  - skript-variable-dump
loadbefore:
  - SkQuery

with

depend:
  - Skript
softdepend:
  - FastAsyncWorldEdit
  - skript-variable-dump
loadbefore:
  - SkQuery

And it works.

[WizardWoodland]

I just wanted to share the solution, because I did not find it on the internet.

[Erisfiregamer1]

Why is Skript not a dependency of SkBee anyway?? That's dumb.

[ShaneBeee]

It is, as seen here:

SkBee/src/main/resources/plugin.yml

Lines 8 to 9 in b3f973c

	softdepend:
	- Skript

On most servers, Skript and SkBee are loaded correctly. It appears some server software (such as Pauper) and maybe some plugins somehow change the load order of plugins when the dependency is a soft depend.
As stated in #230 ... this isn't an issue with SkBee, since SkBee is setup correctly, but the server is somehow manipulating the load order of plugins when a soft depend is used.

Changing this to a hard depend forces it better I guess. This again is an issue with the server not the plugins.

[Erisfiregamer1]

Why isn't it a HARD dependency is what I meant. Then plugins know to load it after AND also the server gives you a huge warning that the dependency is missing.

[ShaneBeee]

Then plugins know to load it after

It's not the plugin that knows to load, it's the server.
Whether it's a hard/soft depend, the server puts everything in the correct order to load.
The issue here isn't SkBee, it's Purpur, which is not doing plugin load order correctly.

I, as well as many other people have been running SkBee on Paper (and some on Spigot) and don't have this issue.
I've only seen this issue about 5 (or so) times, and most of those were running on Purpur.

the server gives you a huge warning that the dependency is missing.

This is the main reason I use a soft depend. When that big error spews out, the average Skripter doesn't know how to read a stack trace, and their first thought is to report it as a bug.
By using a soft depend, I am able to not have that nasty message, as I can manually check for Skript within the plugin, and if Skript is missing, I can print a much nicer/clearer message in console, that Skripters can actually understand.