Skip to content

paper-plugin.yml is not processed #59 #20

@NODeeJay

Description

@NODeeJay

Describe the bug
I assume it is a bug and not a FR since you officially support paper. If my assumption is incorrect, please change the ticket to a FR: Process corresponding plugin detail file ( *plugin.yml ) for different servers (spigot, paper, purpur, etc.)

Plugins that are only for paper servers and not spigot anymore, contain sometimes no plugin.yml, since paper-plugin.yml is the only one needed. MCSS however, seems to expect plugin.yml and does not process the paper-plugin.yml instead, which renders plugins for paper only in the plugin manager to a single v.

Image

To Reproduce
Steps to reproduce the behavior:

  1. Prepare paperMC server
  2. install paper-only plugin, e.g. any from vane
  3. navigate to plugin manager
  4. just v is shown instead of the plugin name, and only name, location and filesize is presented when clicking on detail

Expected behavior
Plugin name and all details are shown.

Investigation
I created a plugin.yml with information provided in the paper-plugin.yml and went to plugin manager, all information was presented as expected, which confirms the plugin.yml is read (over the paper-plugin.yml)

Screenshots
see above

Desktop (please complete the following information):

  • OS, browser, device, server installation independently reproduced

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions