Stack d'items moddés avec Essentials

[PlayFlop_]

Bonjour,

J’ai un souci avec éssentials.
quand je fait un kit, sa stack les armures, épées et tout moddé…
Quelqu’un aurait une solution ?
J’ai même essaye le .setMaxStackSize(1) mais rien ne change…

merci

[Deleted]

Salut,
je pense qu’il faudrait ajouter plusieurs ItemStack de tes pièces pour le kit. En gros si tu fais un seul ItemStack d’une armure moddé, mais comportant un stackSize égale à 2, normal qu’elle viennent se mettre les deux dans le même slot, or si tu fais deux fois l’ItemStack de cette armure moddé, possédant pour les deux un stackSize de 1, selon moi, ton problème sera résolu.

[PlayFlop_]

@‘Plaigon’:

Salut,
je pense qu’il faudrait ajouter plusieurs ItemStack de tes pièces pour le kit. En gros si tu fais un seul ItemStack d’une armure moddé, mais comportant un stackSize égale à 2, normal qu’elle viennent se mettre les deux dans le même slot, or si tu fais deux fois l’ItemStack de cette armure moddé, possédant pour les deux un stackSize de 1, selon moi, ton problème sera résolu.

Comment ça je comprend pas trop…

[Deleted]

Qu’as-tu dans ton fichier yml ?

EDIT: pense à renommer le titre, ce n’est pas suffisamment fidèle à ton soucis.

[PlayFlop_]

@‘Plaigon’:

Qu’as-tu dans ton fichier yml ?

EDIT: pense à renommer le titre, ce n’est pas suffisamment fidèle à ton soucis.

J’ai ça:

############################################################
# +–----------------------------------------------------+ #
# |                       Notes                          | #
# +------------------------------------------------------+ #
############################################################
 
# If you want to use special characters in this document, such as accented letters, you MUST save the file as UTF-8, not ANSI.
# If you receive an error when Essentials loads, ensure that:
#   - No tabs are present: YAML only allows spaces
#   - Indents are correct: YAML hierarchy is based entirely on indentation
#   - You have "escaped" all apostrophes in your text: If you want to write "don't", for example, write "don''t" instead (note the doubled apostrophe)
#   - Text with symbols is enclosed in single or double quotation marks
 
# If you have problems join the Essentials help support channel: http://tiny.cc/EssentialsChat
 
############################################################
# +------------------------------------------------------+ #
# |                 Essentials (Global)                  | #
# +------------------------------------------------------+ #
############################################################
 
# A color code between 0-9 or a-f. Set to 'none' to disable.
ops-name-color: 'none'
 
# The character(s) to prefix all nicknames, so that you know they are not true usernames.
nickname-prefix: ''
 
# The maximum length allowed in nicknames. The nickname prefix is included in this.
max-nick-length: 15
 
# Disable this if you have any other plugin, that modifies the displayname of a user.
change-displayname: true
 
# When this option is enabled, the (tab) player list will be updated with the displayname.
# The value of change-displayname (above) has to be true.
#change-playerlist: true
 
# When EssentialsChat.jar isn't used, force essentials to add the prefix and suffix from permission plugins to displayname.
# This setting is ignored if EssentialsChat.jar is used, and defaults to 'true'.
# The value of change-displayname (above) has to be true.
# Do not edit this setting unless you know what you are doing!
#add-prefix-suffix: false
 
# If the teleport destination is unsafe, should players be teleported to the nearest safe location?
# If this is set to true, Essentials will attempt to teleport players close to the intended destination.
# If this is set to false, attempted teleports to unsafe locations will be cancelled with a warning.
teleport-safety: true
 
# The delay, in seconds, required between /home, /tp, etc.
teleport-cooldown: 5
 
# The delay, in seconds, before a user actually teleports.  If the user moves or gets attacked in this timeframe, the teleport never occurs.
teleport-delay: 5
 
# The delay, in seconds, a player can't be attacked by other players after they have been teleported by a command.
# This will also prevent the player attacking other players.
teleport-invulnerability: 2
 
# The delay, in seconds, required between /heal or /feed attempts.
heal-cooldown: 60
 
# What to prevent from /item and /give.
# e.g item-spawn-blacklist: 10,11,46
item-spawn-blacklist:
 
# Set this to true if you want permission based item spawn rules.
# Note: The blacklist above will be ignored then.
# Example permissions (these go in your permissions manager):
#  - essentials.itemspawn.item-all
#  - essentials.itemspawn.item-[itemname]
#  - essentials.itemspawn.item-[itemid]
#  - essentials.give.item-all
#  - essentials.give.item-[itemname]
#  - essentials.give.item-[itemid]
#  - essentials.unlimited.item-all
#  - essentials.unlimited.item-[itemname]
#  - essentials.unlimited.item-[itemid]
#  - essentials.unlimited.item-bucket # Unlimited liquid placing
#
# For more information, visit http://wiki.ess3.net/wiki/Command_Reference/ICheat#Item.2FGive
permission-based-item-spawn: false
 
# Mob limit on the /spawnmob command per execution.
spawnmob-limit: 10
 
# Shall we notify users when using /lightning?
warn-on-smite: true
 
# The motd and rules are now configured in the files motd.txt and rules.txt.
 
# When a command conflicts with another plugin, by default, Essentials will try to force the OTHER plugin to take priority.
# Commands in this list, will tell Essentials to 'not give up' the command to other plugins.
# In this state, which plugin 'wins' appears to be almost random.
#
# If you have two plugin with the same command and you wish to force Essentials to take over, you need an alias.
# To force essentials to take 'god' alias 'god' to 'egod'.
# See http://wiki.bukkit.org/Commands.yml#aliases for more information.
 
overridden-commands:
#  - god
#  - info
 
# Disabling commands here will prevent Essentials handling the command, this will not affect command conflicts.
# You should not have to disable commands used in other plugins, they will automatically get priority.
# See http://wiki.bukkit.org/Commands.yml#aliases to map commands to other plugins.
disabled-commands:
#  - nick
#  - clear
 
# These commands will be shown to players with socialSpy enabled.
# You can add commands from other plugins you may want to track or
# remove commands that are used for something you dont want to spy on.
# Set - '*' in order to listen on all possible commands.
socialspy-commands:
  - msg
  - w
  - r
  - mail
  - m
  - t
  - whisper
  - emsg
  - tell
  - er
  - reply
  - ereply
  - email
  - action
  - describe
  - eme
  - eaction
  - edescribe
  - etell
  - ewhisper
  - pm
 
# If you do not wish to use a permission system, you can define a list of 'player perms' below.
# This list has no effect if you are using a supported permissions system.
# If you are using an unsupported permissions system, simply delete this section.
# Whitelist the commands and permissions you wish to give players by default (everything else is op only).
# These are the permissions without the "essentials." part.
player-commands:
  - afk
  - afk.auto
  - back
  - back.ondeath
  - balance
  - balance.others
  - balancetop
  - build
  - chat.color
  - chat.format
  - chat.shout
  - chat.question
  - clearinventory
  - compass
  - depth
  - delhome
  - getpos
  - geoip.show
  - help
  - helpop
  - home
  - home.others
  - ignore
  - info
  - itemdb
  - kit
  - kits.tools
  - list
  - mail
  - mail.send
  - me
  - motd
  - msg
  - msg.color
  - nick
  - near
  - pay
  - ping
  - protect
  - r
  - rules
  - realname
  - seen
  - sell
  - sethome
  - setxmpp
  - signs.create.protection
  - signs.create.trade
  - signs.break.protection
  - signs.break.trade
  - signs.use.balance
  - signs.use.buy
  - signs.use.disposal
  - signs.use.enchant
  - signs.use.free
  - signs.use.gamemode
  - signs.use.heal
  - signs.use.info
  - signs.use.kit
  - signs.use.mail
  - signs.use.protection
  - signs.use.repair
  - signs.use.sell
  - signs.use.time
  - signs.use.trade
  - signs.use.warp
  - signs.use.weather
  - spawn
  - suicide
  - time
  - tpa
  - tpaccept
  - tpahere
  - tpdeny
  - warp
  - warp.list
  - world
  - worth
  - xmpp
 
# Note: All items MUST be followed by a quantity!
# All kit names should be lower case, and will be treated as lower in permissions/costs.
# Syntax: - itemID[:DataValue/Durability] Amount [Enchantment:Level].. [itemmeta:value]…
# For Item Meta information visit http://wiki.ess3.net/wiki/Item_Meta
# 'delay' refers to the cooldown between how often you can use each kit, measured in seconds.
# Set delay to -1 for a one time kit.
# For more information, visit http://wiki.ess3.net/wiki/Kits
kits:
  Extane:
    delay: 600
    items:
      - 4105 1 protection:4
      - 4106 1 protection:4
      - 4107 1 protection:4
      - 4108 1 protection:4
      - 4121 1 sharpness:5
  Aragonite:
    delay: 600
    items:
      - 4109 1 protection:4
      - 4110 1 protection:4
      - 4111 1 protection:4
      - 4112 1 protection:4
      - 4126 1 sharpness:5
  Minozite:
    delay: 600
    items:
      - 4113 1 protection:4
      - 4114 1 protection:4
      - 4115 1 protection:4
      - 4116 1 protection:4
      - 4131 1 sharpness:5
  Obsidienne:
    delay: 600
    items:
      - 4117 1 protection:4
      - 4118 1 protection:4
      - 4119 1 protection:4
      - 4120 1 protection:4
      - 4136 1 sharpness:5
  start:
    delay: 10800
    items:
      - 4117 1 protection:1
      - 311 1 protection:1
      - 312 1 protection:1
      - 4120 1 protection:1
      - 4136 1 sharpness:1
      - 364 16
      - 4137 1 efficiency:1
      - 4138 1 efficiency:1
      - 4139 1 efficiency:1
  baron:
    delay: 10800
    items:
      - 4113 1 protection:1
      - 4118 1 protection:1
      - 4119 1 protection:1
      - 4116 1 protection:1
      - 4131 1 sharpness:1
      - 364 16
      - 4132 1 efficiency:1
      - 4133 1 efficiency:1
      - 4134 1 efficiency:1
      - 322 8
      - 368 4
  templier:
    delay: 10800
    items:
      - 4109 1 protection:1
      - 4114 1 protection:1
      - 4115 1 protection:1
      - 4112 1 protection:1
      - 4126 1 sharpness:2
      - 364 16
      - 4127 1 efficiency:2
      - 4128 1 efficiency:2
      - 4129 1 efficiency:2
      - 322 12
      - 368 8
  empereur:
    delay: 10800
    items:
      - 4109 1 protection:2
      - 4110 1 protection:1
      - 4111 1 protection:1
      - 4112 1 protection:2
      - 4126 1 sharpness:3
      - 364 16
      - 4127 1 efficiency:3
      - 4128 1 efficiency:3
      - 4129 1 efficiency:3
      - 322 16
      - 368 12
  staff:
    delay: 10800
    items:
      - 345 1
  pvp:
    delay: 10800
    items:
      - 4109 1 protection:1
      - 4114 1 protection:1
      - 4115 1 protection:1
      - 4112 1 protection:1
      - 4126 1 sharpness:2
      - 364 16
      - 4127 1 efficiency:2
      - 4128 1 efficiency:2
      - 4129 1 efficiency:2
      - 322 12
      - 368 8
      - 373.8226 3
      - 373.16425 2
      - 373.8259 2
      - 373.16421 7
      - 373.16452 2
      - 373.8269 1
      - 373.16458 2
  alchimiste:
    delay: 10800
    items:
      - 373.8226 3
      - 373.16425 2
      - 373.8259 2
      - 373.16421 7
      - 373.16452 2
      - 373.8269 1
      - 373.16458 2
  construction:
    delay: 10800
    items:
      - 1 64
      - 17 64
      - 17.1 64
      - 17.2 64
      - 17.3 64
      - 49 32
      - 159 64
  redstone:
    delay: 10800
    items:
      - 46 32
      - 29 8
      - 33 8
      - 23 4
      - 158 4
      - 331 64
      - 76 4
      - 356 16
      - 154 8
  druide:
    delay: 10800
    items:
      - 372 16
      - 382 8
      - 378 8
      - 376 4
      - 375 4
      - 369 4
      - 289 8
      - 348 16
      - 379 2
  minerais:
    delay: 10800
    items:
      - 264 4
      - 265 16
      - 266 8
      - 263 32
      - 388 8
      - 4100 8
      - 4099 4
      - 4098 2
      - 4097 1
  base:
    delay: 10800
    items:
      - 49 64
      - 49 64
 
# Essentials Sign Control
# See http://wiki.ess3.net/wiki/Sign_Tutorial for instructions on how to use these.
# To enable signs, remove # symbol. To disable all signs, comment/remove each sign.
# Essentials colored sign support will be enabled when any sign types are enabled.
# Color is not an actual sign, it's for enabling using color codes on signs, when the correct permissions are given.
 
enabledSigns:
  #- color
  #- balance
  #- buy
  #- sell
  #- trade
  #- free
  #- disposal
  #- warp
  #- kit
  #- mail
  #- enchant
  #- gamemode
  #- heal
  #- info
  #- spawnmob
  #- repair
  #- time
  #- weather
 
# How many times per second can Essentials signs be interacted with per player.
# Values should be between 1-20, 20 being virtually no lag protection.
# Lower numbers will reduce the possibility of lag, but may annoy players.
sign-use-per-second: 4
 
# Backup runs a batch/bash command while saving is disabled.
backup:
  # Interval in minutes.
  interval: 30
  # Unless you add a valid backup command or script here, this feature will be useless.
  # Use 'save-all' to simply force regular world saving without backup.
  #command: 'rdiff-backup World1 backups/World1'
 
