Skripting

Précise à quoi sert la commande xD ! on join: wait a tick give a diamond sword named "Duel" to player on rightclick: player's tool is a diamond sword name of player's tool is "Duel" open chest with 6 rows named "Duel" to player loop all players: add 1 to {_n} make a gui slot {_n} - 1 of player with player head named "%loop-player%" to close then run player command "/duel %loop-player%" make a gui slot 53 of player with paper named "Duel aléatoire" to close then run player command "/duelrandom" command /duel <player>: trigger: set {_loc} to arg's location add 6 to x-pos of {_loc} add 6 to z-pos of {_loc} teleport player to {_loc} wait a tick give a diamond sword to player and arg send "Le duel commence !" to player and arg command /duelrandom: trigger: make player execute command "/duel %random player out of all players%" on death: victim is a player attacker is a player add 10 to {elos.%attacker%} command /elos: trigger: send "Vous avez %{elos.%player%}% !" on join: {elos.%player%} is not set set {elos.%player%} to 0

Il va falloir passer autrement. Une location dans un fichier YML, a tendance à s'enregistrer comme ça : Loc: # Nom de ta location (je prends la tienne). X: 0 # X. Y: 64 # Y. Z: 0 # Z. World: Lobby # Nom du monde où se trouve la location. Du coup on va faire comme ceci : (J'utilise le YML de SkUtilities qui est mieux) : command /setloc: trigger: set yml value "Loc.X" of file "plugins/Skript/scripts/Villes.yml" to x-pos of player set yml value "Loc.Y" of file "plugins/Skript/scripts/Villes.yml" to y-pos of player set yml value "Loc.Z" of file "plugins/Skript/scripts/Villes.yml" to z-pos of player set yml value "Loc.World" of file "plugins/Skript/scripts/Villes.yml" to "%player's world%" send "Location définie !" command /loc: trigger: set {_x} to yml value "Loc.X" of file "plugins/Skript/scripts/Villes.yml" set {_y} to yml value "Loc.Y" of file "plugins/Skript/scripts/Villes.yml" set {_z} to yml value "Loc.Z" of file "plugins/Skript/scripts/Villes.yml" set {_world} to yml value "Loc.World" of file "plugins/Skript/scripts/Villes.yml" teleport player to position {_x}, {_y}, {_z}, of the world {_world}

FAIS DES RECHERCHES !

on join: wait a tick give a diamond sword named "Duel" to player on rightclick: clicked item is a diamond sword name of clicked item is "Duel" open chest with 6 rows named "Duel" to player loop all players: add 1 to {_n} make a gui slot {_n} - 1 of player with (skull of loop-player parsed as an offline player) named "%loop-player%" to close then run player command "/duel %loop-player%" make a gui slot 53 of player with paper named "Duel aléatoire" to close then run player command "/duelrandom" command /duel <player>: trigger: set {_loc} to arg's location add 6 to x-pos of {_loc} add 6 to z-pos of {_loc} teleport player to {_loc} wait a tick give a diamond sword to player and arg send "Le duel commence !" to player and arg command /duelrandom: trigger: make player execute command "/duel %random player out of all players%" on death: victim is a player attacker is a player add 10 to {elos.%attacker%} command /elos: trigger: send "Vous avez %{elos.%player%}% !" on join: {elos.%player%} is not set set {elos.%player%} to 0

Expression : island level of player Avec WolvSK.

on respawn: wait a tick make player execute command "/taCommande"

Bah ce que t'as mis est bon !

Sinon y a encore plus simple x) : teleport {ta.liste::*} to {ta.location}

LargeSK passe aussi par un PlayerMoveEvent ;) ! Donc ça reviendrait au même. Si tu le veux vraiment en Skript, tu n'auras pas le choix de passer par un On Any Movement : on any movement: {chunck.%player%} = null: set {chunck.%player%} to player's chunk else: {chunck.%player%} != {chunck.%player%} set {_last} to {chunck.%player%} set {chunck.%player%} to player's chunck invoke "On Chunck Change" from player, {_last} and {chunck.%player%} sub "On Chunk Change": send "Vous êtes passé du Chunck %parameter 2% au Chunck %parameter 3% !" to parameter 1

loop all players: loop-player has permission "pompier.receiver" send "..." to loop-player

if {ta.liste::*} contain player

Non car lorsque l'effet est appelé, dans le code Java, Skript détecte si un slah est présent ou pas et l'accorde avec la commande. Il ne récupère pas le string directement donc les deux syntaxes fonctionnent.

C'est un signe d'inégalité. Le != remplace le "is not". C'est comme si j'avais mis : victim is not attacker # Est pareil que : victim != attacker

on death: victim is a player attacker is a player victim != attacker execute console command "/iconomy:money give %attacker% 5"

command /buy <number>: trigger: if {money.%player%} >= arg 1: # ... Si ça ne marche pas, merci de suivre cette procédure : http://pastebin.com/raw/ip1C4XHN

command /cow: trigger: spawn a cow at player's location make the player ride the spawned entity

Tu peux en mettre ou pas, ça revient au même.

Il faut doubler les guillemets car tu utilises des guillemets dans des guillemets.

command /buy <text>: trigger: if {money.%player%} >= arg 1 parsed as a number: # ...

Ça me met bien le nombre d'entrées de la liste mais quand je mets le code dans une fonction: [spoiler=CODE FONCTION] # Fonction function NBClaim(text: text) :: integer: set {_chunks::*} to yaml list "%{_text}%" from file "Ville-Chunk.yml" set {_nombre} to 0 loop {_chunks::*}: add 1 to {_nombre} return {_nombre} # Commande pour voir la fonction command /exemple: trigger: message "%NBClaim(""Aryonia"")%" Ça me mets "<none>" j'aimerais donc savoir ou est mon erreur . Merci de m'avoir lu ! C'est un bug avec Skript, quand tu renvoies un integer, ça renverra tout le temps <none> à cause du bug. Soit tu remplaces :: integer: par :: number: ou bien par :: object:

options: Top: 5 # T'as le choix entre un top 3, 5, 10 etc... command /balancetop: trigger: loop all players: {money.%loop-player%} is set set {_players::%loop-player%} to {money.%loop-player%} loop {_players::*}: add 1 to {_number} if {_ascending::%loop-value%} is not set: set {_ascending::%loop-value%} to loop-index else: set {_number} to 0 loop {_size} times: {_ascending::%loop-value-1%.%loop-number%} is not set set {_ascending::%loop-value-1%.%loop-number%} to loop-index exit loop set {_size} to size of {_ascending::*} loop {_ascending::*}: set {_declining::%{_size}%} to loop-value remove 1 from {_size} send "&aTop {@Top} :" loop {_declining::*}: add 1 to {_result} send "&b%loop-value%&7: &e%{_players::%loop-value%}% !" {_result} is {@Top} stop

Non ce n'est pas exact :P : if {rush1.team.bleu::*} contain player Parce que sinon, si on a deux joueurs : "PsY", et "LePsY". Et que j'utilise le code de @WilliamEzzz, bah ça va détecter les 2 joueurs.

Problème avec les HashMap c'est qu'elles ne peuvent pas être sauvegardées contrairement aux variables et prennent trop de RAM.

On fait ça en Skript aussi x) : function joinPlayerArena(p: player, arena: text): invoke "On Arena Start" from {_p} and {_arena} sub "On Arena Start": if parameter 2 is "ID de votre mini-jeu": # ... Pour rejoindre une arène : joinPlayerArena(leJoueur, "Nom de l'arène") Ca économise un plugin de plus mais sinon GG x) !

Tes variables ?