From my limited understanding; AAC blocks other plugins' security managers, this is an anti-piracy measure similar to the /aac command. If possible it would be nice for AACPlus to implement a way to disable this behavior, or at least an exception for when the NetworkInterceptor plugin in particular is present. There is most likely a way to do this safely (in terms of preserving at minimum a portion of the original anti-piracy measures) by coordinating with the new NetworkInterceptor maintainer who has previously expressed interest in getting these two plugins to work together as per this comment, https://github.com/SlimeDog/NetworkInterceptor/issues/8#issuecomment-664682187. Without having any personal experience with anti-piracy measures myself, could a checksum implemented from either side be of use here?
From my limited understanding; AAC blocks other plugins' security managers, this is an anti-piracy measure similar to the
/aac
command. If possible it would be nice for AACPlus to implement a way to disable this behavior, or at least an exception for when the NetworkInterceptor plugin in particular is present. There is most likely a way to do this safely (in terms of preserving at minimum a portion of the original anti-piracy measures) by coordinating with the new NetworkInterceptor maintainer who has previously expressed interest in getting these two plugins to work together as per this comment, https://github.com/SlimeDog/NetworkInterceptor/issues/8#issuecomment-664682187. Without having any personal experience with anti-piracy measures myself, could a checksum implemented from either side be of use here?