Aller au contenu

uiytt

Ancien
  • Compteur de contenus

    1 152
  • Inscription

  • Dernière visite

  • Jours gagnés

    44

Tout ce qui a été posté par uiytt

  1. uiytt

    Spawn Egg

    Essaye avec "1 zombie spawn egg" et pour les gui... Voici pourquoi TuSKe > SkQuery (pour les guis): https://skript-mc.fr/forum/threads/pourquoi-utilise-tuske-au-lieu-de-skquery-pour-les-gui.15437/#post-120249
  2. uiytt

    Spawn Egg

    Pour les items peut importe que ça soit un menu, un give, un set slot, une condition, etc... le nom restera le même après il te suffit juste d'utiliser la syntaxe pour gui donc dans ce cas: make a gui slot 0 of player with 1 zombie egg named "test"
  3. uiytt

    Spawn Egg

    Normalement juste "1 zombie egg" devrait macher
  4. Par confusions c'est juste que les variables était mal nommé où autre chose ?
  5. C'est pas pour être méchant mais il n'y a strictement AUCUN intérêt à mettre un truc pour ne pas bugué à un truc qui ne bug pas...
  6. heu tu as déjà eu des bugs avec des variables non persistante ??? et pour les conflit faut juste bien gérer les noms...
  7. uiytt

    Authme SkAddon.. ?

    J'ai cherché deux second et j'ai ça : https://www.spigotmc.org/resources/login-skript.34223/ Mais effectivement je peux pas t'aider pour AuthMe
  8. Heu il est totalement inutile de utiliser le .%player% si la variable n'est pas permanante non ? {_EnchantedItemOfPlayer.%player%}
  9. uiytt

    Authme SkAddon.. ?

    Tu peux utiliser un des innobrables skripts de mdp au login et après tu modifie le code non ?
  10. uiytt

    Authme SkAddon.. ?

    Tu cherche quoi dans skaddon ?
  11. J'ai clairement trop la flemme XD de plus les problèmes d'opti sont pas très grave, c'est juste quelques lignes qui pourrait être enlevé
  12. Ok j'ai corrigé et j'ai aussi ajouté pour les joueurs qui sont add dans un claim Par contre pas terrible l'optimisation de ton claim mais pas grave, Voici le code ^^: options: GHamMSG: "&aTu as reçu %arg 2% hammeur(s) !" NNerr: "&cNombres négatifs non-autorisés !" command /hammeur [<text>] [<number>] [<player>]: permission: hammeur.give trigger: if arg 1 is "give": if arg-2 > 0: give arg-2 of iron pickaxe of efficiency 6 and unbreaking 4 and fortune 3 named "&c[&6Hammeur&c]" to arg-3 send {@GHamMSG} else: send {@NNerr} on break: if name of player's tool is "&c[&6Hammeur&c]": set {_1.%player%} to location of event-block set {_2.%player%} to location of event-block if player's pitch is between -50 and 50: add 1 to y-coord of {_1.%player%} subtract 1 from y-coord of {_2.%player%} if player's horizontal facing is west or east: add 1 to z-coord of {_1.%player%} subtract 1 from z-coord of {_2.%player%} loop blocks within {_1.%player%} to {_2.%player%}: if {chunk.%chunk at location of loop-block%} is not set: set {_ok} to true if {chunk.%chunk at location of loop-block%} is equal to player: set {_ok} to true if {chunk.%chunk at location of player%.%player%} is equal to true: set {_ok} to true if {_ok} is equal to true: id of loop-block isn't 7 or 8 or 9 or 10 or 11 or 138 or 49 or 47 or 52 or 52 or 87 or 0 or 89 or 17 or 5 or 80 or 65 break loop-block with player's tool if player's tool is enchanted with fortune 1: chance of 3%: drop 1 diamond at loop-block else if player's tool is enchanted with fortune 2: chance of 2%: drop 2 diamond at loop-block else if player's tool is enchanted with fortune 3: chance of 3%: drop 3 diamond at loop-block else if player's tool is enchanted with fortune 4: chance of 3%: drop 4 diamond at loop-block else if player's tool is enchanted with fortune 5: chance of 3%: drop 5 diamond at loop-block else if player's horizontal facing is north or south: add 1 to x-coord of {_1.%player%} subtract 1 from x-coord of {_2.%player%} loop blocks within {_1.%player%} to {_2.%player%}: if {chunk.%chunk at location of loop-block%} is not set: set {_ok} to true if {chunk.%chunk at location of loop-block%} is equal to player: set {_ok} to true if {chunk.%chunk at location of player%.%player%} is equal to true: set {_ok} to true if {_ok} is equal to true: id of loop-block isn't 7 or 8 or 9 or 10 or 11 or 138 or 49 or 47 or 52 or 87 or 0 or 89 or 17 or 5 or 80 or 65 break loop-block with player's tool if player's tool is enchanted with fortune 1: chance of 3%: drop 1 diamond at loop-block else if player's tool is enchanted with fortune 2: chance of 3%: drop 2 diamond at loop-block else if player's tool is enchanted with fortune 3: chance of 3%: drop 3 diamond at loop-block else if player's tool is enchanted with fortune 4: chance of 3%: drop 4 diamond at loop-block else if player's tool is enchanted with fortune 5: chance of 3%: drop 5 diamond at loop-block else: add 1 to x-coord of {_1.%player%} add 1 to z-coord of {_1.%player%} subtract 1 from x-coord of {_2.%player%} subtract 1 from z-coord of {_2.%player%} loop blocks within {_1.%player%} to {_2.%player%}: if {chunk.%chunk at location of loop-block%} is not set: set {_ok} to true if {chunk.%chunk at location of loop-block%} is equal to player: set {_ok} to true if {chunk.%chunk at location of player%.%player%} is equal to true: set {_ok} to true if {_ok} is equal to true: id of loop-block isn't 7 or 8 or 9 or 10 or 11 or 138 or 49 or 47 or 52 or 87 or 0 or 89 or 17 or 5 or 80 or 65 break loop-block with player's tool if player's tool is enchanted with fortune 1: chance of 3%: drop 1 diamond at loop-block else if player's tool is enchanted with fortune 2: chance of 3%: drop 2 diamond at loop-block else if player's tool is enchanted with fortune 3: chance of 3%: drop 3 diamond at loop-block else if player's tool is enchanted with fortune 4: chance of 3%: drop 4 diamond at loop-block else if player's tool is enchanted with fortune 5: chance of 3%: drop 5 diamond at loop-block
  13. Mais si tu es propriétaire tu peux ?
  14. Ha oui j'ai fais une erreurs d’inattention, essaye ça : options: GHamMSG: "&aTu as reçu %arg 2% hammeur(s) !" NNerr: "&cNombres négatifs non-autorisés !" command /hammeur [<text>] [<number>] [<player>]: permission: hammeur.give trigger: if arg 1 is "give": if arg-2 > 0: give arg-2 of iron pickaxe of efficiency 6 and unbreaking 4 and fortune 3 named "&c[&6Hammeur&c]" to arg-3 send {@GHamMSG} else: send {@NNerr} on break: if name of player's tool is "&c[&6Hammeur&c]": set {_1.%player%} to location of event-block set {_2.%player%} to location of event-block if player's pitch is between -50 and 50: add 1 to y-coord of {_1.%player%} subtract 1 from y-coord of {_2.%player%} if player's horizontal facing is west or east: add 1 to z-coord of {_1.%player%} subtract 1 from z-coord of {_2.%player%} loop blocks within {_1.%player%} to {_2.%player%}: if {chunk.%chunk at location of loop-block%} is not set: set {_ok} to true if {chunk.%chunk at location of loop-block%} is equal to "%player%": set {_ok} to true if {_ok} is equal to true: id of loop-block isn't 7 or 8 or 9 or 10 or 11 or 138 or 49 or 47 or 52 or 52 or 87 or 0 or 89 or 17 or 5 or 80 or 65 break loop-block with player's tool if player's tool is enchanted with fortune 1: chance of 3%: drop 1 diamond at loop-block else if player's tool is enchanted with fortune 2: chance of 2%: drop 2 diamond at loop-block else if player's tool is enchanted with fortune 3: chance of 3%: drop 3 diamond at loop-block else if player's tool is enchanted with fortune 4: chance of 3%: drop 4 diamond at loop-block else if player's tool is enchanted with fortune 5: chance of 3%: drop 5 diamond at loop-block else if player's horizontal facing is north or south: add 1 to x-coord of {_1.%player%} subtract 1 from x-coord of {_2.%player%} loop blocks within {_1.%player%} to {_2.%player%}: if {chunk.%chunk at location of loop-block%} is not set: set {_ok} to true if {chunk.%chunk at location of loop-block%} is equal to "%player%": set {_ok} to true if {_ok} is equal to true: id of loop-block isn't 7 or 8 or 9 or 10 or 11 or 138 or 49 or 47 or 52 or 87 or 0 or 89 or 17 or 5 or 80 or 65 break loop-block with player's tool if player's tool is enchanted with fortune 1: chance of 3%: drop 1 diamond at loop-block else if player's tool is enchanted with fortune 2: chance of 3%: drop 2 diamond at loop-block else if player's tool is enchanted with fortune 3: chance of 3%: drop 3 diamond at loop-block else if player's tool is enchanted with fortune 4: chance of 3%: drop 4 diamond at loop-block else if player's tool is enchanted with fortune 5: chance of 3%: drop 5 diamond at loop-block else: add 1 to x-coord of {_1.%player%} add 1 to z-coord of {_1.%player%} subtract 1 from x-coord of {_2.%player%} subtract 1 from z-coord of {_2.%player%} loop blocks within {_1.%player%} to {_2.%player%}: if {chunk.%chunk at location of loop-block%} is not set: set {_ok} to true if {chunk.%chunk at location of loop-block%} is equal to "%player%": set {_ok} to true if {_ok} is equal to true: id of loop-block isn't 7 or 8 or 9 or 10 or 11 or 138 or 49 or 47 or 52 or 87 or 0 or 89 or 17 or 5 or 80 or 65 break loop-block with player's tool if player's tool is enchanted with fortune 1: chance of 3%: drop 1 diamond at loop-block else if player's tool is enchanted with fortune 2: chance of 3%: drop 2 diamond at loop-block else if player's tool is enchanted with fortune 3: chance of 3%: drop 3 diamond at loop-block else if player's tool is enchanted with fortune 4: chance of 3%: drop 4 diamond at loop-block else if player's tool is enchanted with fortune 5: chance of 3%:
  15. uiytt

    [Tuske Gui] Changer Attack damages

    C'est vraiment dans les nbt ? O_o
  16. uiytt

    Balise de Soin

  17. uiytt

    [Tuske Gui] Changer Attack damages

    De 1 ça ne change que pour le joueur de 2 il y a encore plus d'infos sur l'item...
  18. uiytt

    [Tuske Gui] Changer Attack damages

    Tu ne peux pas l'enlever à ma connaissance... mais à partir de la 1.9 le +7 attack damage passe en gris et deviens plus petit
  19. Je m'y connais pas vraiment car je préfère ne pas utiliser les condition raccourcis, c'est moins pratique quand on essaye de comprendre un code.
  20. uiytt

    Balise de Soin

    Tu as mal copié mon code ^^ c'est pas while event-block at location.... mais while block at location....
  21. uiytt

    Bug ou erreur de code ?

    Ok passe ton poste en résolue ^^
  22. uiytt

    Balise de Soin

    De rien ça fait plaisir ^^ et les doubles postes c'est pas pour moi c'est juste qu'un modo qui passe par là risque de te mettre une infraction... Et essaye de remplacer placed block par event-block
  23. uiytt

    Balise de Soin

    Essaye : On place: if player's gamemode is survival: if event-block is 1 beacon named "&9&lBalise regen" with lore "&9Regen pendant 30 second x2": set {_s} to 0 while block at location of placed block is a beacon: loop all players in radius 10 around location of placed block: apply regeneration of tier 2 to loop-player for 1 second wait 1 second if {_s} is equal to 30: set block at location of placed block to air add 1 to {_s} Et fait attention au double poste !
  24. uiytt

    Bug ou erreur de code ?

    t'as enlevé les %% ?
  25. uiytt

    Balise de Soin

×
×
  • Créer...

Information importante

Nous avons placé des cookies sur votre appareil pour aider à améliorer ce site. Vous pouvez choisir d’ajuster vos paramètres de cookie, sinon nous supposerons que vous êtes d’accord pour continuer.