fix(API): sbpp_checker library name #1034
Open
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.
Description
Fix library name conflict between
sbpp_checker
andsbpp_main
(both were usingsourcebans++
)sbpp_main
keepssourcebans++
sbpp_checker
now usessourcebanspp_checker
This allows proper verification of specific libraries via
LibraryExists
and avoids any confusion between the two plugins.Description
The main issue is a library name conflict where both sbpp_checker and sbpp_main were using the same name "sourcebans++" when registering their library via
RegPluginLibrary
. This was causing problems when checking for library existence withLibraryExists
.Motivation and Context
LibraryExists
withsourcebans++
for using sbpp checker natives, wich was always incorrect to due the sameRegPluginLibrary
as sbpp_main.How Has This Been Tested?
Tested with a test plugin implementing all new forwards:
Screenshots (if appropriate):
Types of changes
Checklist: