admittance
This plugin provides a sign-based activation mechanism for all sorts of doors, levers and buttons. Mechanisms can be activated by right clicking on a sign. Doors will change their open state (no double doors yet), levers and stone-buttons will activate , for a certain amount of time, then deactivate/switch back, depending on sign setup. The access can be restricted, so players may or may not have access depending on the syntax of a sign.
Maintenance Phase
Due to timing constraints i will most likely not add much more to this plugin, however i will keep it updated as long as possible.
Quick links: Features | Installation | Configuration | Permissions | Compatibility | API | FAQ
Motivation:
- Inspired by Lockette and WorldGuard(indirectly) this provides a way to grant certain or all players access to doors and redstone circuitry, even if those players do not have access to those, for instance due to WorldGuard region flags or locking by Lockette.
- It is possible to have the chest-access and use flags set (WorldGuard) and using a locked door (Lockette) paired with an admittance sign, to restrict the access to the whole area at once to certain users. Thus access to areas, say a mob grinder can be sold by an admittance-sign, without allowing people to change the interior, still easy to maintain and visible.
- With admittance it can be directly visible who has access.
- It is not a high security plugin, whatever that is, you have to mind door-exploits and some uncertainty on shutting down, if people trigger mechanisms shortly before shutdown of the plugin.
Basic features (features/basic):
- Public access
- Restrict access to individual players (up to three per sign)
- Restrict access on base of a permission.
- Toggle mechanisms once is possible, not having them switch back again.
Party/Team features (features/party):
- Restrict access to members of the party of a certain player (only possible while that player is online, up to two).
- Restrict access to members of a party with a certain name (up to two).
Economy features (features/economy):
- "admittance fee" - one time fee for getting access.
- "buy exclusive" - buy exclusive access (The sign changes to restricted/indiviual access for the buyer).
- Support for currency specification (Multiple currencies work with MultiCurrency and PluginLibSharedLibrary).
Details:
- All blocks that are orthogonally adjactant to the block the sign is attached to will be checked for lever,button, door (metal/wooden).
- Also works with signs that stand on a block.
Protection features (features/protection):
- It is possible to test for a player placing a sign, if the player may trigger blocks which the sign would activate. If the player is not allowed to trigger mechanisms on those blocks, it will be denied to place the sign. Currently there is only support for linking to WorldGuard with canBuildChecks, but it can be extended for custom checks. Further protection plugins/solutions will be supported, lateron.
Compatibility:
The stated versions are the earliest that were tested, you should in general use the newest.
- The newest version is always tested with the latest RB of CraftBukkit, but also with one of the latest CB snapshots, 0.4.2 might be a candidate down to RB 1060.
- WorldGuard (check if player can build on activateable blocks on placing the sign. Versions tested: 5.2.2 and above)
- iConomy 5 (very basic, only one currency. Version: 5.0.1 tested)
- iConomy 6 (very basic, only one currency. Version: 6.04b tested)
- BOSEconomy (Versions: tested: 0.7.2)
- Essentials Economy (Essentials version 2.6.1, 2.5.7 - admittance 0.3.3 and above)
- MultiCurrency (Version 0.11 - admittance 0.3.4 and above)
- Vault (Only allows for one currency), linking to another economy plugin.
- mcMMO (for party, Versions tested: 1.0.50 and above)
- With plugins that set the EconomyInterface
- With plugins that set the PartyInterface
- With plugins that set the CanTriggerInterface (for checks if a sign may be placed.)
NOTE: If you have several plugins installed, that admittance might want to use for economy for instance, then you can use the configuration to let admittance exclude or choose a certain one. This could be the case with Essentials+iConomy, for instance.
State:
- First non-beta release is worked towards (actually it is pretty much done with 0.4.0 - beta).
Upcoming changes / current topics: See Implementation/Progress for detailed information.
Notes:
- Names longer than 15 characters do not fit on a sign. The only way of granting access is to use public or party access, or to use the perm-based access: give the user an abbreviation permission like "admittance.group.longname42" so access is possible using "[longname42]" instead of the user name.
- This does not track states of doors or other mechanisms on shutdown or disabling the plugin, this is left to a locking plugin like lockette.
- Admittance does not provide protection ! To really restrict access you need to combine it with a protection plugin like WorldGuard.
- The [buy exclusive] option can be used to have a simple and visual confirmation of someone sending you money, for the sign changes to restricted access for the player that used it.
- It is possible to place fee/buy signs for other people (cooperation possible).
Feel free to pose questions, request features or just discuss stuff !
@ThisUsernameIsMine
Likely, i give it 48 hours in total :).
@asofold
Probably not.. but "My Server Is Fun And Awesome" tops it off (i smell an ad from a rat :D )
@ZoeZombieCanada
Is your server using admittance !?
@Master_Zangetsu
Are you refering to permission-based access or to party access?
your group based acces instruction make no sense what so ever ... please revise them
@Conkill
Thanks for reference, i could not find a good match for "magicalspells", but now i understand.
@asofold
I found the culprit, for future references, that magic spell lock thingy was LWC causing the signs to be locked and because that has not yet been setup correctly it refused permission.
So lesson 1: Don't start in alphabetical order when installing mods, look at the onces that needs permissions first, but thanks for your reply's I'm just glad I can use this plugin now.
@Conkill 1.
Obviously the magicalspells thingy conflicts somehow, i am not sure what that does, maybe it greedily inaugurates all sign syntax with "[...]" or there is something else with that plugin, like preventing interaction on protectd grounds.
You could try as a workaround, to set the first-line entry (and maybe the second line entries too) in the admittance configuration to something that is not using "[" and "]", maybe like "*admittance*". I have to check out what magicalspells does concerning protection, if it prevents all interaction, it might get difficult.
2.
Yes, with a newly generated configuration file you will have to set superperms to true in the permissions section !
Coming from 1.7.2 the plugin still sets that to false, because many people just wanted to use it out of the box, be it with or without permissions plugin.
I will probably get rid of the "admittance:" prefix in the configuration, i comes from a time when i thought, i might integrate admittance into something else, or let it use the configuration file of another plugin. Also i might set superperms to true for the next version, but that might take a while.
@asofold
I tried everything I deleted the .config file so it would re create
I actually had those permissions without the * the funny thing is everyone can create signs we use [admittance] [fee] 10 PlayerName
When you click on the sign it gives you that notice and says it's lock by magicalspell. When I use [admittance] same thing when I use "admittance' same error. i also assigned the admin permissions to the group just to check if that might fix it and nothing, so it seems the creation part of premissions work, but not the use part only way I can use is if I'm op
PermissionsEX is also clean new Permmission nodes started from scratch admintance was first plugin to check and haven't gotten past that, the only other plugins that communicating with admittance is WorldGuard and EconomyInterface is VaultEconomy
Any other ideas where I need to look.
@Conkill
I am using PermissionsEx myself, so in general that should be possible.
I almost had forgotten myself how to do this - the wildcard permissions do not work!
You can howver use the parent nodes "admittance.use", "admittance.create" and "admittance.cmd", admittance will map those internally.
The perm-based access should pose no problem, it just allows you to use something like "[Police]" instead of a user name, so all players with the permission "admittance.group.police" will have access to that sign (i am using that for access to doors in the "Ministry of Police", where we have different groups that inherit the admittance.group.police node from each other).
You get a "private sign" message ? That sounds strange, it should be something like "You don't have permission to use this type of sign (PUBLIC).", otherwise we have to check what protection plugins you are using, it might conflict with the "[admittance]" syntax, in that case one still could use other magic words without "[...]", that is configurable. To test for such conflict you could either change the first-line entry with "[admittance]" to "admittance", or without changing configuration test the toggle sign with "[admittance]".
Hi I love this plugin, was using it back when MC was version 1.7.3
Curently I'm busy setting up a new economy server and would like to use this plugin again but for the love of myself I just can't get this to work, II'm using PermissionsEx and have added - admittance.cmd.* - admittance.create.* - admittance.use.* - modifyworld.*
to the Default group everyone can create signs also need to mention for economy part using latest economy version but if the user is not an op he or she can't use the sign gives that private sign notice and I just can't find any node that I could add so users can use the signs, i've turned of perm-based and any permissions and still same result any ideas on how toget this plugin to play nice using permissions ex
@funk1983
I created a ticket for this: http://dev.bukkit.org/server-mods/admittance/tickets/2-check-npe-in-vault-economy/
Please provide some information:
When ever i try and use another players "fee" sign i get the attached error in the console, any ideas whats causing it?
@DJBeauchamp
I used BOSEconomy 0.7.2 from bukkitdev.
It would work as op and as non-op given the BOSEconomy.common permission, using PermissionsEx.
Note: BOSEconomy uses the currency "coin" by default, so $ will not work at first.
@DJBeauchamp
(See pm)
Maybe i should make it beta though...
Awesome! I'll definitely try it out with BOSEconomy and PEX tonight.
I just might do that :)
@DJBeauchamp Maybe ask PEX to add a graphical one...
Well, i uploaded admittance 0.2.2 with probably working BOSEconomy support.
So once the file is approved that will probably be an option too, because it seems to accept the PEX compatibility layer (which would be like phoenix permissions 2.7, if i am right). Not sure what iConomy5 does with permissions.
Ah I'll try that one out then I downloaded PermissionsBukkit last night.
What I really would like is one with a graphical interface honestly. Even if it's web based :P
@DJBeauchamp
Ok, good luck.
On the other hand i just coded BOSEConomy interface, so that will be available, if everything works out... within ten minutes.
Still you will have to set some permissions. I personally decided to use PermissionsEx (PEX) because it seems the best near future solution concerning compatibility, but that is just a quick judgement by my - iConomy6 does not yet work with it.