re-enable /co i for ops

Co was blocked due to a vulnerability that was raised, and as we are no longer in a position to easily or want to maintain a custom fork of CoreProtect, I think we will now likely block /co for OP's going forward unfortunately, as maintaining a fork of CoreProtect just for the sake of enabling this is not really a sustainable option imho

Why not add a command like /inspect that behaves like /co i in which OPs can use? Use the CoreProtect API
https://www.minerealm.com/comm…iewtopic.php?f=32&t=16687

@anthony#1779 This seems like a reasonable solution to me. Invoking the official API is much more sustainable than forking the entire plugin.

@StevenNL2000#1783 yeah I'm inclined to agree. When I get home I'll take a look as it would be my preferred way forward if we allow non admins to use Co inspect

@StevenNL2000#1783 @wild1145#1790 According to Telesphoreo there is no API functionality on behalf of CoreProtect for toggling the inspector and IntelliJ has personally declined (to him) the possibility of it being added.

@fssp#1811 We don't need to toggle the inspector, we need to perform lookups. We can even reuse the code for the logstick to perform a lookup when it is used.

Vouch

nay

Vouch I need this so badly

Object, iirc this can be abused a lot by just making a bunch of calls to the database, which can cause lots of issues with the dB not being able to handle the amount of requests

So we won't re-enable the native core protect commands, because it will require us to try to maintain a custom variant of core protect, which is not something we want to do.

Given CoreProtect does have an API and we're storing in MySQL anyway, I will approve this suggestion but only if we implement this functionality as part of TFM and are not using the native /co command.

I will also ask that we have a cool down on the command / interface which should be able to be configured as part of config, as I believe the fact /co I doesn't have a cool down / queue logic seemed to be what caused us issues at the start.

@SuperRyn#1959 Because you can't see people doing it... You're not spamming commands, you're spamming queries using /co i

FS-14 raised to implement the custom command as previously described.

To update there is now an /inspect command (I think is what it was called) which will allow OP's (And admins) to inspect blocks using CoreProtect without exposing the issue we originally had.