# Set this true to enable permission per warp.
per-warp-permission: false
 
# Sort output of /list command by groups.
# You can hide and merge the groups displayed in /list by defining the desired behaviour here.
# Detailed instructions and examples can be found on the wiki: http://wiki.ess3.net/wiki/List
list:
    # To merge groups, list the groups you wish to merge
    #Staff: owner admin moderator
    Admins: owner admin
    # To limit groups, set a max user limit
    #builder: 20
    # To hide groups, set the group as hidden
    #default: hidden
    # Uncomment the line below to simply list all players with no grouping
    #Players: '*'
 
# More output to the console.
debug: false
 
# Set the locale for all messages.
# If you don't set this, the default locale of the server will be used.
# For example, to set language to English, set locale to en, to use the file "messages_en.properties".
# Don't forget to remove the # in front of the line.
# For more information, visit http://wiki.ess3.net/wiki/Locale
locale: fr
 
# Turn off god mode when people leave the server.
remove-god-on-disconnect: false
 
# Auto-AFK
# After this timeout in seconds, the user will be set as AFK.
# This feature requires the player to have essentials.afk.auto node.
# Set to -1 for no timeout.
auto-afk: 300
 
# Auto-AFK Kick
# After this timeout in seconds, the user will be kicked from the server.
# essentials.afk.kickexempt node overrides this feature.
# Set to -1 for no timeout.
auto-afk-kick: -1
 
# Set this to true, if you want to freeze the player, if the player is AFK.
# Other players or monsters can't push the player out of AFK mode then.
# This will also enable temporary god mode for the AFK player.
# The player has to use the command /afk to leave the AFK mode.
freeze-afk-players: false
 
# When the player is AFK, should he be able to pickup items?
# Enable this, when you don't want people idling in mob traps.
disable-item-pickup-while-afk: false
 
# This setting controls if a player is marked as active on interaction.
# When this setting is false, the player would need to manually un-AFK using the /afk command.
cancel-afk-on-interact: true
 
# Should we automatically remove afk status when a player moves?
# Player will be removed from AFK on chat/command regardless of this setting.
# Disable this to reduce server lag.
cancel-afk-on-move: true
 
# You can disable the death messages of Minecraft here.
death-messages: true
 
# Should players with permissions be able to join and part silently?
# You can control this with essentials.silentjoin and essentials.silentquit permissions if it is enabled.
# In addition, people with essentials.silentjoin.vanish will be vanished on join.
allow-silent-join-quit: false
 
# You can set a custom join message here, set to "none" to disable.
# You may use color codes, use {USERNAME} the player's name or {PLAYER} for the player's displayname.
custom-join-message: "none"
 
# You can set a custom quit message here, set to "none" to disable.
# You may use color codes, use {USERNAME} the player's name or {PLAYER} for the player's displayname.
custom-quit-message: "none"
 
# Add worlds to this list, if you want to automatically disable god mode there.
no-god-in-worlds:
#  - world_nether
 
# Set to true to enable per-world permissions for teleporting between worlds with essentials commands.
# This applies to /world, /back, /tp[a|o][here|all], but not warps.
# Give someone permission to teleport to a world with essentials.worlds. <worldname># This does not affect the /home command, there is a separate toggle below for this.
world-teleport-permissions: false
 
# The number of items given if the quantity parameter is left out in /item or /give.
# If this number is below 1, the maximum stack size size is given. If over-sized stacks.
# are not enabled, any number higher than the maximum stack size results in more than one stack.
default-stack-size: 1
 
# Over-sized stacks are stacks that ignore the normal max stack size.
# They can be obtained using /give and /item, if the player has essentials.oversizedstacks permission.
# How many items should be in an over-sized stack?
oversized-stacksize: 0
 
# Allow repair of enchanted weapons and armor.
# If you set this to false, you can still allow it for certain players using the permission.
# essentials.repair.enchanted
repair-enchanted: true
 
# Allow 'unsafe' enchantments in kits and item spawning.
# Warning: Mixing and overleveling some enchantments can cause issues with clients, servers and plugins.
unsafe-enchantments: false
 
#Do you want Essentials to keep track of previous location for /back in the teleport listener?
#If you set this to true any plugin that uses teleport will have the previous location registered.
register-back-in-listener: false
 
#Delay to wait before people can cause attack damage after logging in.
login-attack-delay: 5
 
#Set the max fly speed, values range from 0.1 to 1.0
max-fly-speed: 0.8
 
#Set the max walk speed, values range from 0.1 to 1.0
max-walk-speed: 0.8
 
#Set the maximum amount of mail that can be sent within a minute.
mails-per-minute: 1000
 
