KrimBuy:Eng: Unterschied zwischen den Versionen

Aus Minecraft Gameserver Wiki
Wechseln zu: Navigation, Suche
(Configuration of rulesets)
(Configuration file)
 
Zeile 155: Zeile 155:
 
           y: 0
 
           y: 0
 
           z: 0
 
           z: 0
 
+
      permOut: '' - permission needed to build outside of the region.
 +
      blockpvp: false - should the plugin handle the pvp on this world?
  
 
=== Download ===
 
=== Download ===
 
[http://dev.bukkit.org/server-mods/krimbuy/]
 
[http://dev.bukkit.org/server-mods/krimbuy/]

Aktuelle Version vom 27. Juni 2013, 19:34 Uhr

KrimBuy

KrimBuy is a fully automated protection plugin. It enables you to easily crate rules for diffent types of plots in your database which outline the properties of those plots. The protections that are then build will then adhere to those rules, granting you endless flexibility through their sophistication, even allowing you to control which (perhaps ugly) blocks shouldn't be created

At the moment, the plugin is localized in german. A multi-language version will be submitted on public demand.

Video Tutorial

Usage

User-Commands:

  • /buyGS = Buy the selected plot.
  • /upgradeGS = Upgrade your plot the the next available level.
  • /passGS = Set a password for your plot. (Like with LWC)
  • /useGS PASS = Use a password to access a plot.
  • /sellGS = Sell the plot.
  • /nextGS TYP = Your compass points to the next free plot of the given type
  • /mineGS TYP = Your compass points to the next free plot of the given type that belongs to you.

Administrative commands:

  • /listGS NAME = Lists all plots of the given player with their respective IDs
  • /delGS ID = Deletes a plot.
  • /giveGS NAME = Presents the plot to the user. If no parameter is given, it will DELETE everything on the plot.
  • /tpGS ID = Teleports to a plot.
  • /nolooseGS NAME = Excludes the player from the auto-free system until he logs in again.
  • /kbruleset TYPE = All future plots will have the ruleset TYP.
  • /makesell PRICE = The plot will be purchaseable at the given price.
  • /kbupdate = The plot will be recomputed. (E.g. Size changed, ..)

Permissions

   kb.buy:
       description: User permissions for buy
       default: op
   kb.upgrade:
       description: User permissions for upgrade
       default: op
   kb.create:
       description: admin permissions to create
       default: op
   kb.build:
       description: Allowed to build everywhere
       default: op
   kb.chest:
       description: Allowed to open chests everywhere
       default: op
   kb.nochest:
       description: Not Allowed to open chests :P
       default: op
   kb.interact:
       description: Allowed to interact with everything
       default: op
   kb.admin:
       description: Administrative permisssions
       default: op
   kab.build:
       description: Allowed to build (anti-guest-grief)
       default: op
   kab.interact:
       description: Allowed to Interact (anti-guest-grief)
       default: op

Configuration of rulesets

The rules themself have to be added in the mySQL - Database. To do so, insert them in the table _ruleset.

id: Leave empty, will be added automatically


onlyamount: How many plots are allowed? 0 = unlimited


ruleset: Name of the ruleset


level: Level of this rule. Starts from 1.


permissionnode: Permission needed to buy plots of this type.


controlblockheight: Vertical distance from the control-block (bedrock) to the bottom. Negative values enable you to place the


control-block below the surface.


height: The plots height.(The height that users are allowed to build in)


deep: How deep is the plot.


price: Needed for anything that uses levels. With level=1, the value has no effect at all.


bottom: A comma-separated list of blocktypes. Blocks of those types form the surface of the plot. Specification DamageValues/SubID's isn't possible.


blocks: A comma-separated list of types that can neither be added, destroyed, nor modified in any other way on this plot.


miet: Daily fees that will be withdrawn from the proprietors money account. 0 = deactivated. 1 = "equals the price that the user paid to buy the plot. (-> /makesell)". Everything else: the actual fee.


autofree: Number of days of inactivity after the users plot will get deleted. 0 = deactivated.


nobuild: On the plot may only be built when it was bought. 1 = on. 0 = off. Important: Should always be 1, too many of those "0" plots slow down the server.


clear: The plot will be cleared when it is bought. 0 = off (not recommended), 1 = only the surface, 2= everything is going to replaced with air.


cansell: May the user sell his plot ? (important with fees) 0 = disabled, everything else = the percentage of the original price that he gets.

pvp: if the plugin should handle pvp of the world, then it can be enabled for this lot here.

indoor: only allows building if there is a roof

pricexp: only in use with the plugin KrimXP


gruppe: Links/Groups two rulesets together. Name of the group and ruleset together make up the plot-name that is displayed to the user. Especially useful for onlyamount. Equals ruleset-name if left empty.

Another little tip: If "no" is chosen as a password for a plot, everyone who hasn't used / tried a password may build on the plot. "no" is the default value. Should soly be used in exceptional cases, nobuild = 0 is more recommendable.

Configuration file

If it hasn't been created automatically -> Create a folder KrimBuy at plugins/.

Config-Explanation: System:

 Database:
   Type: mySQL -- don't change
   Settings:
     Name: DATABASE
     Table: PREFIX
     MySQL:
       Hostname: HOST
       Port: '3306'
       Username: MYSQL_USER
       Password: MYSQL_PASS
 worlds: world,world_the_end -- worlds that the plugin should be active at
 interactMessage: 0 -- if set to 1 it will send the player a message if he has no permissions to build
 lang: en -- language, de for german or en for english
 sponge: 1 -- place a sponge on a free lot
 hookPistonEvent: 1 -- check piston events - can take a lot performance
 worldLimit:
   default: -- default value for all worlds - where it should be protected, you can add one for every world
     protect:
       from:
         x: 0 -- keep on 0 if you dont want this feature and protect the whole world
         y: 0
         z: 0
       to:
         x: 0
         y: 0
         z: 0
      permOut:  - permission needed to build outside of the region.
      blockpvp: false - should the plugin handle the pvp on this world?

Download

[2]