neoPaintingSwitch
neoPaintingSwitch - switching paintings the easy way:
This plugin uses the same basic idea as located here and here.
This plugin was originally created by Edward Hand (credit to him!) then abandoned and updated by MadMonkeyCo (thanks for keeping it alive) but abandoned again. Because I use it, a lot, I needed it working. So, I have rewritten it to use the bukkit api instead of hooking directly into the net.minecraft server. Meaning it shouldn't break after every new minecraft version.
How it works:
- Place a painting on the wall.
- Right click the painting and then using the mouse scoll wheel to scroll through the paintings.
- When you find the painting you like simply right click again or walk away from the painting. The plugin will disengage and the painting you have selected will remain.
There you have it, in a nutshell, it simplifies the selecting of paintings and saves alot of time. The plugin is also smart enough to know which paintings are the correct size for the space available. No commands to remember, simply click and scroll. Simple as that.
Features
- Allows you to scroll through paintings by aiming and right clicking at them and using the mouse wheel to scroll through paintings.
- Permissions support ("neopaintingswitch.use"). -Groupmanager, bukkit permissions, niji based permissions, bPermissions, Vault, PermissionsEx and any other permissions that works with bukkit.
- config to turn off permissions checks entirely
- Support for worldguard regions
- Remembers last painting used and will attempt to use the same painting for future placements.
Permissions:
- neopaintingswitch.use
Config:
- free4All
- false : enables permissions checks and allows anyone to switch paintings
- true : disables permissions checks and allows anyone to switch paintings
- debug
- true: enables permission debug traps
- true: enables permission debug traps
If you are still not convinced this is the plugin for you, check out the review made by ServerMiner.
if you like this plugin and want to support me. Its much appreciated. :-)
Donate With BitCoin 1NfcRtfUgqmQc3o3wKtN4k6MLKJSAetyHc
This is great for VIP!!! The vip pepele can use it. and it is simple to change a paiting. and no-vip pepele can't use it. and it is hard to change a paiting.
mhuahaha!! XD
Now I have more for vip users.
The latest version if now available. I have provided a new download mirror. Seems github decided that having a download section was just TOO confusing for everyone so they removed that capability from accounts. I'm now migrating over to sourceForge for my projects. Hence the new download mirror.
The update should be available for download on BukkitDev as soon as it is approved.
Until then you can either use the mirror or bypass the approval process by going to the following link neoPaintingSwitch v133
@USM666
Thank you, main page updated. :)
Your plugin has been reviewed by USM's Bukkit Reviews at http://www.youtube.com/watch?v=8NaCAd8qis0
@BangL
Hmm, I guess I miss read the code when I posted but its not showing region; instead the world name. Although, I must confess I dont use worldguard and dont know how it works. So now I'm relying on users for this implementation. I assume the world name is used as a region? In any case, the implementation from the pull is unaltered. So, regardless of my misunderstanding it should still work as intended.
Thanks for clearing up the confusion.
@arcvvolf
the permission check is "worldguard.region.bypass.<region>", not player. and the reason for this is: this also includes "worldguard.*" or "*" this allows changing of paintings also for non-op admins. (like the wg build check)
@Cultist_O
Originally I was hooking into worldguards regionManager and checking isOwnerOfAll or isMemberOfAll worldguard methods against the Player attempting to modify a painting. The pull changed that to testing for isOp or if they have "worldguard.region.bypass.player" permission, and then hooking into regionManager using the canBuild worldguard method for permission checks.
So, yea, two different methods, hence different way of interacting with worldguard. It will need testing though.
@arcvvolf
Unfortunately I am waiting for a few things before I update to 1.4, good to know that there is something in the works though, I am happy enough with that for now. Once I have everything else in order I will try it and get back to you (though it might not be a beta by then) Mind if I ask how they will interact differently?
Thanks a lot!
@Cultist_O
There was a recent pull request for dealing with worldguard support. It changes how painting switch interacts with worldguard. If you can, please try the latest beta I have compiled. If that doesnt work to your satisfaction please let me know and I can add a config option for disabling worldguard support. Thanks!
Github mirror
You can get it at the link above. NOTE: this will only work with the latest bukkit build. (1.4.2-R0.2 build #2449) and versions up from that. Due to new api changes and event deprecations soon to take effect.
Any chance you could add a config setting to disable the WorldGuard support? Or a permissions node to allow manipulation regardless of regions? On my server we use both plugins, but we don't utilize the claims functionality of WorldGuard, instead admins create regions with certain effects, and to save their WorldEdit selections for later. Unfortunately, if someone happens to live in an area we've done this with, they can no-longer switch their paintings. Furthermore, even admins, who should be able to do pretty much anything, can't change paintings inside a region. Or if there is a simple fix using WorldGuard please let me know.
@arcvvolf
Yaaay it works now :D thx
@pkt77
Thank you, that was much more helpful. There was a bug some how introduced during worldguard implementation. It has been fixed and everything is working correctly.
The new update has been submitted to the bukkit dev site.
It will probably take a while for it to be approved. Until such time the link is here neoPaintingSwitch 1.321 for those who want it now :)now available via bukkit dev.@arcvvolf
The folder doesn't spawn in the plugins directory, but in the console, it says the plugin has enabled.
@pkt77
All my tests show it does work with 1.3.2. Saying it doesnt work will not help me help you. So if you have something specific that you see not working let me know. Otherwise, ....
This plugin does not work with 1.3.2 :(
@OriginalMadman
neoPaintingSwitch 1.321This is a version with members of regions allowed to also have permissions for painting switching.Test it out and if no one has problems with it, I'll upload this as the next official version.
@OriginalMadman
It wont be hard to add members too, in fact 1 line of code at most... I really dont use worldguard so I dont have a clue as to how its permissions worked. Thats why owners were the first choice.
Next version, maybe today or more likely tomorrow.
@arcvvolf
Excellent, much appreciated! Will install and test now. Although I do think members should be allowed, as they have building rights in the region (the only difference is that they can't administer rights in the region).
@Juelz0312
I'll test to see if this is true. But I find it HIGHLY unlikely because paintingswitch doesnt mess with blocks only the painting entities and only using the built in bukkit method for switching a painting. So I'm pretty confident you have a conflict with some other plugin and Orebfuscator and not neopaintingswitch.
This plugin conflicts with Orebfuscator, the anti Xray plugin. The creator of Orebfuscator told me that you should make a fix. Plz fix :3