# Set the maximum time /tempban can be used for in seconds.
# Set to -1 to disable, and essentials.tempban.unlimited can be used to override.
max-tempban-time: -1
 
############################################################
# +–----------------------------------------------------+ #
# |                   EssentialsHome                     | #
# +------------------------------------------------------+ #
############################################################
 
# Allows people to set their bed at daytime.
update-bed-at-daytime: true
 
# Set to true to enable per-world permissions for using homes to teleport between worlds.
# This applies to the /home only.
# Give someone permission to teleport to a world with essentials.worlds. <worldname>world-home-permissions: false
 
# Allow players to have multiple homes.
# Players need essentials.sethome.multiple before they can have more than 1 home.
# You can set the default number of multiple homes using the 'default' rank below.
# To remove the home limit entirely, give people 'essentials.sethome.multiple.unlimited'.
# To grant different home amounts to different people, you need to define a 'home-rank' below.
# Create the 'home-rank' below, and give the matching permission: essentials.sethome.multiple. <home-rank># For more information, visit http://wiki.ess3.net/wiki/Multihome
sethome-multiple:
  2: 2
  3: 3
  4: 4
 
# In this example someone with 'essentials.sethome.multiple' and 'essentials.sethome.multiple.vip' will have 5 homes.
# Remember, they MUST have both permission nodes in order to be able to set multiple homes.
 
# Set the timeout, in seconds for players to accept a tpa before the request is cancelled.
# Set to 0 for no timeout.
tpa-accept-cancellation: 120
 
############################################################
# +------------------------------------------------------+ #
# |                   EssentialsEco                      | #
# +------------------------------------------------------+ #
############################################################
 
# For more information, visit http://wiki.ess3.net/wiki/Essentials_Economy
 
# Defines the balance with which new players begin. Defaults to 0.
starting-balance: 30
 
# worth-# defines the value of an item when it is sold to the server via /sell.
# These are now defined in worth.yml
 
# Defines the cost to use the given commands PER USE.
# Some commands like /repair have sub-costs, check the wiki for more information.
command-costs:
  # /example costs $1000 PER USE
  #example: 1000
  # /kit tools costs $1500 PER USE
  #kit-tools: 1500
 
# Set this to a currency symbol you want to use.
# Remember, if you want to use special characters in this document, 
# such as accented letters, you MUST save the file as UTF-8, not ANSI.
currency-symbol: '/home-rank>
 
# Set the maximum amount of money a player can have.
# The amount is always limited to 10 trillion because of the limitations of a java double.
max-money: 10000000000000
 
# Set the minimum amount of money a player can have (must be above the negative of max-money).
# Setting this to 0, will disable overdrafts/loans completely.  Users need 'essentials.eco.loan' perm to go below 0.
min-money: -10000
 
# Enable this to log all interactions with trade/buy/sell signs and sell command.
economy-log-enabled: false
 
############################################################
# +------------------------------------------------------+ #
# |                   EssentialsHelp                     | #
# +------------------------------------------------------+ #
############################################################
 
# Show other plugins commands in help.
non-ess-in-help: true
 
# Hide plugins which do not give a permission.
# You can override a true value here for a single plugin by adding a permission to a user/group.
# The individual permission is: essentials.help.<plugin>, anyone with essentials.* or '*' will see all help regardless.
# You can use negative permissions to remove access to just a single plugins help if the following is enabled.
hide-permissionless-help: true
 
############################################################
# +------------------------------------------------------+ #
# |                   EssentialsChat                     | #
# +------------------------------------------------------+ #
############################################################
 
# This section requires the EssentialsChat.jar to work.
 
chat:
 
  # If EssentialsChat is installed, this will define how far a player's voice travels, in blocks.  Set to 0 to make all chat global.
  # Note that users with the "essentials.chat.spy" permission will hear everything, regardless of this setting.
  # Users with essentials.chat.shout can override this by prefixing text with an exclamation mark (!)
  # Users with essentials.chat.question can override this by prefixing text with a question mark (?)
  # You can add command costs for shout/question by adding chat-shout and chat-question to the command costs section."
  radius: 0
 
  # Chat formatting can be done in two ways, you can either define a standard format for all chat.
  # Or you can give a group specific chat format, to give some extra variation.
  # For more information of chat formatting, check out the wiki: http://wiki.ess3.net/wiki/Chat_Formatting
 
  format:  '{&e%{faction.player.rank.%player%}% | %{faction.player.factionset.%player%}%&6} §r§7 §r{DISPLAYNAME}§r§7:§r {MESSAGE}'
  #format: '§7[{factions_roleprefix}§r§7{factions_nameforce}§r§7] §r§7[{GROUP}] §r{DISPLAYNAME}§r§7:§r {MESSAGE}'
 
  group-formats:
  #  Default: '{DISPLAYNAME}&7:&r {MESSAGE}'
  #  Admins: '[{GROUP}]§r§7{DISPLAYNAME}&7:&c {MESSAGE}'
 
  # If you are using group formats make sure to remove the '#' to allow the setting to be read.
 
