Aller au contenu
  • 0

Le to run player command "/tacommande" de tuske Marche pas

AppleSHaf

Posée par AppleSHaf,

 Partager

Question

AppleSHaf Apprenti

AppleSHaf

Posté(e)
Posté(e)

Bonjour Et bien mon problème est simple voici mon code
  

			open virtual chest inventory with size 2 with name "&6&lShop / Blocks" to player
			create a gui slot 0 of player with 64 obsidian named "&fObsidian &c&lAcheter pour &e16.000$" to run player command "/buyobsi"

c'est cette partie la qui ne marche pas mais voici le code entier
  

command /ShopFactionsblock:
	trigger:
		if world is "Factions":	
			open virtual chest inventory with size 2 with name "&6&lShop / Blocks" to player
			create a gui slot 0 of player with 64 obsidian named "&fObsidian &c&lAcheter pour &e16.000$" to run player command "/buyobsi"

Et le truc ces que le Player a part si il est op sa n'execute pas la commande /buyObsi
Je ne comprend pas ... ces la premiere fois que j utilise tuske Jetait avant sous SkQuery Donc peut être ces un truc tout Con
Merci d'avance pour vos reponsse 

11 réponses à cette question

Messages recommandés

  • 0
AppleSHaf Apprenti

AppleSHaf

Posté(e)
  • Auteur
Posté(e)
Il y a 4 heures, noftaly a dit :

Perso je n'ai jamais réussi a faire marcher ca...

J'utilise tout le temps le 


blablabla to run:
	make player execute command "/tacommande"

 

Ha

  • 0
AppleSHaf Apprenti

AppleSHaf

Posté(e)
  • Auteur
Posté(e)

Mais enfaite jai sa comme erreur dans la console
  

