|
Post by Simpson_Manor on Jan 19, 2020 5:17:44 GMT
Since theres no updates for replacing original CoreProtect with TF-CoreProtect, a real deal is attempt to make another plugin which it has most codes from CoreProtect Inspection with some codes removed inside the .jar file to prevent anyone access the rollback command or something. The default command will be /i or /inspector or /inspection etc etc...
You might name it as InspectorX, OPInspector, or anything that is suggested plugin name.
However, it is recommended to do it by yourself and start from beginning, not just copy most codes from Inspector. but making your own code if doesn't work and put the plugin and restart/refresh/reload the server.
|
|
?Robin
Club 4000 Member
caleb get off of tf
Posts: 8,027
| Likes: 8,604
|
Post by ?Robin on Jan 19, 2020 5:34:38 GMT
so basically logstick 2?
we can't see coreprotects code so idk what ur going on with this
|
|
StevenNL2000
Forum Admin
Posts: 6,415
| Likes: 6,936
IGN: StevenNL2000
Timezone: UTC+01:00
Member is Staff. Need immediate assistance? Send a PM
|
Post by StevenNL2000 on Jan 19, 2020 16:46:57 GMT
The fact that we installed and decided to keep CoreProtect even though we've had logstick since the beginning is a hint at how difficult it is to make a grief inspection plugin that is even somewhat decent.
|
|
grntbg
Full Member
Omnis anima potestatibus sublimioribus subdita sit.
Posts: 295
|
Post by grntbg on Jan 20, 2020 17:39:18 GMT
...a real deal is attempt to make another plugin which it has most codes from CoreProtect Inspection with some codes removed inside the .jar file to prevent anyone access the rollback command or something CoreProtect is a closed-source plugin meaning that "making another plugin which has code from CoreProtect" wouldn't overcome what kept "TF-CoreProtect" from being implemented. What's the point of this, exactly? With any decent permissions system, you could unblock `/co inspect` for operators. I believe this could still be done with OOBE TFM.
|
|