############################################################
# +–----------------------------------------------------+ #
# |                 EssentialsProtect                    | #
# +------------------------------------------------------+ #
############################################################
 
# This section requires the EssentialsProtect.jar to work.
 
protect:
 
  # General physics/behavior modifications.
  prevent:
    lava-flow: false
    water-flow: false
    water-bucket-flow: false
    fire-spread: true
    lava-fire-spread: true
    flint-fire: false
    lightning-fire-spread: true
    portal-creation: false
    tnt-explosion: false
    tnt-playerdamage: false
    tnt-minecart-explosion: false
    tnt-minecart-playerdamage: false
    fireball-explosion: false
    fireball-fire: false
    fireball-playerdamage: false
    witherskull-explosion: false
    witherskull-playerdamage: false
    wither-spawnexplosion: false
    wither-blockreplace: false
    creeper-explosion: false
    creeper-playerdamage: false
    creeper-blockdamage: false
    enderdragon-blockdamage: true
    enderman-pickup: false
    villager-death: false
    # Monsters won't follow players.
    # permission essentials.protect.entitytarget.bypass disables this.
    entitytarget: false
    # Prevent the spawning of creatures.
    spawn:
      creeper: false
      skeleton: false
      spider: false
      giant: false
      zombie: false
      slime: false
      ghast: false
      pig_zombie: false
      enderman: false
      cave_spider: false
      silverfish: false
      blaze: false
      magma_cube: false
      ender_dragon: false
      pig: false
      sheep: false
      cow: false
      chicken: false
      squid: false
      wolf: false
      mushroom_cow: false
      snowman: false
      ocelot: false
      iron_golem: false
      villager: false
      wither: false
      bat: false
      witch: false
      horse: false
 
  # Maximum height the creeper should explode. -1 allows them to explode everywhere.
  # Set prevent.creeper-explosion to true, if you want to disable creeper explosions.
  creeper:
    max-height: -1
 
  # Disable various default physics and behaviors.
  disable:
    # Should fall damage be disabled?
    fall: false
 
    # Users with the essentials.protect.pvp permission will still be able to attack each other if this is set to true.
    # They will be unable to attack users without that same permission node.
    pvp: false
 
    # Should drowning damage be disabled?
    # (Split into two behaviors; generally, you want both set to the same value.)
    drown: false
    suffocate: false
 
    # Should damage via lava be disabled?  Items that fall into lava will still burn to a crisp. ;)
    lavadmg: false
 
    # Should arrow damage be disabled?
    projectiles: false
 
    # This will disable damage from touching cacti.
    contactdmg: false
 
    # Burn, baby, burn!  Should fire damage be disabled?
    firedmg: false
 
    # Should the damage after hit by a lightning be disabled?
    lightning: false
 
    # Should Wither damage be disabled?
    wither: false
 
    # Disable weather options?
    weather:
      storm: false
      thunder: false
      lightning: false
 
############################################################
# +------------------------------------------------------+ #
# |                EssentialsAntiBuild                   | #
# +------------------------------------------------------+ #
############################################################
 
  # This section requires the EssentialsAntiBuild.jar to work.
 
  # Disable various default physics and behaviors
  # For more information, visit http://wiki.ess3.net/wiki/AntiBuild
 
    # Should people with build: false in permissions be allowed to build?
    # Set true to disable building for those people.
    # Setting to false means EssentialsAntiBuild will never prevent you from building.
    build: true
 
    # Should people with build: false in permissions be allowed to use items?
    # Set true to disable using for those people.
    # Setting to false means EssentialsAntiBuild will never prevent you from using items.
    use: true
 
    # Should we tell people they are not allowed to build?
    warn-on-build-disallow: true
 
  # For which block types would you like to be alerted?
  # You can find a list of IDs in plugins/Essentials/items.csv after loading Essentials for the first time.
  # 10 = lava :: 11 = still lava :: 46 = TNT :: 327 = lava bucket
  alert:
    on-placement:
    on-use:
    on-break:
 
  blacklist:
 
    # Which blocks should people be prevented from placing?
    placement:
 
    # Which items should people be prevented from using?
    usage:
 
    # Which blocks should people be prevented from breaking?
    break:
 
    # Which blocks should not be pushed by pistons?
    piston:
 
    # Which blocks should not be dispensed by dispensers
    dispenser:
 
