Fly na działce

Pomidor | 2021-05-27 21:53:27 UTC | #1

Witam, znowu ja z kolejnym błędem :(. A mianowicie graczom nie działa fly na działce po powrocie z netheru bezpośrednio na działkę. Ma ktoś jakis pomysł czemu tak jest? Plugin od działek to protectionstones

igoyek | 2021-05-28 22:08:17 UTC | #2

Z twojego opisu nic nie wynika.
Podeślij jakieś logi z konsoli, pliki konfiguracyjne z wtyczek typu Essentials lub tej wtyczki na system działek.
Nikt nie będzie w stanie Ci pomóc po twoim opisie, chyba że miał taki problem kiedyś i się dokładnie o co chodzi. Staraj się pisać staranniej posty, żeby ułatwić innym pracę 😜

Pomidor | 2021-05-29 12:02:06 UTC | #3

z logów nic nie wynika o tym pluginie

a tu config działek

type = “JUKEBOX”

Another way to refer to the protection stone

Can be used for /ps give and /ps get

Must be one word (no spaces)

alias = “1”

Description of the protection block type

Shows up in /ps get menu

description = “50x50”

Whether or not to restrict obtaining of the protection stone to only /ps get and /ps give and custom crafting recipes.

Other ways to obtain this block (ex. mining) will not work as a protection stone.

Useful to allow the protection block to only be obtained from a shop or command.

Set to “false” if you want to allow players to obtain a protection stone naturally

restrict_obtaining = true

Enable or disable the use of this protection stone in specific worlds

“blacklist” mode prevents this protect block from being used in the worlds in “worlds”

“whitelist” mode allows this protect block to only be used in the worlds in “worlds”

Can be overriden with protectionstones.admin permission (including OP)!

worldlisttype = “blacklist”
worlds = [
“worldnether”,
“worldend”
]

Whether or not to actually restrict the protection stone from being placed when the world is restricted (in blacklist/whitelist)

The block will place normally, without PS behaviour.

preventblockplaceinrestricted_world = true

Whether or not to allow the block to be placed in the wild.

If set to false, the protection block can only be placed in existing regions.

allowplacingin_wild = true

[region]
# Minimum distance between claims (that aren’t owned by the same owner), measured from the protection block to the edge of another region
# You will probably have to change this between blocks, since the region sizes will be different
# Set to -1 for no minimum, but will still check for overlapping regions
distancebetweenclaims = -1

# Protection radius of block (radius of 64 -> 129 x 129 region)
# Set y_radius to -1 if you want it to protect from sky to bedrock. If this doesn't appear to work set it to 256.
# y_radius must be -1 if you are allowing the region to be merged ("allow_merging" option)
x_radius = 25
y_radius = -1
z_radius = 25

# Offset the protection block
# If you would like to make the protection block not be at the center of new regions, you can offset it here
# ex. x_offset = 64, y_offset = 0, z_offset = 64 would make it at the corner of a created region
x_offset = 0
y_offset = 0
z_offset = 0

# How many blocks to offset the default location of /ps home from the protection block
home_x_offset = 0.0
home_y_offset = 1.0
home_z_offset = 0.0

# Specify the default flags to be set when a new protected region is created.
# Can use -g [group] before the flag to set group flags (ex. -g members pvp deny).
# Can use PlaceholderAPI placeholders in string flags (ex. greeting, farewell).
flags = [
    "pvp deny",
    "tnt deny",
    "greeting &f&lWchodzisz  na dzialke gracza &c&l%player%",
    "farewell &f&lWychodzisz z dzialki gracza &c&l%player%",
    "creeper-explosion deny",
]

# List all the flags that can be set by region owners.
# If you want to whitelist the groups that can be set as well, use -g (ex. "-g all,members pvp" restricts it to no group flag, and members group)
# "-g all pvp" - Prevents players setting the group to nonmembers, and being invulnerable to attacks.
allowed_flags = [

“-g all fly”,
“-g all entry”,
“-g members use”,
]

# Which flags to hide from /ps info
hidden_flags_from_info = [
    "ps-merged-regions",
    "ps-merged-regions-types",
    "ps-block-material",
    "ps-price",
    "ps-landlord",
    "ps-tenant",
    "ps-rent-period",
    "ps-rent-last-paid",
    "ps-for-sale",
    "ps-rent-settings",
    "ps-tax-payments-due",
    "ps-tax-last-payment-added",
    "ps-tax-autopayer"
]

# Default priority type for this block type protection stone
priority = 0

# Whether or not to allow creation of regions that overlap other regions you don't own
# This is dangerous, so think about this carefully if you set it to true.
allow_overlap_unowned_regions = false

# Whether or not to allow players to create other regions that overlap this region.
# "owner" - only allow owners to overlap this (default)
# "member" - allow members and owners to overlap this region type. (useful for city plots)
# "all" - allow all players to overlap this region type.
# "none" - no players, not even the owners of the region can overlap it
# allow_overlap_unowned_regions does not need to be true for this to work.
allow_other_regions_to_overlap = "owner"

# Whether or not to allow this regions created with this block to merge with other regions
# allow_merging_regions must be set to true in config.toml
allow_merging = true

# Allowed types of regions to merge into (referred to by alias)
# Be sure to add the alias of this current region type to allow merging with it ex. ["64"]
# Add "all" if you want to allow this region to merge into any region
allowed_merging_into_types = [
    "all"
]

system | 2021-06-30 12:02:54 UTC | #4

Ten temat został automatycznie zamknięty 32 dni po ostatnim wpisie. Tworzenie nowych odpowiedzi nie jest już możliwe.