Fix documentation for addClientSideModDependency
and add new modIsInstalled
function with more sensible naming and semantics
#51
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
addClientSideModDependency
function used to do what it says; it would check if the mod was installed and abort the plugin loading if it wasn't. At some point, the semantics changed to supposedly "returning whether the mod is available", but even that has been broken for a long time, as it actually returns whether the mod is UNavailable. This has had a knock-on effect to theoverrideFrameworkChecks
flag, which is meant to make it so that checks always succeed; however, because a check succeeding means returning false in this broken function, the flag being set actually makes all plugins with mod dependencies abort initialisation.This PR deprecates the old function and updates its documentation to describe the actual behaviour of the function. It also introduces a new function with a more sensible name that describes its more sensible semantics.