############################################################
# +------------------------------------------------------+ #
# |            Essentials Spawn / New Players            | #
# +------------------------------------------------------+ #
############################################################
 
# This section requires essentialsspawn.jar to work.
 
newbies:
  # Should we announce to the server when someone logs in for the first time?
  # If so, use this format, replacing {DISPLAYNAME} with the player name.
  # If not, set to ''
  #announce-format: ''
  announce-format: '&dBienvenue {DISPLAYNAME}&d sur Extania!'
 
  # When we spawn for the first time, which spawnpoint do we use?
  # Set to "none" if you want to use the spawn point of the world.
  spawnpoint: newbies
 
  # Do we want to give users anything on first join? Set to '' to disable
  # This kit will be given regardless of cost and permissions, and will not trigger the kit delay.
  #kit: ''
  kit: baron
 
# Set this to lowest, if you want Multiverse to handle the respawning.
# Set this to high, if you want EssentialsSpawn to handle the respawning.
# Set this to highest, if you want to force EssentialsSpawn to handle the respawning.
respawn-listener-priority: high
 
# When users die, should they respawn at their first home or bed, instead of the spawnpoint?
respawn-at-home: false
 
# End of file <-- No seriously, you're done with configuration.
 
```</plugin></home-rank></worldname></worldname>

[Deleted]

Où sont les lignes posant problème ?

[PlayFlop_]

@‘Plaigon’:

Où sont les lignes posant problème ?

Mais tu n’a pas comprit le souci, c’est que quand je fait /kit blabla (exemple)

En jeu sa me stack les objets moddé par 64 même les armures, épées et tout
Et je sais pas comment fixé ça

[Deleted]

J’ai très bien compris ton problème, relis mes messages, et réponds à ma question, à moins que tu ne souhaites pas recevoir de mon aide ?

[PlayFlop_]

@‘Plaigon’:

J’ai très bien compris ton problème, relis mes messages, et réponds à ma question, à moins que tu ne souhaites pas recevoir de mon aide ?

Mais comment je peut changé l’item stack de l’armure et des outils tout ça ?

Edit:

default-stack-size: 1 (De base a -1)
oversized-stacksize: 0 (De base a 64)
j’ai essayé de mettre a 1 et ça ne change rien

[Deleted]

Il faut que tes ItemStack d’armures/épées/outils moddées stackable d’origine par 1, contenus dans ton fichier .yml du plugin, soient enregistrés avec un stackSize de 1.

[PlayFlop_]

@‘Plaigon’:

Il faut que tes ItemStack d’armures/épées/outils moddées stackable d’origine par 1, contenus dans ton fichier .yml du plugin, soient enregistrés avec un stackSize de 1.

Oui mais ou je doit modifier ceci ?

Car dans essentials il n’y a pas moyen fin je trouve pas

[Deleted]

Tu donnes l’impression de ne rien connaître à ton plugin de kit, ou tout du moins au contenu du fichier yml dont nous sommes en présence.
Moi j’ai vu des lignes comportant plusieurs paramètres, et j’en déduis l’odre suivant: l’id de l’item à give, sa quantité, et optionnellement des tag à attribuer (ici des enchantements).
Quelqu’un ne sera pas toujours là pour te mâcher le travail, et te renvoyer le fichier .yml dont tu rêves nuit et jour, (enfin ai-je parlé trop vite ? Peut-être BrokenSwing aura la complaisance de le faire, hmm ?).
A ta place je relirai la doc sur ton plugin de kit, et j’essaierai de bidouiller les lignes constituant le fichier .yml, modifier tel ou tel paramètre que je t’ai explicité au-desssus

[BrokenSwing]

Tu te fais du mal Plaigon, arrête de le support de la 1.7.10

[PlayFlop_]

@‘Plaigon’:

Tu donnes l’impression de ne rien connaître à ton plugin de kit, ou tout du moins au contenu du fichier yml dont nous sommes en présence.
Moi j’ai vu des lignes comportant plusieurs paramètres, et j’en déduis l’odre suivant: l’id de l’item à give, sa quantité, et optionnellement des tag à attribuer (ici des enchantements).
Quelqu’un ne sera pas toujours là pour te mâcher le travail, et te renvoyer le fichier .yml dont tu rêves nuit et jour, (enfin ai-je parlé trop vite ? Peut-être BrokenSwing aura la complaisance de le faire, hmm ?).
A ta place je relirai la doc sur ton plugin de kit, et j’essaierai de bidouiller les lignes constituant le fichier .yml, modifier tel ou tel paramètre que je t’ai explicité au-desssus

Je m’en fou d’avoir le fichioer .yml fait, je veux juste comprendre quell ligne je suis censé modifié, j’avais lu que c’étais avec le stacksize (LES DEUX lignes que je t’ai donc envoyé) et au final tu me parle des Kits mais me dit pas ce qui ne vas pas donc bon…
Les tags comme tu dit, ne changeront rien vus que quand On refera le kit, les TAGS comme tu dis seront quand même les même qu’avant.

EDIT:
Pour information, le plugin essentials est le même pour les version au dessus

[BrokenSwing]

Et cette discussion devrait se trouver dans “Support pour les utilisateurs”

[PlayFlop_]

@‘BrokenSwing’:

Et cette discussion devrait se trouver dans “Support pour les utilisateurs”

Oui, autant pour moi

[Deleted]

Ne détourne pas le sens de mes phrases, tu as aussi l’air d’avoir du mal avec la langue française.
Je te parlais des kits car tu essaies de give des items à des joueurs en fonctions de la commande kit, et car surtout ton fichier .yml semble les give en fonction des kits possédés par le joueur exécutant la commande. Une dernière fois, puisque t’as du mal semblerait-il, il te faut reprendre les lignes ajoutant les items à give, et voir celles-ci concernant tes items moddés, et retirés tout chiffre/nombre associés au stackSize, qui dépasserait 1, et rajouter la ligne concernée autant de fois que tu veux combler les slots du joueur avec.
A quel moment ai-je dit que les tags allaient résoudre ton problème ? J’ai parlé des tags pour décrire les paramètres des lignes sur lesquelles tu butes.
Au passage, on va déjà atteindre la troisième page pour un problème aussi ridicule, voire même grotesque pour quelqu’un qui se prénomme “Dév” xDDD
Au lieu de venir me retourner mes propres mots, essaie au moins de dire ne serait-ce qu’une seule fois, le mot merci, car il va s’agir, minimum,de ton 6ème ou 7ème poste de demande d’aide auquel je réponds, et pas une seule fois, t’as eu la bonté de me remercie avec un point de réputation. J’ai l’impression de perdre mon temps quand j’aide des personnes comme toi, vois ton soucis avec d’autres membres, qui auront + de patience que moi, car moi j’ai déjà atteint la limite mdrr

[PlayFlop_]

@‘Plaigon’:

Ne détourne pas le sens de mes phrases, tu as aussi l’air d’avoir du mal avec la langue française.
Je te parlais des kits car tu essaies de give des items à des joueurs en fonctions de la commande kit, et car surtout ton fichier .yml semble les give en fonction des kits possédés par le joueur exécutant la commande. Une dernière fois, puisque t’as du mal semblerait-il, il te faut reprendre les lignes ajoutant les items à give, et voir celles-ci concernant tes items moddés, et retirés tout chiffre/nombre associés au stackSize, qui dépasserait 1, et rajouter la ligne concernée autant de fois que tu veux combler les slots du joueur avec.
A quel moment ai-je dit que les tags allaient résoudre ton problème ? J’ai parlé des tags pour décrire les paramètres des lignes sur lesquelles tu butes.
Au passage, on va déjà atteindre la troisième page pour un problème aussi ridicule, voire même grotesque pour quelqu’un qui se prénomme “Dév” xDDD
Au lieu de venir me retourner mes propres mots, essaie au moins de dire ne serait-ce qu’une seule fois, le mot merci, car il va s’agir, minimum,de ton 6ème ou 7ème poste de demande d’aide auquel je réponds, et pas une seule fois, t’as eu la bonté de me remercie avec un point de réputation. J’ai l’impression de perdre mon temps quand j’aide des personnes comme toi, vois ton soucis avec d’autres membres, qui auront + de patience que moi, car moi j’ai déjà atteint la limite mdrr

En même temps la pluspart de mes postes, tu me prend pour un con, et ne m’aide pas.
Donc je vous pas pourquoi je te remercierais.

Sur mes autres postes, la plupart du temps c’est d’autre moddeur qui me donne réponse et non TOI.

Donc vus que CETTE FOIS tu ma aider, OUI je te dit MERCI.

Donc avant de prendre les gens pour des cons et te croire supérieurs a tout le monde, vas te faire soigné vieux fou.

[robin4002]

J’ai déplacé dans la section aide de la catégorie cauldron qui est plus appropriée.

Merci également de vous calmer …

[Deleted]

De rien, satisfait d’avoir pu rendre service, mais ça n’empêche que tu pourrais rester courtois, au lieu d’avoir recours à des insultes et de vilaines phrases. Je ne te prends pas pour un “c**”, sincèrement, mais pour un débutant qui déteste chercher par lui même, voilà tout !
Ah et aussi, tu es sûrement le seul sur ce forum, à penser que je suis “un vieux fou devant se faire soigner”  :issou: