FriskStick
FriskStick
Please, use the ticket system for issues! In addition, make sure to check the Important Information section of this page before downloading!
Requested by TaylaGang- http://forums.bukkit.org/threads/frisking-plugin-read-the-thread-for-more-info.88332/
NOTE: dchaosknight here again, everyone! Before you get excited about my return, don't get your hopes up just yet. I can't say if this is a full-fledged return to maintaining this plugin; it's too early to tell. I can only hope that I won't lose motivation this time around, but that's all it is: a hope. All I can say is this: I'm glad to be updating this plugin again, and I hope you all are, too. Happy frisking!
This highly-configurable plugin will allow you to search people for drugs and other contraband, able to be defined in the config. It also implements other features such as a "beatdown mode", which allows "cops" to beat other players if they don't comply in order to get the job done.
Features
- Right click on or hit a player while holding a stick to frisk them! Don't abuse it, though: with each frisking that they don't have drugs on them, you'll take damage!
- When you frisk them, the drugs that were in their inventory will be taken out and confiscated by you!
- Auto-jail players! (Requires Essentials to work)
- Report other players for drugs!
- Chase players down when they're on the run!
How Frisking Works
The ability to frisk someone relies upon permissions, of which you can find a list below. Frisking is pretty simple: right click or hit the player with a stick in your hand (configurable). Once you've done that, you will attempt to frisk them for a certain amount of time (also configurable), during which the player you are frisking can either run or stay put. If they stay, they will immediately be frisked, taking any drugs in their possession away from them and giving them to you. If the config allows for auto-jailing, the player will also be jailed (NOTE: Requires Essentials to work). If they don't have any drugs, however, you will be punished by taking damage. If the player chooses to run, they will enter a mode called "beatdown mode" and be considered to be "on the run". In this mode, right clicking them won't work; you can only hit them. Once they lose enough health, be it by falling or by you hitting them, they will be too weak to carry on, allowing you to frisk and jail them.
Config
The config reference for this plugin can be found here.
Commands
The command list for this plugin can be found here.
Permissions
The permission list for this plugin can be found here.
Source Code
You can see the source code on GitHub.
What's New?
1.0 Beta
- Rewrote plugin from scratch in an effort to make the code more organized and legible
- Added beatdown mode
- Removed ability to frisk by command
- Fixed every bug currently reported, if memory serves:
- Fixed duplication glitch with renamed items
- Fixed auto-jailing issue
- Fixed frisking inventory issue (the items didn't always appear in the cop's inventory)
- Fixed internal error when frisking
- Added more permissions
- Added more config options
- Switched from an id-based to a name-based system for defining drugs in the config
- Added a few new commands
- Updated to 1.7.9
Click here for the full change log.
Important Information
- If you happen to be updating from an older version to 1.0 Beta, delete the old config file before using this plugin!
- This plugin currently utilizes Plugin Metrics for stat collection. Plugin Metrics collects information concerning the following things about your server: the contents of plugins/Plugin-Metrics/config.yml, the number of players currently online, the version of the server you're running, the version of FriskStick you're running, and the Mineshafter status of your server. It will send most of this information (excluding the Mineshafter status) along with the version of Plugin Metrics being run, the GUID of the server (which is what Plugin Metrics uses to identify servers in place of IPs), and any custom data associated with FriskStick to mcstats.org, where it will be made publicly available for everyone to see. If you wish to exclude your server from this data collection, go to your plugins/Plugin-Metrics directory and set opt-out in the config.yml to true.
- In addition to using Plugin Metrics, FriskStick also uses CurseForge's API to detect available updates on the BukkitDev website. If you wish for the plugin to not make the internet connection necessary to check this, set enable-update-checking in plugins/FriskStick/config.yml to false.
- The auto-jailing feature is dependent on Essentials to work. If Essentials is not installed on your server, the plugin will still load, but the auto-jailing functionality will be missing regardless of the settings in the config.
- If you are installing Beta 1.0 and FriskStick was not previously installed, go into your plugins directory and create a folder titled FriskStick. If you fail to do this, the plugin will crash upon starting. This bug is due to an oversight during testing, as the folder was already present on the test server. It will be fixed in the next release, but until then, I apologize for the inconvenience.
@faxionsurvival
@deleted_8117261
Yeah, I think I stumbled upon something that could possibly help fix that a while back. The only reason I was hesitant to use it was because it was deprecated. I know "deprecated" doesn't mean "broken", but... I don't know, that's just me.
@faxionsurvival
Happy to help. You mind creating a ticket for the bug on the github page? Thanks.
Thanks for the update! No worries guys, the previous build was working, The only bug I still see is the inventory switch for frisked items. They do require a relog to get the items. Its not a huge problem or anything, but the only bug I notice. I appreciate the work on this plugin as you know it is a major part to my server. Thanks guys!
UPDATE: Hey everyone! While it isn't available for download as of making this comment, I'd like to tell you a sort of "Beta" version is on the way. This is mainly for people wanting an update, and it also adds an auto updater for testing. I'll leave it up to domingocool to decide whether or not to add it to the changelog, but I thought I'd might as well let you know!
EDIT: The update is now available for download!
@faxionsurvival
Thanks! It's partially been school-related stuff for the both of us, but for me, just not getting around to it has been a factor. I keep telling myself that I should get to work on this thing, but I end up forgetting, or doing something else. As I've said before, I've been pushing for an update since September, but... well, life. Once again, thanks for being so patient; I know it's probably been a pain!
@faxionsurvival
Hey there! I will be updating the plugin to 1.3.2 R3.0 most likely today.
EDIT: I decided to actually just wait until the latest recommended build comes out. EDIT2: Actually, I'll work on an update. it will just be using a developmental version.
Waiting patiently for an update!
NEWS: I have removed the poll from the front page. To those of you who may be thinking that this plugin is no longer being developed, it is. I know it's been a long time, but I have good news for you: I believe I have a version almost ready for release, so... there may be an update later this month (key word: may, but that doesn't mean I'll quit working on it). Thanks for being so patient, everyone!
IMPORTANT, READ THIS: Due to errors popping up, there's been a... delay, to say the least. I am really sorry, but with school and everything along with those errors, it's dragged on much longer than anticipated. So, I've created a poll off to the side; if you can take the time to vote, it'd be much appreciated. I should mention that if the majority say to update soon, some things may be missing in the next update. Thanks, everyone!
@faxionsurvival
Thanks and no problem. We have some plans for the plugin that you may like for future updates.
Thanks so much, I have donated to you and dchaosknight's project as its a huge part of my server. Thanks for your hard work!
@faxionsurvival
Sure thing. It will be in the next update.
Could you possibly add a permission for players to not be able to be frisked. I run a server with both cops and crooks. I don't want to allow the cops to frisk eachother.
1.3 Alpha is out! A few things have been added and some more have been fixed. The bug where the server would crash when you type a command in the console rather than in-game has been fixed, so that's good news. Also, the /report <playername> command has been implemented so it should work properly. I have also implemented Plugin Metrics so that we can get some stats on the plugin. You can always opt-out if you don't want to send any data or if it isn't working properly. There is no personal data being sent, in case you're wondering. If you find any errors or bugs, please submit a ticket here or on the GitHub page. Don't post a comment about it. Enjoy :)
Anyone here getting an error or crashing when using the frisk command? If you are, please submit a ticket. Thanks.
UPDATE: 1.2 Alpha is here! I just remembered I forgot to change the version name in the file, so if it bothers you for whatever reason, go into the jar file, open the "plugin.yml" file, and next to version, put the correct version in there.
Otherwise, this update includes quite a bit of new stuff, so I would definitely recommend reading up on it!
EDIT: I meant to post this, just for fun: That file took FOREVER and a day to be accepted. I was expecting it to be accepted when I woke up, but it's nearly 13 hours later!
@ryanloder
Could you create a ticket, please? Also, include in it the FULL error log. Thanks!
@dchaosknight
It says unsupported major.minor version 51.0
@ryanloder
I have no problems with this plugin functioning correctly, There is a slight bug with the inventory taking a second to appear in the friskers inventory, thats fixed with a simple relog. Besides that this plugin is a main feature on our server and we love it. If you are having problems make sure you go through your config file and set what you want your cops to frisk and confiscate. Thanks dchaosknight for your hard work!
@ryanloder
What isn't working? As far as I can see, you didn't report anything was wrong in the first place.