Andre_601

Something else that imo could deserve a rework is the `api-version` option. Feels for me a bit annoying that you can only define a single API version rather than multiple...

> The notion of defining an API version is pointless > > a) The entire system as it stands is practically just a boolean check for if it's defined or...

Something else that just came to mind: What about a change to the authors option to allow adding a personal link, description, etc? Like f.e. ```yaml authors: - name: MainAuthor...

> currently you can manually extend Command/PluginIdentifiableCommand in a class and register your commands to the commandmap yourself. How would this look like in terms of code? 🤔

> Well, then either remove it, or perhaps make it _kinda_ the oposite way of how it works? Like allow a plugin dev to tell the server "Hey, this plugin...

Paper should log libraries loaded by a Plugin through its PluginLoader, because as of right now is that not the case, which has the potential risk that someone could load...

I just personally want it to be logged in one way or another. Because without that, server owners wouldn't know what libraries are loaded by a plugin, which would be...

Something I find a little tedious right now is that you have to define load-before/load-after separately to the dependency declarations, which can be annoying. If dependencies are just `- name:...

Can't recall where I mentioned that before (I think in the paper plugin PR and on Discord?) but a replacement of the `/reload` command and its broken logic with an...

I mentioned a possible solution for reload, which is having an event plugins can listen to, to then decide what to do with that. That way, it's open to the...