Ever had a problem where a staff member did /op and used it to ruin the server? What about a player getting /op and using it in malicious ways? Or have you just wanted to troll people that ask "Can I have op?" and obviously want to grief. If so, this is the plugin for you!
This plugin is an extremely simple plugin that is used as a way to stop people from getting op!
Current Permission Plugins it works with:
- Normal Minecraft (/deop "player")
- PEX (/pex user "player" remove *)
- Group Manager (/manudelp "player" *)
- Custom commands run when the Anti-Force Op detects op! (as of v1.1)
Soon to work with:
- (PM me any other plugins you can think of for default commands to run!)
Permissions:
mcplugins.antiforceop (as the default)
*Do not give ANYONE this permission unless you want them to be banned
*/op gives this permission, this is how it is detected if a person is an op
*Now changeable as of v1.1
*Using pex and putting the permission "-mcplugins.antiforceop" then adding "*" still bans you!
How to setup:
Probably the most confusing part of the plugin. The way it works is that if anyone has op or permission * then they will be banned. You need to give staff that would normally have op, all permissions excluding the one added in the plugin. They will have the permissions they need just like normal, but won't be banned.
MLTBAQ (or just FAQ):
- Q - "The plugin is banning me!"
- A - You need to setup your permissions file to make you not have every permission in the game (aka op) (Refer to "How to setup")
- Q - "The plugin is banning all people op even staff!"
- A - You need to setup your permissions file to make staff and you not have every permission in the game (aka op) (Refer to "How to setup")
- Q - "This plugin sucks!"
- A - Explain why it sucks? Do you just suck at reading instructions? Is it banning you for no reason? Explain!
- Q - "So I have to add every permission in the game instead of just doing /op. That's WAY TOO tedious!"
- A - You can add all permissions from a single plugin by using the permission "essentials.*" for example, essentials.
Support:
As of currently, I have no direct support options, but I do have access to indirect support here. (Indirect support means you don't spend a dime, but I get money)
Downloads Goal:
5 Downloads: ✓
10 Downloads: ✓
15 Downloads: ✓
20 Downloads: ✓
30 Downloads: ✓
40 Downloads: ✓
50 Downloads: ✓
70 Downloads: ✓
100 Downloads: ✓
I don't believe it is possible to get any more. Prove me wrong
Later : WOW Im surprised. Didn't think you would like such a simple plugin
110 Downloads: ✓
120 Downloads: ✓
130 Downloads: ✓
Terms and Conditions:
When you download and use this plugin, you agree to the following:
Any false bans made by this plugin is your permissions setup's fault, not this plugin.
You may not redistribute or claim this plugin as your own.
You may not decompile this plugin or modify it without the owner's
permission.
Any ops not banned that grief is not the fault of this plugin or the creator.
(Changelogs provide information that the main description doesn't include)
This plugin is an extremely simple plugin that is used as a way to stop people from getting op!
Current Permission Plugins it works with:
- Normal Minecraft (/deop "player")
- PEX (/pex user "player" remove *)
- Group Manager (/manudelp "player" *)
- Custom commands run when the Anti-Force Op detects op! (as of v1.1)
Soon to work with:
- (PM me any other plugins you can think of for default commands to run!)
Permissions:
mcplugins.antiforceop (as the default)
*Do not give ANYONE this permission unless you want them to be banned
*/op gives this permission, this is how it is detected if a person is an op
*Now changeable as of v1.1
*Using pex and putting the permission "-mcplugins.antiforceop" then adding "*" still bans you!
How to setup:
Probably the most confusing part of the plugin. The way it works is that if anyone has op or permission * then they will be banned. You need to give staff that would normally have op, all permissions excluding the one added in the plugin. They will have the permissions they need just like normal, but won't be banned.
MLTBAQ (or just FAQ):
- Q - "The plugin is banning me!"
- A - You need to setup your permissions file to make you not have every permission in the game (aka op) (Refer to "How to setup")
- Q - "The plugin is banning all people op even staff!"
- A - You need to setup your permissions file to make staff and you not have every permission in the game (aka op) (Refer to "How to setup")
- Q - "This plugin sucks!"
- A - Explain why it sucks? Do you just suck at reading instructions? Is it banning you for no reason? Explain!
- Q - "So I have to add every permission in the game instead of just doing /op. That's WAY TOO tedious!"
- A - You can add all permissions from a single plugin by using the permission "essentials.*" for example, essentials.
Support:
As of currently, I have no direct support options, but I do have access to indirect support here. (Indirect support means you don't spend a dime, but I get money)
Downloads Goal:
5 Downloads: ✓
10 Downloads: ✓
15 Downloads: ✓
20 Downloads: ✓
30 Downloads: ✓
40 Downloads: ✓
50 Downloads: ✓
70 Downloads: ✓
100 Downloads: ✓
I don't believe it is possible to get any more. Prove me wrong
Later : WOW Im surprised. Didn't think you would like such a simple plugin
110 Downloads: ✓
120 Downloads: ✓
130 Downloads: ✓
Terms and Conditions:
When you download and use this plugin, you agree to the following:
Any false bans made by this plugin is your permissions setup's fault, not this plugin.
You may not redistribute or claim this plugin as your own.
You may not decompile this plugin or modify it without the owner's
permission.
Any ops not banned that grief is not the fault of this plugin or the creator.
Spoiler: 1.1 Changelog
Changelog:
+ Custom commands to run.
+ Permission Name changeable in config (Recommended to not tell anyone what it is)
+ Added group manager command
+ Custom reason of ban
+ Custom commands to run.
+ Permission Name changeable in config (Recommended to not tell anyone what it is)
+ Added group manager command
+ Custom reason of ban
Spoiler: 1.1.1 Changelog
Changelog:
+ Fixed the config generation error
- The I/O exception error
+ Fixed the config generation error
- The I/O exception error
Spoiler: 1.1.2 Changelog
Changelog:
+ Ops List
+ Ability to disable Permission Check
+ Ability to disable Ops List check
+ Ability to let Op List override the Permission Check (Ops in the list can have the perm and not be banned)
+ A lot more confusion
+ New checking system
+ Customizable interval between checks
- Ideas
- Some lag
+ Ops List
+ Ability to disable Permission Check
+ Ability to disable Ops List check
+ Ability to let Op List override the Permission Check (Ops in the list can have the perm and not be banned)
+ A lot more confusion
+ New checking system
+ Customizable interval between checks
- Ideas
- Some lag
(Changelogs provide information that the main description doesn't include)
Quick facts
- Edition: Minecraft Java
- File type: .jar
- Minecraft versions listed: 1.8, 1.9
- How to install: Install the matching mod loader (Forge, Fabric or NeoForge) for your Minecraft version. → Download the .jar. → Put it in the .minecraft/mods folder and launch that loader profile.
- Where to get it: Opens on Spigot — not every file is mirrored on our own servers.
Install steps are the general flow for this file type — How to install Minecraft Java mods & modpacks walks through it step by step.
Anti-Force Op - Abandoned is a free Minecraft Java mod. Compatible with Minecraft 1.8, 1.9. Downloaded 4,589 times (via Spigot). Download it and open it directly in the game.