Bukkit

@AquaXV

My ideas don't point toward a prison server. If I had a prison server, though, I wouldn't exactly need the whole "do this with permissions" hassle. I'd just set someone to that group and call it a day. Problem is, my server isn't a prison server, so I can't just do that and remember everyone's previous ranks AND remember to put them back later on. ;)

If you want to know where I'm stealing "pulling" my ideas from, take a look at SimpleJail (plugin is outdated). It has some of the features I described.

So let's take my example with warping. I don't want regular, ol' innocent players warping into my prisons (to which they can't get out). Nor do I want them nasty convicts warping into the outside world, which defeats the point of being detained. In a prison server, there's probably only a prison to play around in (and if there's more, the highlight of the server is the prison system) so this sort of permissions handling isn't all that necessary.

@Plumeex

This is just my opinion, but I feel like those commands/mechanics belong to other plugins, as this is a jailing plugin, and should strictly stick to all things relating to jailing. Muting and auto AFK kicking can be found in other plugins that aren't strictly made for jailing.

@AquaXV

Sorry for sounding pushy, but I wanted to reiterate this question first from my previous comment: "Also, when players die, will they respawn at their "jail point", whether it's the jail-location or jail-cell-location? (If you decide to add jail cells.)"

If you decide to use a dependency, you could probably use Vault as it's pretty much a one-stop shop for hooking into permissions plugins in general. The problem with restricting certain actions is, how would one go about restricting them without potential plugin conflicts? Permissions would be a clean solution to this, but trying to consider all the possible actions you'd want to block could be a hassle.

Let's take, for example, teleportation. I want to block all teleportation outside of the "prison" (which is a structure with an arbitrary perimeter, and NOT a region recognised by another plugin). But I want teleportation within the prison to still be possible to inmates only. Let's see how I can approach this without permissions.

First off, if you give the ability to block commands via this plugin, I'd have to block all teleportation commands and their aliases. So that would include, but not be limited to: "/tp <arg>"; "/home"; "/warp <name>"; "/sethome"; "/teleport <arg>"; etc. Then, I'd somehow have to make certain commands available to only inmates, presumably also provided by this plugin, like "/warp <exampleplace1>" and etc.

With permissions, I can simply give nodes to deny most forms of teleportation, and give special nodes to allow certain forms of teleportation. Also, most people have Vault on their servers already, as it's pretty much needed for... anything.

I've no problem with making "DateDiff" a mandatory argument, and I think it should be mandatory, but other people could think otherwise (I myself would never be hasty enough to give a permanent sentence). Another solution would render both arguments (reason and DateDiff) optional, but would also be bulky at the same time. If you're familiar with CoreProtect's command structure, you could do something like "/ojail jail p:<playername> j:<jailname> t:<time> r:<reason>" so that whatever arguments can be optional are made optional, and the order of the arguments won't matter.

And thanks for considering all of my ideas and taking your time to make the plugin! I appreciate it. :)

68 years? Looks like I'm going to need parole. :)

Anyway, I have four suggestions to make:

• I do appreciate the idea of forcing someone to be on to pass their jail sentence, but could you add a configurable option to make it so that time spent offline will count too (basically, like a normal temp-ban sentence)? I do understand the merit of making people serve their sentence, but in my case, I would rather intend it to be more as a "lite-ban".
• Set up jail-cells. The system could work basically like "jails within jails". If all jail cells are occupied, search for the cell with the least amount of players and put the player in that cell.
• Instead of resorting to action-restrictions that are internal to the plugin, how about demoting a player to a group, and then restoring the player to their previous group? That way, it's up to the admin to decide how their prisoners are restricted. It could work by adding a player to the designated group-name (name of the group is configurable), then when they've served their time, remove the player from the same group-name.
• I know the person below me suggested this, but a reason for jailing could be important for the purposes of recording a descriptive player-infraction history. Perhaps you could make the "DateDiff" argument mandatory to specify, with an optional "reason" argument afterwards.

Also, when players die, will they respawn at their "jail point", whether it's the jail-location or jail-cell-location? (If you decide to add jail cells.)

Nice plugin , i think u can counting how many times player entered the jail and do some punishments like : ban, mute, etc.. & u can do custom jail reasons like swearing griefing etc.. & do custom punishment too & let the custom jail args like this: /jail <player> [reason]

• hope understanding me :)