14.10 17:34:31 [Server] ERROR #!#! 
14.10 17:34:31 [Server] ERROR #!#! [Skript] Severe Error:
14.10 17:34:31 [Server] ERROR #!#! TuSKe's class com.github.tukenuke.tuske.effects.EffMakeDrop generated an exception while loading
14.10 17:34:31 [Server] ERROR #!#! 
14.10 17:34:31 [Server] ERROR #!#! Something went horribly wrong with Skript.
14.10 17:34:31 [Server] ERROR #!#! This issue is NOT your fault! You probably can't fix it yourself, either.
14.10 17:34:31 [Server] ERROR #!#! It looks like you are using some plugin(s) that alter how Skript works (addons).
14.10 17:34:31 [Server] ERROR #!#! Following plugins are probably related to this error in some way:
14.10 17:34:31 [Server] ERROR #!#! TuSKe (github.com/Tuke-Nuke/TuSKe) 
14.10 17:34:31 [Server] ERROR #!#! You should try disabling those plugins one by one, trying to find which one causes it.
14.10 17:34:31 [Server] ERROR #!#! If the error doesn't disappear even after disabling all listed plugins, it is probably Skript issue.
14.10 17:34:31 [Server] ERROR #!#! In that case, you will be given instruction on how should you report it.
14.10 17:34:31 [Server] ERROR #!#! On the other hand, if the error disappears when disabling some plugin, report it to author of that plugin.
14.10 17:34:31 [Server] ERROR #!#! Only if the author tells you to do so, report it as Skript issue (url below)
14.10 17:34:31 [Server] ERROR #!#! Issue tracker: https://github.com/SkriptLang/Skript/issues (only if you know what you're doing!)
14.10 17:34:31 [Server] ERROR #!#! 
14.10 17:34:31 [Server] ERROR #!#! Stack trace:
14.10 17:34:31 [Server] ERROR #!#! java.lang.NullPointerException
14.10 17:34:31 [Server] ERROR #!#!     at com.github.tukenuke.tuske.effects.EffMakeDrop.<clinit>(EffMakeDrop.java:25)
14.10 17:34:31 [Server] ERROR #!#!     at java.lang.Class.forName0(Native Method)
14.10 17:34:31 [Server] ERROR #!#!     at java.lang.Class.forName(Class.java:348)
14.10 17:34:31 [Server] ERROR #!#!     at ch.njol.skript.SkriptAddon.loadClasses(SkriptAddon.java:108)
14.10 17:34:31 [Server] ERROR #!#!     at com.github.tukenuke.tuske.TuSKe.onEnable(TuSKe.java:100)
14.10 17:34:31 [Server] ERROR #!#!     at org.bukkit.plugin.java.JavaPlugin.setEnabled(JavaPlugin.java:292)
14.10 17:34:31 [Server] ERROR #!#!     at org.bukkit.plugin.java.JavaPluginLoader.enablePlugin(JavaPluginLoader.java:340)
14.10 17:34:31 [Server] ERROR #!#!     at org.bukkit.plugin.SimplePluginManager.enablePlugin(SimplePluginManager.java:405)
14.10 17:34:31 [Server] ERROR #!#!     at org.bukkit.craftbukkit.v1_9_R2.CraftServer.loadPlugin(CraftServer.java:362)
14.10 17:34:31 [Server] ERROR #!#!     at org.bukkit.craftbukkit.v1_9_R2.CraftServer.enablePlugins(CraftServer.java:322)
14.10 17:34:31 [Server] ERROR #!#!     at net.minecraft.server.v1_9_R2.MinecraftServer.t(MinecraftServer.java:416)
14.10 17:34:31 [Server] ERROR #!#!     at net.minecraft.server.v1_9_R2.MinecraftServer.l(MinecraftServer.java:381)
14.10 17:34:31 [Server] ERROR #!#!     at net.minecraft.server.v1_9_R2.MinecraftServer.a(MinecraftServer.java:336)
14.10 17:34:31 [Server] ERROR #!#!     at net.minecraft.server.v1_9_R2.DedicatedServer.init(DedicatedServer.java:268)
14.10 17:34:31 [Server] ERROR #!#!     at net.minecraft.server.v1_9_R2.MinecraftServer.run(MinecraftServer.java:532)
14.10 17:34:31 [Server] ERROR #!#!     at java.lang.Thread.run(Thread.java:748)
14.10 17:34:31 [Server] ERROR #!#! 
14.10 17:34:31 [Server] ERROR #!#! Version Information:
14.10 17:34:31 [Server] ERROR #!#!   Skript: 2.2-dev36
14.10 17:34:31 [Server] ERROR #!#!   Bukkit: 1.9.4-R0.1-SNAPSHOT
14.10 17:34:31 [Server] ERROR #!#!   Minecraft: 1.9.4
14.10 17:34:31 [Server] ERROR #!#!   Java: 1.8.0_181 (Java HotSpot(TM) 64-Bit Server VM 25.181-b13)
14.10 17:34:31 [Server] ERROR #!#!   OS: Linux amd64 4.9.103-xxxx-std-ipv6-64
14.10 17:34:31 [Server] ERROR #!#! 
14.10 17:34:31 [Server] ERROR #!#! Server platform: Spigot
14.10 17:34:31 [Server] ERROR #!#! 
14.10 17:34:31 [Server] ERROR #!#! Current node: null
14.10 17:34:31 [Server] ERROR #!#! Current item: null
14.10 17:34:31 [Server] ERROR #!#! 
14.10 17:34:31 [Server] ERROR #!#! Thread: Server thread
14.10 17:34:31 [Server] ERROR #!#! 
14.10 17:34:31 [Server] ERROR #!#! Language: english
14.10 17:34:31 [Server] ERROR #!#! Link parse mode: DISABLED
14.10 17:34:31 [Server] ERROR #!#! 
14.10 17:34:31 [Server] ERROR #!#! End of Error.
14.10 17:34:31 [Server] ERROR #!#!

 

Invité
Ce sujet ne peut plus recevoir de nouvelles réponses.
 Partager
Aller à la liste des questions
×
×
  • 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.