Ero sivun ”BukkitPluginConfigs” versioiden välillä

Kulmapaikasta
Siirry navigaatioon Siirry hakuun
(Luotu sivu dualin tämänhetkisistä Bukkit pluginien asetuksista.)
 
(Lisätty irkkikeskustelu permissioneista)
 
(4 välissä olevaa versiota samalta käyttäjältä ei näytetä)
Rivi 2: Rivi 2:


Seuraavassa on listattu joitakin tärkeimpiä pluginien konffeja dualilla.
Seuraavassa on listattu joitakin tärkeimpiä pluginien konffeja dualilla.
Suurimmat muokkaukset on bPermissions pluginin konffeissa, koska ne tietysti määräävät kaikkien käyttäjien ryhmät, prefixit, käyttöoikeudet jne. sekä joidenkin pluginien kohdalla toiminnan, eli jos käyttäjällä on jokin permission node, niin plugin tekee tällöin automaattisesti jonkin toiminnon. Näihin kuuluvat mm. AdminCmd ja Vanish pluginit.


'''HUOM! Tällä sivulla listatut asetustiedostojen sisällöt voivat olla vanhoja, mutta code-tageja edeltävät linkit johtavat serverillä käytössä oleviin eli siis ajantasaisiin versioihin!'''
'''HUOM! Tällä sivulla listatut asetustiedostojen sisällöt voivat olla vanhoja, mutta code-tageja edeltävät linkit johtavat serverillä käytössä oleviin eli siis ajantasaisiin versioihin!'''
Joitakin juttuja muistilistassa:
* Älä poista groupilta tai userilta wildcard permission nodea negatoimalla se! Se johtaa kaikkien kyseisten permissioneiden poistumiseen, vaikka halutut olisivat positiivisina määriteltyinä tuon jälkeen. Eli poista vaan koko rivi konffista.
* plugins/bPermissions/ alla olevat users.yml ja groups.yml ovat esimerkkejä ja templaatteja uusille maailmoille. Käytössä olevat ovat konffit maailman mukaan nimetyissä hakemistoissa.
* Poikkeuksena jos config.yml:ssä on use-global-files päällä
bPermissions Quick Howto:
<code>
These are the default commands in bPermissions
• "/permissions save" Use save after changing permissions with commands, otherwise they'll be overwritten when you reload permissions
• "/permissions reload" Do this for your permission edits to take effect
• "/permissions cleanup" This cleans out all empty users groups from your files. Any user with no permissions and simply in the default group
• "/permissions backup" This backs up all of your permission files!
To do any of these commands, you need the bPermissions.admin permission node.
You can shorten the "permissions" in these commands to "p", "bp", or "perm" .
There are two stages to the command structure for changing group/user meta data/permissions in bPermissions.
Stage 1: Select which object you would like to edit.
example: /world World_Awesome
example: /group Admin - this will create a group if it does not exist, or select an existing group with that name!
example: /user HerpDerp
Stage 2: Change object as you wish, using this structure:
/OBJECT ACTION VALUE
User's available actions: addgroup, rmgroup, setgroup, addperm, rmperm, meta
Group's available actions: addgroup, rmgroup, addperm, rmperm, meta
World's available actions: mirror (mirrorto) (mirrorfrom)
*note: Meta data's VALUE has two arguements, KEY and VALUE. See examples below.
User examples:
example: /user rmgroup Admin This removes group "Admin" from the user selected previously.
example: /user setgroup Noob This sets the user selected to group "Noob"
example: /user rmperm some.node This removes node "some.node" from selected player
example: /user meta prefix Herp This sets meta data "prefix" to "Herp" on selected player
Group examples:
example: /group addgroup Member This makes the selected group inherit group "Member"
example: /group addperm a.node This adds permission node "a.node" to the selected group.
example: /group meta suffix Derp This adds suffix "Derp" to selected group.
If you use an object in a command, such as /world, /user, or /group, It will give you the currently selected object,
EX:
/world, would give the output of, "Currently selected world: yourworldnamehere"
-----------------
Shorthands/one-liners:
To set codename_B to admin in all worlds
/exec u:codename_B a:setgroup v:admin
To add the permission "bPermissions.admin" to the admin group in world "world"
/exec g:admin a:addperm v:bPermissions.admin w:world
• u/g: selects the user/group and provides the name
• a: provides the action (addgroup/rmgroup/setgroup/addperm/rmperm)
• v: provides the value (ie. WHAT you are adding/removing/setting)
• w: provides the world (optional, leave blank to apply to all worlds)
</code>


==== AdminCmd ====
==== AdminCmd ====
Ei vissiin merkittäviä muutoksia oletuksesta.
Ei vissiin merkittäviä muutoksia oletuksesta, paitsi:
 
