-
Notifications
You must be signed in to change notification settings - Fork 260
Closed
Labels
Status: Fix availableA fix for the issue is available.A fix for the issue is available.Type: Issue (PlaceholderAPI)Issue caused by PlaceholderAPI not working properly.Issue caused by PlaceholderAPI not working properly.
Description
Confirmation
- My issue isn't already found on the Issue tracker.
- My issue is about PlaceholderAPI and not any expansion or external plugin
- The issue isn't already fixed in a Spigot Release or Development Build.
- The Common Issues page doesn't mention this issue.
Type
API Bug
What happens?
Right now is PlaceholderAPI's expansion loading broken in a sense that it may load the same expansion twice, if there are 2 jar files of it.
This is partially to blame on how the expansion is downloaded. PlaceholderAPI will download the expansion into a jar named expansion-<name>.jar, replacing it, if already present. If there is the same expansion now, but with a different jar name will it not be replaced.
Expected Behaviour
There should be a way to prevent the same expansion from loading twice, which could be achieved by checking if an expansion with that name already exists.
The jar replacement would be a more difficult story here.
How to Reproduce
- Manually download an expansion, or rename the jar already present
- Download the same expansion through the
/papi ecloudcommand. - Reload PlaceholderAPI.
/papi dump Output
No real need for it.
Console Log
No response
Errors
No response
Additional Info
No response
Metadata
Metadata
Assignees
Labels
Status: Fix availableA fix for the issue is available.A fix for the issue is available.Type: Issue (PlaceholderAPI)Issue caused by PlaceholderAPI not working properly.Issue caused by PlaceholderAPI not working properly.