FakeOP Advanced
Fool your annoying players into thinking they have OP.
Features:
- Define custom commands along with messages to send the user on command.
- List commands to run on the server once the user sent a fake command.
Commands/Permissions:
- /fakeop add/remove xKaikz - fakeop.op - adds/removes users from being a fake OP
- /fakeop reload - fakeop.op - reloads the users, fake commands and run commands
How-to:
- Annoying user A comes online and says they want OP.
- Admin B already has their run.txt setup with ban $sender in the first line.
- Admin B does /fakeop add UserA
- User A tries to /op GrieferC, but is instead banned instantly.
run.txt/commands.txt Macros:
- $sender - (only for run.txt) replaces with the username that the command was run from
- $1, $2, $3 etc - arguments passed in a command. If you have /cmd $1 $2 $3, you do /cmd i am awesome, it would return i am awesome.
- &color - &b is light blue. Usual Minecraft colors.
Note:
- Setting the '*' fake command will return the message set for any command that is run by the user
Now I Am The ONLY OP ON MY SERVER!
Thanks!!!
@Zath137
You can do that already... Set the fake command "*" to something then set the run.txt command to "ban $sender Get off my server".
@antty2003
I want this so badly!
@Adondriel
Yeah, most of my plugins don't work with the console, something I need to absolutely fix. I'll do so over the weekend.
i cant seem to use this with console?
Make it so that when they execute any command (any command) make it change it to /ban <fakeop'dplayername> Get off my server..."OP?!" LOL
@65Wolf
Sorry about the wait. Stupid BukkitDev...
You can have multiple commands on each line in run.txt, it will just run one after another. If you ban or kick the $sender in run.txt, they shouldn't be seeing anything. The plugin shows the fake message in commands.txt, then runs the commands in run.txt.
I'll have to look into the last two issues. I never run into either of these in testing.
@Superkabii
lol, I've had this plugin on my server since the whole Planet Minecraft this started, just saw a Reddit post about it and remembered I had it. :3
The problem I am seeing, is that after the message from Command.txt is displayed to the FakeOp, it then displays the normal message from bukkit:
Unknown command. Type "help" for help.
This message needs to be shut off. Dead giveaway that something is up otherwise.
For reference, my Run.txt file was left empty when doing this!
Also, when users who are FakeOp'd do /pl or /plugins, after displaying the fake message, it also runs that command. I tried a few other commands, but they did not work, just gave the appropriate fake message, followed by the bukkit message, as stated above. We do use the PluginList plugin.
Now, another note. I added a line into the Run.txt file. I added kick $sender (in place of ban $sender). Now, as the user does not have access to that command, when the FakeOp types in any command, it will not kick him. The reason shown in console is that the player was 'denied access to the command.'
I feel special now.
ok, let me see if I'm understanding this correctly... Lets say we are using the default commands.txt, and run.txt, that are provided by the plugin. Am I correct in thinking that commands.txt will be ignored (or superceded) because of the information line in the run.txt file thats says 'ban $sender'? Therefore, the first command Fakeop UserA tries will automatically ban him because of the ban $sender line in run.txt? (And ignoring the 'ban:&e$1 banned.i response as indicated in the Commands.txt file?) So basically, this would be a one-time shot for UserA to use any command? Once he does, he's banned? (Or has the effect of whatever command line we would put in the first line of the file run.txt.) And am I correct in assuming only one command line can be placed in run.txt?
So then, if I were to clear the first line in run.txt and save it as a blank file, the command responses listed in the commands.txt would then show Fakeop UserA the respective responses, based on what command he typed in? Is this a correct assumption? So basically, the run.txt file supercedes the commands.txt file?
So, if run.txt is now an empty file (no command listed in the run.txt file), and Fakeop UserA now typed '/op GrieferC' - then Fakeop UserA would see the message shown in commands.txt file, which in this case is as follows: 'Opping GrieferC' - Correct?
I guess bottom line, as 1cec0ld aluded to earlier, a little clearer explaination of the files would be nice. Leaves a lot to assumption.
And I agree that his idea of allowing us to set 'sudo' commands would be sweet!! However, if implemented, I would caution server owners to guard setting it to ban someone other than the sender, for example: if UserA tries to Op GrieferD, then have it ban GrierD instead. This would be a neat feature, BUT.... if UserA gets smart and figures this out, he could ban your legit players or admins the same way!
Thanks in advance for clarification!
@1cec0ld
Alright, I'll see what I can do.
I'd prefer it, yes. A custom -different command than what they enter- per command I choose. I never know what idocy they're going to try, and Its nice to have a different response for them. And funny to mess with regular players as well, something to laugh over. Thank you for your time
@1cec0ld
Configs should be generated when the plugin is first run. So you want it to run a different command per fake command?
Can you create an example config? Would it support for example: FakeOpA runs /gamemode (returns message "You are not worthy) and/or FakeOpA runs /kill (anyone) (and runs /suicide instead)
So I like your /ban idea, but im a bit more cruel and horrible.