Calling hook CanAcceptItem resulted in a conflict between the following plugins: SkinPerks - CanAccept (CanAcceptResult), Backpacks (CannotAccept (CanAcceptResult))

skin perks is a later plugin and backpacks is working with no problem so you could talk to skin perks dev for a fix

The Backpacks plugin only uses the CanAcceptItem hook to disallow adding items being added to the backpack if they have been blacklisted in the config. It's not clear to me what proper compatibility looks like between these two plugins since I'm not sure why SkinPerks is using the CanAcceptItem hook. In theory, items with different skins can have completely different abilities with that plugin, so simply blacklisting items by short name in Backpacks may be too simplistic, so there could be room for improvement with Backpacks here. For example, allowing a hammer in the backpack would also allow superior skinned versions of the hammer which may be too overpowered to store in the backpack for some servers if it's not configured to drop on death or clear on map wipe.

In this case, SkinPerks wants to allow the item to be added to the backpack container even though you have configured the item to be blacklisted in the Backpacks config. Presumably the correct resolution is for SkinPerks to also disallow the item. If correct, SkinPerks should be updated to call the CanAcceptItem method in Backpacks and return the same result if it's equal to CannotAccept.