BuildersPlot
BuildersPlot allows servers to easily protect their worlds by assigning plots to their guests. In this way, BuildersPlot allows people assigned to plots to only build inside those plots. No more grief, block spam, or fire problems. All of these actions are limited to land inside a plot. Plots are fully configurable and can be any size. They can also be claimed by guests if set up a certain way; drastically reducing the amount of attention needed by server staff.
Features:
- Easily create Plot both claimable and directly owned by a player.
- Force your guests to build in their own plot.
- Grief, block spam, and fire issues completely blocked outside of plots (No more grief!)
- Protect your guests' builds with ease
- Teleport to other player's plots (And your own plot)
- No more need to rollback, grief can't happen in the first place!
- Simple commands to make, manage, and delete plots.
Commands: [Parameter] represents an optional parameter whereas <parameter> represents a required parameter.
- /plot - Displays all commands ingame.
- /plot create <Plot Name> <Plot Owner OR "NoOwner"> - This allows admins/mods (specified in player.yml) to create a plot by using 2 points (point they are standing on and point they are looking at) to create a cuboid region. If second argument is NoOwner, guests will be able to claim this plot.
- /plot mark <Plot Name> <Plot Owner OR "NoOwner"> - This creates a plot but instead of using point1 as the block you are standing on and point2 as the block you are looking at, it uses the points you selected with the marker tool. (Left click with gold hoe for point1, right click for point2)
- /plot info <Plot Name> - Displays info for the specified plot.
- /plot edit <Plot Name> <point1 OR point2> - Allows someone to edit one of the points of a plot by using the block they are looking at as the new point.
- /plot delete <Plot Name> - Deletes the specified plot.
- /plot claim <Plot Name> - Claims the specified plot if it exists or isn't already owned or the player doesn't already own a plot.
- /plot unclaim <Plot Name> - Unclaims the specified plot
- /plot tp [Plot Owner]- Teleports to your plot (or the player specified's plot)
- /plot list - Lists all unclaimed plots
- /plot addMember <Player Name>- Adds an exempt player to players.yml (This player will not be restricted to building in a plot anymore)
- /plot addMod <Player Name> - Adds a player who is allowed to create/delete/modify plots and add members to players.yml
- /plot ignoreWorld <World Name> - Adds a world to worlds.yml (BuildersPlot will no longer stop block events in this world)
- /plot removeIgnored <World Name> - Removes a world from worlds.yml
- /plot reloadConfig - Reloads all the config files without having to restart the server.
- /plot expandUp <Plot Name> - Sets the upper Y-Limit of this plot to 256.
- /plot addFriend <Plot Name> <Player Name> - Adds this player to this plot's friends list, which allows them to build in the plot as well.
- /plot removeFriend <Plot Name> <Player Name> - Removes this player from this plot's friends list.
Plot System Functionality:
The plot system requires a guest to own a plot before they can build anywhere. Without a plot, they cannot burn/break/build anywhere. Admins (or Moderators specified in players.yml) are allowed to make plots and either assign them directly to a guest or make it claimable (Using "NoOwner" as the Plot Owner parameter). That guest can now build only in that plot, and no where else
Permission Nodes (Work with most Permissions plugins):
- buildersplot.create - Allows a user to create a plot
- buildersplot.mark - Allows a user to create a plot using the Marker Tool (Gold hoe)
- buildersplot.edit - Allows a user to edit a plot by either using the block they are looking at for point1/point2 or by using the points selected with the marker tool
- buildersplot.delete - Allows a user to delete a plot.
- buildersplot.config - Allows a user to reload and modify the config files via command
- buildersplot.teleportother - Allows a user to teleport to another person's plot (/plot tp <PlotOwner>)
- buildersplot.exempt - Exempts a user from plots (same as adding them to members list in players.yml ... this user can build anywhere now)
Per-World Preferences for Plots:
With the implementation of v1.1 you might notice a worlds.yml hanging around in your BuildersPlot folder. The first time this is generated, it is empty. This means that by default, BuildersPlot watches all of your worlds and makes sure that everyone in all worlds is restricted to plots (unless they are in players.yml, admin, or have the buildersplots.exempt node). If you execute the command /plot ignoreWorld <WorldName you will add this world to worlds.yml and BuildersPlot will ignore all block events in it. This means that the world will no longer be protected by grief! If you wish to remove the world you can execute the command /plot removeIgnored <WorldName>. This removes the world from worlds.yml.
This doesn't work
I don't know If you guys ever check this or ever intend to update it, but this is a much better concept than the other plot plugins, custom size plots is great! however, I would like to request you incorporate worldedit's gmask #region somehow, maybe? so that i can give people worldedit without worrying about them leveling other people's builds (just as a grief protection, new members don't get WE anyway) this plugin also crashes occasionally disallowing people to make plots before I reload, I can give you the log if you reply to me/intend to update.
whenever someone that is not op tries to claim a plot there is an internal error
Are you planning to update this plugin for 1.3.2 or not? I would love to know, because I still have the max plots issue.
hellooooooooooooooooo long time no see, sniffle YOU TOOK MY VIDEO CLIP DOWN SNIFFLE :( . just about to reinstall builderplot but i need to no before i do how will it work on a Tekkit server ? is there any none conflicted problems between them ? . also did you add the expand vert when making a plot
the old utube Video of Builderplot
will be making a good load more videos on it if it works on the tekkit server as we will be using it as are main :) so show me the love lol
even gave you a shout out on are guild site lol Guild4Gamers
please make it so the admins can reset plots and remove the owners... many leave the plots empty and its annoying to recreate the plots
Thanks :)
Is there an ETA for 1.3.1?
01:13:58 [SCHWERWIEGEND] null org.bukkit.command.CommandException: Unhandled exception executing command 'plot' in plugin BuildersPlot v1.3 at org.bukkit.command.PluginCommand.execute(PluginCommand.java:42) at org.bukkit.command.SimpleCommandMap.dispatch(SimpleCommandMap.java:166) at org.bukkit.craftbukkit.CraftServer.dispatchCommand(CraftServer.java:484) at net.minecraft.server.NetServerHandler.handleCommand(NetServerHandler.java:811) at net.minecraft.server.NetServerHandler.chat(NetServerHandler.java:771) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:754) at net.minecraft.server.Packet3Chat.handle(Packet3Chat.java:34) at net.minecraft.server.NetworkManager.b(NetworkManager.java:246) at net.minecraft.server.NetServerHandler.a(NetServerHandler.java:102) at net.minecraft.server.NetworkListenThread.a(NetworkListenThread.java:82) at net.minecraft.server.MinecraftServer.w(MinecraftServer.java:559) at net.minecraft.server.MinecraftServer.run(MinecraftServer.java:451) at net.minecraft.server.ThreadServerApplication.run(SourceFile:492) Caused by: java.lang.NullPointerException at me.firefly.BuildersPlot.BuildersPlot.onPlotClaim(BuildersPlot.java:1065) at me.firefly.BuildersPlot.BuildersPlot.onPlot(BuildersPlot.java:540) at me.firefly.BuildersPlot.BuildersPlot.onCommand(BuildersPlot.java:494) at org.bukkit.command.PluginCommand.execute(PluginCommand.java:40) ... 12 more
please fix this.
Source?
And... one more issue. It appears the Maximum Plots Per Player is being ignored. I have players claiming a great many plots when my limit is 2... is this a bug?
So... when can we expect the next version?
@TheManiacPT Absolutely genius, thanks for expanding on my comment! That would be wonderful, and I look forward to it!
@FireflyDev
It's fine by me, 'cause I just want to be able to set a tp point in my plot. ;D I'm would be very excited if you implemented both, but I'm really happy anyways, even if only one is going to be implemented! ;D
@TheManiacPT
Great idea. Will be implemented in the next version, however I will only implement 1 /plot settp for everyone's use.
@Expatcat
or it could be a point that you could set, like with "/plot set tp", so you could do "/plot tp" and go to that point, instead of going to one of the selected points, when doing the area for the plot.(And you could only do /plot set tp in your plot) And then there could exist other command that allows you to set a spot where people could tp to there, and another one that allowed you to tp to other plots; For setting a spot where people would arrive: "/plot set tpother"; for teleporting to other plots: "/plot tpother [PLOT NAME]" I think it would be nice this way, because you could set a TP for you, and a different one for other people, making it more private/secure. ;D
When teleporting to a plot, I believe that the point-of-arrival should be the center of the plot, and definitely not the corner. If you think about it, the corner of a plot is an extremely inefficient place to be marked as a teleport location since that is where all other players will go. If you mark your plot with fences, like I did, and revolve around the /plot tp command, then the initial view of all players is the backend of my plot. If possible, a tp to the center instead of the corner would be wonderful.
@Badman959
It tells them the plot's name.
How come when i make a plot, it doesnt tell other players what the name of the plot is or who owns it. Example: 'Welcome to Targets_Tower' , i cannot find a permissions node for it.
When I installed this plugin it was working great the first day, but then when I was testing it the next day, I did "/plot claim" & the plot name, and I got an "error contact the head administrator" (This isn't the exact message)
Could it be a bug with the plot being in a "WorldGuard Region", except I did test deleting the region :/
And I did not own a plot already, please help me a.s.a.p, please. :D :'(