<code javascript n>
editSignRightClick: false
</code>
 
Ilman tuon disablointia kylttejä ei pysty asettamaan toisen kyltin päälle...
 
Ja pikkukorjaukset itse käyttämieni tagien ja väritysten takia (vai hetkonen korjasinko tuon users.yml/groups.yml prefixistä?? Voi olla että muokkasin tämän kohdan silti...):
AdminCmd/locales/en_US.yml:
<code javascript n>
gmSwitch: '§aGameMode for %player §aswitched to : §f%gamemode'
</code>


[http://masa.dy.fi/minecraft/configs/bukkit/plugins/AdminCmd_config.yml config.yml]<br />
[http://masa.dy.fi/minecraft/configs/bukkit/plugins/AdminCmd_config.yml config.yml]<br />
Rivi 15: Rivi 93:


==== bChatmanager ====
==== bChatmanager ====
Pieniä muutoksia oletuskonffin viestien muotoiluun.<br />
[http://masa.dy.fi/minecraft/configs/bukkit/plugins/bChatManager_config.yml config.yml]
[http://masa.dy.fi/minecraft/configs/bukkit/plugins/bChatManager_config.yml config.yml]
<code javascript n>
<code javascript n>
formats:  
formats:  
Rivi 32: Rivi 112:


==== bPermissions ====
==== bPermissions ====
Yleiset asetukset: [http://masa.dy.fi/minecraft/configs/bukkit/plugins/bPermissions_config.yml config.yml]<br />
Asetusten peilaus/kopiointi jostakin maailmasta toisiin maailmoihin: [http://masa.dy.fi/minecraft/configs/bukkit/plugins/bPermissions_mirrors.yml mirrors.yml]<br />
Käyttäjäkohtaiset oikeudet: [http://masa.dy.fi/minecraft/configs/bukkit/plugins/bPermissions_users.yml users.yml]<br />


config.yml:
<code javascript n>
auto-save: true
track-type: single
debug-mode: false
allow-offline-mode: false
use-global-files: false
</code>
mirros.yml esimerkki:
<code javascript n>
world_nether: world
world_end: world
worlds/dirt62: world
worlds/end_empty: world
worlds/flat62: world
worlds/stone62: world
</code>
tracks.yml (mikäli trackseja haluaisi käyttää, meidän pienellä servulla/käyttäjämäärällä ei ole tarpeen):
<code javascript n>
default:
- default
- User
- Moderator
- Admin
</code>
users.yml (esimerkki):
<code javascript n>
users:
  asdfas_rv:
    permissions: []
    groups:
    - user
  chestbursted:
    permissions: []
    groups:
    - user
  flotari:
    permissions: []
    groups:
    - user
  lanxu:
    permissions: []
    groups:
    - moderator
  masa_:
    permissions: []
    groups:
    - admin
    meta:
      priority: '50'
      prefix: '&f[&dOwner&f] '
</code>
groups.yml sisältääkin sitten varsinaiset oikeuksien määritykset. Se on vielä tällä hetkellä vähän niinkuin TODO :p


==== CleanroomGenerator ====
==== CleanroomGenerator ====
Rivi 39: Rivi 179:
==== HawkEye ====
==== HawkEye ====
HUOM! Ohessa vain muokatut kohdat (log:n alla kaikki kohdat true arvossa, en muista oliko jokin muu kuin flow:t oletuksena false):
HUOM! Ohessa vain muokatut kohdat (log:n alla kaikki kohdat true arvossa, en muista oliko jokin muu kuin flow:t oletuksena false):
Ja tietenkään en tänne laita tietokannan tunnuksia...
Ja en tietenkään tänne laita tietokannan tunnuksia...


<code javascript n>
<code javascript n>
Rivi 53: Rivi 193:


==== MinecraftBot ====
==== MinecraftBot ====
Eipä mitään ihmeempiä, servu, nick, kanava ja muotoilut kuntoon.
Eipä mitään ihmeempiä, servu, nick, kanava ja muotoilut kuntoon.<br />
[http://masa.dy.fi/minecraft/configs/bukkit/plugins/MinecraftBot_config.yml config.yml]
[http://masa.dy.fi/minecraft/configs/bukkit/plugins/MinecraftBot_config.yml config.yml]


Rivi 61: Rivi 201:


==== Multiverse-Core ====
==== Multiverse-Core ====
Oletuskonffi??<br />
Oletuskonffi(?).<br />
[http://masa.dy.fi/minecraft/configs/bukkit/plugins/Multiverse-Core_config.yml config.yml]
[http://masa.dy.fi/minecraft/configs/bukkit/plugins/Multiverse-Core_config.yml config.yml]


Rivi 135: Rivi 275:


==== Multiverse-Portals ====
==== Multiverse-Portals ====
Oletuskonffi.<br />
Oletuskonffi(?).<br />
[http://masa.dy.fi/minecraft/configs/bukkit/plugins/Multiverse-Portals_config.yml config.yml]
[http://masa.dy.fi/minecraft/configs/bukkit/plugins/Multiverse-Portals_config.yml config.yml]


Rivi 165: Rivi 305:
<code javascript n>
<code javascript n>
ItemOpenInvItemID: 280
ItemOpenInvItemID: 280
</code>
==== SimplyVanish ====
[http://masa.dy.fi/minecraft/configs/bukkit/plugins/SimplyVanish_config.yml config.yml]
<code javascript n>
flags:
  bypass:
    blocks:
    - '23'
    - '54'
    - '61'
    - '62'
    - '58'
    - '116'
    - '117'
    - '118'
    entities:
    - MINECART
    ignore-permissions: true
  cmd:
    whitelist: false
    commands:
    - me
    - tell
    - vantell
    - tellvan
pickup:
  exp:
    workaround:
      enabled: true
      distance:
        threshold: 3.0
        teleport: 1.0
        remove: 0.5
      velocity: 0.3
messages:
  suppress:
    join: false
    quit: false
  fake:
    enabled: false
    join: '&e%name joined the game.'
    quit: '&e%name left the game.'
  notify:
    state:
      enabled: false
      permission: simplyvanish.see-all
    ping:
      enabled: false
      period: 30
save:
  enabled: true
  always: true
  interval: 0
  delay: 10
auto-vanish:
  use: true
  permission: simplyvanish.auto-vanish
no-abort: false
permissions:
  allow-ops: false
  superperms: true
  fake-permissions:
    set1:
      permissions:
      - all
      players: []
    set2:
      permissions:
      - vanish.self
      - reappear.self
      - flags.display.self
      - flags.set.self.drop
      players: []
extended-configuration: true
load-plugins: []
commands:
  vantell:
    log: false
    mirror: true
    aliases: []
  vanish:
    aliases:
    - svanish
    - svan
  reappear:
    aliases:
    - srea
  tvanish:
    aliases:
    - stvanish
    - stvan
  simplyvanish:
    aliases: []
  vanished:
    aliases: []
  vanflag:
    aliases: []
  vanpeek:
    aliases: []
inventories:
  allow-real-peek: true
flag-sets:
  cc: +cmd +chat
  cl: '*clear'
  act: +damage +attack +target +interact +pickup +drop
</code>
==== UltraHardCore ====
[http://masa.dy.fi/minecraft/configs/bukkit/plugins/UltraHardCore_config.yml config.yml]
<code javascript n>
hideFoodBar:
  enabled: false
  number: 5
  worlds:
  - uhc_1
  - uhc_2
cancelRegen:
  enabled: true
  worlds:
  - uhc_1
  - uhc_2
deathMessage:
  enabled: true
  worlds:
  - uhc_1
  - uhc_2
playerListHealth:
  enabled: true
transmitDamage:
  enabled: true
  maxticks: 20
  worlds:
  - uhc_1
  - uhc_2
forceHardMode:
  enabled: true
  worlds:
  - uhc_1
  - uhc_2
removeRecipies:
  removeGoldenApple: true
  removeGlisteringMelon: true
addRecipies:
  addGoldenApple:
    enabled: true
  addGlisteringMelon:
    enabled: true
kickBan:
  enabled: true
  message: You died! Bad luck.
  worlds:
  - uhc_1
  - uhc_2
randomFirstSpawn:
  enabled: true
  minradius: 0
  minradiusplayer: 100
  center:
    enabled: false
    x: 0
    z: 0
  radius: 500
  circle: true
  allowedBlocks:
    enabled: true
    IDs:
    - 1
    - 2
    - 3
    - 12
    - 13
    - 78
    - 79
initialItems:
  enabled: true
  itemIDs: 35-3&4,5-3
boundaries:
  ticker: 1
  worlds:
    world:
      enabled: true
      radius: 800
      circle: true
      center:
        overrideCenter: false
        x: 0
        z: 0
    world_nether:
      enabled: false
      radius: 100
      circle: true
      center:
        overrideCenter: false
        x: 0
        z: 0
    world_the_end:
      enabled: false
      radius: 800
      circle: true
      center:
        overrideCenter: false
        x: 0
        z: 0
    uhc_1:
      enabled: true
      radius: 1000
      circle: false
      center:
        overrideCenter: false
        x: 0
        z: 0
    uhc_2:
      enabled: false
      radius: 1000
      circle: true
      center:
        overrideCenter: false
        x: 0
        z: 0
ticker:
  delayOnRespawn: 500
  delayOnJoin: 500
  initDelay: 20
  period: 20
portals:
  creationRadius: 14
  searchRadius: 128
teamsEnabled: false
teams:
  teamname1:
  - player1
  - player2
  - etc
  teamname2:
  - player3
  - player4
  - player5
localChat:
  enabled: false
  distance: 200
</code>
==== VanishNoPacket ====
[http://masa.dy.fi/minecraft/configs/bukkit/plugins/VanishNoPacket_config.yml config.yml]
<code javascript n>
#
# VanishNoPacket
#  A fine choice of invisibility for the discerning server administrator.
#  http://www.kitteh.org
#
#  See documentation for details:
#  http://dev.bukkit.org/server-mods/vanish/pages/configuration/
#
fakeannounce:
    automaticforsilentjoin: false
    join: '%p joined the game.'
    quit: '%p left the game.'
hooks:
    essentials: false
    dynmap: false
    JSONAPI: false
    spoutcraft: false
checkupdates: false
permissionsupdates:
    checkonworldchange: true
effects:
    lightning:
        count: 0
permtest: false
debug: false
configVersionDoNotTouch:
    SeriouslyThisWillEraseYourConfig: 4
</code>
</code>


==== WorldEdit ====
==== WorldEdit ====
Oletuskonffi.
Oletuskonffi(?).<br />
[http://masa.dy.fi/minecraft/configs/bukkit/plugins/WorldEdit_config.yml config.yml]


<code javascript n>
<code javascript n>
Rivi 235: Rivi 652:
no-op-permissions: false
no-op-permissions: false
debug: false
debug: false
</code>
===== Muistilappuja =====
<code>
18:02:20 <@dumptruckman> false means no one has it by default
18:02:26 <@dumptruckman> true means everyone has it by default
18:02:39 <@dumptruckman> not-op means non-ops have it by default
18:02:44 <@dumptruckman> and op means ops have it by default
18:03:03 < masa_> wait, what?
18:03:22 < masa_> are there such values for permissions?
18:05:43 < masa_> at least not in bpermissions i would think, since the nodes are given as "- node.node" for
                  positive or "- ^node.node" for negative
18:07:58 < masa_> ah great... now i can't build on my teleport wall, since it is near 0,0 :D
18:08:11 < masa_> gimme that OP back
18:10:16 < masa_> btw have any of you come across a minecraft backup tool that would use some sort of binary
                  diff of maybe even more specific kind of "minecraft-data-optimized" algorithms?
18:10:57 <@dumptruckman> masa_: those are the values as defined by super perms
18:11:05 <@dumptruckman> individual permission managers may vary
18:11:44 <@dumptruckman> but it's possible to set up permissions via permissions.yml in your server
                        directory on a binary basis
18:11:50 <@dumptruckman> ops and non-ops
18:12:14 <@dumptruckman> no concept there of per world or groups or per user
18:12:17 < masa_> oh, didn't know that
18:12:30 <@dumptruckman> you could for instance do
18:12:38 < masa_> "Welcome to bPermissions, a Superperms Manager for Bukkit!"
18:12:41 <@dumptruckman> mv.bypass.*:
18:12:41 <@dumptruckman>  default: false
18:12:45 <@dumptruckman> and if that doesn't work
18:12:56 <@dumptruckman> then something is wrong
18:13:09 < masa_> ok, thanks
18:13:12 <@dumptruckman> thing is, that's already how that permissions is set up
18:13:22 <@dumptruckman> so doing that should have no impact on anything
18:14:02 < masa_> i think i'll stick with the bpermissions stuff for now, that way they are kind of in the
                  same place and i don't forget there is stuff elsewhere
18:15:57 <@dumptruckman> masa_: for reference: http://wiki.bukkit.org/Permissions.yml
18:16:17 <@dumptruckman> permissions.yml allows you to create custom permissions
</code>
</code>

Nykyinen versio 31. heinäkuuta 2012 kello 17.18


Seuraavassa on listattu joitakin tärkeimpiä pluginien konffeja dualilla. Suurimmat muokkaukset on bPermissions pluginin konffeissa, koska ne tietysti määräävät kaikkien käyttäjien ryhmät, prefixit, käyttöoikeudet jne. sekä joidenkin pluginien kohdalla toiminnan, eli jos käyttäjällä on jokin permission node, niin plugin tekee tällöin automaattisesti jonkin toiminnon. Näihin kuuluvat mm. AdminCmd ja Vanish pluginit.

HUOM! Tällä sivulla listatut asetustiedostojen sisällöt voivat olla vanhoja, mutta code-tageja edeltävät linkit johtavat serverillä käytössä oleviin eli siis ajantasaisiin versioihin!

Joitakin juttuja muistilistassa:

  • Älä poista groupilta tai userilta wildcard permission nodea negatoimalla se! Se johtaa kaikkien kyseisten permissioneiden poistumiseen, vaikka halutut olisivat positiivisina määriteltyinä tuon jälkeen. Eli poista vaan koko rivi konffista.
  • plugins/bPermissions/ alla olevat users.yml ja groups.yml ovat esimerkkejä ja templaatteja uusille maailmoille. Käytössä olevat ovat konffit maailman mukaan nimetyissä hakemistoissa.
  • Poikkeuksena jos config.yml:ssä on use-global-files päällä

bPermissions Quick Howto:

These are the default commands in bPermissions

• "/permissions save" Use save after changing permissions with commands, otherwise they'll be overwritten when you reload permissions • "/permissions reload" Do this for your permission edits to take effect • "/permissions cleanup" This cleans out all empty users groups from your files. Any user with no permissions and simply in the default group • "/permissions backup" This backs up all of your permission files!

To do any of these commands, you need the bPermissions.admin permission node. You can shorten the "permissions" in these commands to "p", "bp", or "perm" . There are two stages to the command structure for changing group/user meta data/permissions in bPermissions.

Stage 1: Select which object you would like to edit.

example: /world World_Awesome example: /group Admin - this will create a group if it does not exist, or select an existing group with that name! example: /user HerpDerp

Stage 2: Change object as you wish, using this structure:

/OBJECT ACTION VALUE

User's available actions: addgroup, rmgroup, setgroup, addperm, rmperm, meta Group's available actions: addgroup, rmgroup, addperm, rmperm, meta World's available actions: mirror (mirrorto) (mirrorfrom)

  • note: Meta data's VALUE has two arguements, KEY and VALUE. See examples below.

User examples: example: /user rmgroup Admin This removes group "Admin" from the user selected previously. example: /user setgroup Noob This sets the user selected to group "Noob" example: /user rmperm some.node This removes node "some.node" from selected player example: /user meta prefix Herp This sets meta data "prefix" to "Herp" on selected player

Group examples: example: /group addgroup Member This makes the selected group inherit group "Member" example: /group addperm a.node This adds permission node "a.node" to the selected group. example: /group meta suffix Derp This adds suffix "Derp" to selected group.

If you use an object in a command, such as /world, /user, or /group, It will give you the currently selected object, EX: /world, would give the output of, "Currently selected world: yourworldnamehere"


Shorthands/one-liners:

To set codename_B to admin in all worlds /exec u:codename_B a:setgroup v:admin

To add the permission "bPermissions.admin" to the admin group in world "world" /exec g:admin a:addperm v:bPermissions.admin w:world

• u/g: selects the user/group and provides the name
• a: provides the action (addgroup/rmgroup/setgroup/addperm/rmperm)
• v: provides the value (ie. WHAT you are adding/removing/setting)
• w: provides the world (optional, leave blank to apply to all worlds) 

AdminCmd

Ei vissiin merkittäviä muutoksia oletuksesta, paitsi:

editSignRightClick: false

Ilman tuon disablointia kylttejä ei pysty asettamaan toisen kyltin päälle...

Ja pikkukorjaukset itse käyttämieni tagien ja väritysten takia (vai hetkonen korjasinko tuon users.yml/groups.yml prefixistä?? Voi olla että muokkasin tämän kohdan silti...): AdminCmd/locales/en_US.yml: gmSwitch: '§aGameMode for %player §aswitched to : §f%gamemode'

config.yml
motd.txt
motdNewUser.txt
news.txt
rules.txt

bChatmanager

Pieniä muutoksia oletuskonffin viestien muotoiluun.
config.yml

formats:

   display-name-format: '%player'
   message-format: '[%world] %prefix%player&f: %message'
   local-message-format: '[LOCAL] %prefix%player&f: %message'
   personal-message-format: '[FROM] %prefix%player &f---> %message'
   alert-format: '&c[ALERT] &f%message'
   me-format: '* %player %message'

toggles:

   control-me: true
   ranged-mode: false

other:

   chat-range: 100.0

bPermissions

Yleiset asetukset: config.yml
Asetusten peilaus/kopiointi jostakin maailmasta toisiin maailmoihin: mirrors.yml
Käyttäjäkohtaiset oikeudet: users.yml

config.yml: auto-save: true track-type: single debug-mode: false allow-offline-mode: false use-global-files: false

mirros.yml esimerkki: world_nether: world world_end: world worlds/dirt62: world worlds/end_empty: world worlds/flat62: world worlds/stone62: world

tracks.yml (mikäli trackseja haluaisi käyttää, meidän pienellä servulla/käyttäjämäärällä ei ole tarpeen): default: - default - User - Moderator - Admin

users.yml (esimerkki): users:

 asdfas_rv:
   permissions: []
   groups:
   - user
 chestbursted:
   permissions: []
   groups:
   - user
 flotari:
   permissions: []
   groups:
   - user
 lanxu:
   permissions: []
   groups:
   - moderator
 masa_:
   permissions: []
   groups:
   - admin
   meta:
     priority: '50'
     prefix: '&f[&dOwner&f] '

groups.yml sisältääkin sitten varsinaiset oikeuksien määritykset. Se on vielä tällä hetkellä vähän niinkuin TODO :p

CleanroomGenerator

Vain maailmageneraattori plugin, ei asetustiedostoja.

HawkEye

HUOM! Ohessa vain muokatut kohdat (log:n alla kaikki kohdat true arvossa, en muista oliko jokin muu kuin flow:t oletuksena false): Ja en tietenkään tänne laita tietokannan tunnuksia...

log:

 water-flow: true
 lava-flow: true

general:

 log-item-drops-on-death: true
 cleanse-period: 20h
 delete-data-on-rollback: false
 give-user-tool: false

MinecraftBot

Eipä mitään ihmeempiä, servu, nick, kanava ja muotoilut kuntoon.
config.yml

MobDisguise

Oletuskonffi.
config.yml

Multiverse-Core

Oletuskonffi(?).
config.yml

  1. ------------------------------------------------------------------------- #
  2. This is the MV2 Config. If you mess it up, copy the values out #
  3. delete it, and it will be regenerated. Then use the ingame interface #
  4. to add your values back via the "/mv conf" command. #
  5. When in-game, simply type: "/mv conf ?" for help. #
  6. A config with explanations can be found here: #
  7. https://github.com/Multiverse/Multiverse-Core/wiki/config.yml #
  8. #
  9. #
  10. IMPORTANT !! IMPORTANT !! IMPORTANT !! IMPORTANT !! IMPORTANT !!IMPORTANT #
  11. #
  12. Do NOT delete this line from your config!!!! #
  13. ==: com.onarandombox.MultiverseCore.MultiverseCoreConfiguration #
  14. #
  15. IMPORTANT !! IMPORTANT !! IMPORTANT !! IMPORTANT !! IMPORTANT !!IMPORTANT #
  16. ------------------------------------------------------------------------- #

multiverse-configuration:

 ==: com.onarandombox.MultiverseCore.MultiverseCoreConfiguration
 enforceaccess: 'true'
 prefixchat: 'true'
 teleportintercept: 'true'
 firstspawnoverride: 'false'
 displaypermerrors: 'true'
 globaldebug: '0'
 messagecooldown: '5000'
 version: '2.9'
 firstspawnworld: world
 teleportcooldown: '1000'


Multiverse-Inventories

Lisätty last_location asetus, jotta pelaajien viimeisin sijainti joka maailmassa säilyy.
config.yml

  1. Multiverse-Inventories Settings
  1. ===[ Multiverse Inventories Config ]===

settings:

 # This is the locale you wish to use.
 locale: en
 # Level of debugging information to display.
 # 0 = off, 1-3 increasing amount of debug spam.
 debug_level: 0
 # If this is true it will generate world groups for you based on MV worlds.
 first_run: false
 # If this is set to true, it will enable bypass permissions (Check the wiki for more info.)
 use_bypass: false
 # If set to true, any world not listed in a group will automatically use the settings for the default group!
 default_ungrouped_worlds: false
 # If this is set to true, players will have different inventories/stats for each game mode.
 # Please note that old data migrated to the version that has this feature will have their data copied for both game modes.
 use_game_mode_profiles: false

shares:

 # You must specify optional shares you wish to use here or they will be ignored.
 # The only built in optional share is "economy"
 use_optionals:
 - last_location

groups: {}

Esimerkkikonffi groups.yml:stä, riippuu miten maailmat halutaan ryhmitellä!
groups.yml

Multiverse-NetherPortals

Ei tarvitse käsin muokata konffitiedostoja, sisältö on vain portaalien linkkaukset, jotka hoituvat komennoin in-game.

Multiverse-Portals

Oletuskonffi(?).
config.yml

  1. This is the MV-Portals Config. If you mess it up, copy the values out
  2. delete it, and it will be regenerated. Then use the ingame interface
  3. to add your values back via the "/mvp conf" command.
  4. When in-game, simply type: "/mvp conf ?" for help.
  5. A config with explanations can be found here:
  6. https://github.com/Multiverse/Multiverse-Portals/wiki/config.yml

wand: 290 useonmove: true portalsdefaulttonether: true enforceportalaccess: true portalcooldown: 1000 clearonremove: true teleportvehicles: true framematerials: [] version: 2.7

Multiverse-SignPortals

Ei konffitiedostoja.

OpenInv

Oletuskonffi:

ItemOpenInvItemID: 280

SimplyVanish

config.yml

flags:

 bypass:
   blocks:
   - '23'
   - '54'
   - '61'
   - '62'
   - '58'
   - '116'
   - '117'
   - '118'
   entities:
   - MINECART
   ignore-permissions: true
 cmd:
   whitelist: false
   commands:
   - me
   - tell
   - vantell
   - tellvan

pickup:

 exp:
   workaround:
     enabled: true
     distance:
       threshold: 3.0
       teleport: 1.0
       remove: 0.5
     velocity: 0.3

messages:

 suppress:
   join: false
   quit: false
 fake:
   enabled: false
   join: '&e%name joined the game.'
   quit: '&e%name left the game.'
 notify:
   state:
     enabled: false
     permission: simplyvanish.see-all
   ping:
     enabled: false
     period: 30

save:

 enabled: true
 always: true
 interval: 0
 delay: 10

auto-vanish:

 use: true
 permission: simplyvanish.auto-vanish

no-abort: false permissions:

 allow-ops: false
 superperms: true
 fake-permissions:
   set1:
     permissions:
     - all
     players: []
   set2:
     permissions:
     - vanish.self
     - reappear.self
     - flags.display.self
     - flags.set.self.drop
     players: []

extended-configuration: true load-plugins: [] commands:

 vantell:
   log: false
   mirror: true
   aliases: []
 vanish:
   aliases:
   - svanish
   - svan
 reappear:
   aliases:
   - srea
 tvanish:
   aliases:
   - stvanish
   - stvan
 simplyvanish:
   aliases: []
 vanished:
   aliases: []
 vanflag:
   aliases: []
 vanpeek:
   aliases: []

inventories:

 allow-real-peek: true

flag-sets:

 cc: +cmd +chat
 cl: '*clear'
 act: +damage +attack +target +interact +pickup +drop

UltraHardCore

config.yml

hideFoodBar:

 enabled: false
 number: 5
 worlds:
 - uhc_1
 - uhc_2

cancelRegen:

 enabled: true
 worlds:
 - uhc_1
 - uhc_2

deathMessage:

 enabled: true
 worlds:
 - uhc_1
 - uhc_2

playerListHealth:

 enabled: true

transmitDamage:

 enabled: true
 maxticks: 20
 worlds:
 - uhc_1
 - uhc_2

forceHardMode:

 enabled: true
 worlds:
 - uhc_1
 - uhc_2

removeRecipies:

 removeGoldenApple: true
 removeGlisteringMelon: true

addRecipies:

 addGoldenApple:
   enabled: true
 addGlisteringMelon:
   enabled: true

kickBan:

 enabled: true
 message: You died! Bad luck.
 worlds:
 - uhc_1
 - uhc_2

randomFirstSpawn:

 enabled: true
 minradius: 0
 minradiusplayer: 100
 center:
   enabled: false
   x: 0
   z: 0
 radius: 500
 circle: true
 allowedBlocks:
   enabled: true
   IDs:
   - 1
   - 2
   - 3
   - 12
   - 13
   - 78
   - 79

initialItems:

 enabled: true
 itemIDs: 35-3&4,5-3

boundaries:

 ticker: 1
 worlds:
   world:
     enabled: true
     radius: 800
     circle: true
     center:
       overrideCenter: false
       x: 0
       z: 0
   world_nether:
     enabled: false
     radius: 100
     circle: true
     center:
       overrideCenter: false
       x: 0
       z: 0
   world_the_end:
     enabled: false
     radius: 800
     circle: true
     center:
       overrideCenter: false
       x: 0
       z: 0
   uhc_1:
     enabled: true
     radius: 1000
     circle: false
     center:
       overrideCenter: false
       x: 0
       z: 0
   uhc_2:
     enabled: false
     radius: 1000
     circle: true
     center:
       overrideCenter: false
       x: 0
       z: 0

ticker:

 delayOnRespawn: 500
 delayOnJoin: 500
 initDelay: 20
 period: 20

portals:

 creationRadius: 14
 searchRadius: 128

teamsEnabled: false teams:

 teamname1:
 - player1
 - player2
 - etc
 teamname2:
 - player3
 - player4
 - player5

localChat:

 enabled: false
 distance: 200

VanishNoPacket

config.yml

  1. VanishNoPacket
  2. A fine choice of invisibility for the discerning server administrator.
  3. http://www.kitteh.org
  4. See documentation for details:
  5. http://dev.bukkit.org/server-mods/vanish/pages/configuration/

fakeannounce:

   automaticforsilentjoin: false
   join: '%p joined the game.'
   quit: '%p left the game.'

hooks:

   essentials: false
   dynmap: false
   JSONAPI: false
   spoutcraft: false

checkupdates: false permissionsupdates:

   checkonworldchange: true

effects:

   lightning:
       count: 0

permtest: false debug: false configVersionDoNotTouch:

   SeriouslyThisWillEraseYourConfig: 4

WorldEdit

Oletuskonffi(?).
config.yml

  1. WorldEdit's configuration file
  2. About editing this file:
  3. - DO NOT USE TABS. You MUST use spaces or Bukkit will complain. If
  4. you use an editor like Notepad++ (recommended for Windows users), you
  5. must configure it to "replace tabs with spaces." In Notepad++, this can
  6. be changed in Settings > Preferences > Language Menu.
  7. - Don't get rid of the indents. They are indented so some entries are
  8. in categories (like "max-blocks-changed" is in the "limits"
  9. category.
  10. - If you want to check the format of this file before putting it
  11. into WorldEdit, paste it into http://yaml-online-parser.appspot.com/
  12. and see if it gives "ERROR:".
  13. - Lines starting with # are commentsand so they are ignored.

limits:

   max-blocks-changed:
       default: -1
       maximum: -1
   max-radius: -1
   max-super-pickaxe-size: 5
   max-brush-radius: 5
   disallowed-blocks: [6, 7, 14, 15, 16, 26, 27, 28, 29, 39, 31, 32, 33, 34, 36, 37, 38, 39, 40, 46, 50, 51, 56, 59, 69, 73, 74, 75, 76, 77, 81, 83]

use-inventory:

   enable: false
   allow-override: true

logging:

   log-commands: true
   file: worldedit.log

super-pickaxe:

   drop-items: true
   many-drop-items: false

snapshots:

   directory:

navigation-wand:

   item: 345
   max-distance: 100

scripting:

   timeout: 3000
   dir: craftscripts

saving:

   dir: schematics

history:

   size: 15
   expiration: 10

butcher:

      butcher-default-radius: -1

wand-item: 271 shell-save-type: no-double-slash: false no-op-permissions: false debug: false

Muistilappuja

18:02:20 <@dumptruckman> false means no one has it by default 18:02:26 <@dumptruckman> true means everyone has it by default 18:02:39 <@dumptruckman> not-op means non-ops have it by default 18:02:44 <@dumptruckman> and op means ops have it by default 18:03:03 < masa_> wait, what? 18:03:22 < masa_> are there such values for permissions? 18:05:43 < masa_> at least not in bpermissions i would think, since the nodes are given as "- node.node" for

                 positive or "- ^node.node" for negative

18:07:58 < masa_> ah great... now i can't build on my teleport wall, since it is near 0,0 :D 18:08:11 < masa_> gimme that OP back 18:10:16 < masa_> btw have any of you come across a minecraft backup tool that would use some sort of binary

                 diff of maybe even more specific kind of "minecraft-data-optimized" algorithms?

18:10:57 <@dumptruckman> masa_: those are the values as defined by super perms 18:11:05 <@dumptruckman> individual permission managers may vary 18:11:44 <@dumptruckman> but it's possible to set up permissions via permissions.yml in your server

                        directory on a binary basis

18:11:50 <@dumptruckman> ops and non-ops 18:12:14 <@dumptruckman> no concept there of per world or groups or per user 18:12:17 < masa_> oh, didn't know that 18:12:30 <@dumptruckman> you could for instance do 18:12:38 < masa_> "Welcome to bPermissions, a Superperms Manager for Bukkit!" 18:12:41 <@dumptruckman> mv.bypass.*: 18:12:41 <@dumptruckman> default: false 18:12:45 <@dumptruckman> and if that doesn't work 18:12:56 <@dumptruckman> then something is wrong 18:13:09 < masa_> ok, thanks 18:13:12 <@dumptruckman> thing is, that's already how that permissions is set up 18:13:22 <@dumptruckman> so doing that should have no impact on anything 18:14:02 < masa_> i think i'll stick with the bpermissions stuff for now, that way they are kind of in the

                 same place and i don't forget there is stuff elsewhere

18:15:57 <@dumptruckman> masa_: for reference: http://wiki.bukkit.org/Permissions.yml 18:16:17 <@dumptruckman> permissions.yml allows you to create custom permissions