Better Informations for Plugins if they failed

[TheMeinerLP]

Is your feature request related to a problem?

In many cases, users of plugins encounter errors when starting them. Unfortunately, it is not clear to users what actions they need to take to solve the problem. In some cases, the problem is also that users generally do not understand the error.

Describe the solution you'd like.

Using Doc's function, you could throw a specific exception and extra fields at the OnEnable, which then contains more detailed information on why the plugin is disabled or what you have to do to get the plugin functional again.

Describe alternatives you've considered.

Alternatives would be that every developer does it differently and users have to obtain information with many circumstances.

Other

This would give developers a way to give users UX-friendly help and make it uniform

[electronicboy]

1. We generally don't want to shove 20 dozen pieces of hover text inside of the plugins message, the output is limited and hover stuff can burn through that pretty fast
2. I'm not really sure what this solves, which isn't already solvable if people handled this in the logs. It's the port of call for understanding why something went sideways

[NonSwag]

In pretty much all the cases where a plugin blows up, you can easily find a solution by just asking google or contacting the dev
also, most less knowledged users don't even read stacktraces nor well written error messages let alone hover messages

[Machine-Maker]

Yeah, I think logs should be sufficient for this. They should be the place errors are described, and server owners should understand how to read them, and if they don't, pastebinning the log to a discord server will usually get an answer.