Using carrot on a sticks as triggers - Revision history

Mellori: Category

2020-10-11T12:45:01Z

Zedwick: Added tutorial category

2017-07-14T15:59:17Z

Added tutorial category

Dax23333 at 15:22, 14 July 2017

2017-07-14T15:22:54Z

Dax23333 at 15:20, 14 July 2017

2017-07-14T15:20:57Z

Dax23333 at 15:19, 14 July 2017

2017-07-14T15:19:34Z

Dax23333 at 15:01, 14 July 2017

2017-07-14T15:01:30Z

Dax23333 at 14:47, 14 July 2017

2017-07-14T14:47:06Z

Dax23333: Created page with "Carrot on a sticks are often used as activators for tools in maps. The reason for this is that a scoreboard objective with the type stat.useItem.carrot_on_a_stick will increme..."

2017-07-14T14:28:34Z

Created page with "Carrot on a sticks are often used as activators for tools in maps. The reason for this is that a scoreboard objective with the type stat.useItem.carrot_on_a_stick will increme..."

New page

Carrot on a sticks are often used as activators for tools in maps. The reason for this is that a scoreboard objective with the type stat.useItem.carrot_on_a_stick will increment whenever the item is right clicked, regardless of any kind of success condition as is common with other items. Blocks for example need to be placed, and food needs to be eaten. But the carrot on a stick becomes a right click detector with this objective set up, making it extremely useful.

This tutorial will cover the construction of a simplified version of the class ability system from dungeondash, which is far too large and complex to properly cover here. It will also feature the ability to have seperate carrot on a sticks that do different things depending on thier lore, creating vast numbers of possible uses for them in a single map. The dungeon dash class system is unfortunatly outdated, and the 1.12 addition of @s would help simplify some of the commands. Other aspects of it will likely be covered in future tutorials.

==Commands==
This tutorial uses 4 commands.
*scoreboard (tagging, creating objectives, setting scores, testing scores)
*execute
*say
*give

==The Tutorial==
Firstly we want to setup our objective to track players right clicking a carrot on a stick. There should only be one of these on the server, more are completly unnecessary.

/scoreboard objectives add UseStick stat.useItem.minecraft.carrot_on_a_stick

Set this objective to be displayed on the sidebar to see it working.

/scoreboard objectives setdisplay sidebar UseStick

← Older revision		Revision as of 12:45, 11 October 2020
Line 130:		Line 130:
	'''/give @p minecraft:carrot_on_a_stick 1 0 {display:{Lore:["This is a magic wand!"]}}'''		'''/give @p minecraft:carrot_on_a_stick 1 0 {display:{Lore:["This is a magic wand!"]}}'''

−	[[Category:~~Tutorial~~]]	+	[[Category:Minecraft_Tutorial]]

← Older revision		Revision as of 15:59, 14 July 2017
Line 129:		Line 129:

	'''/give @p minecraft:carrot_on_a_stick 1 0 {display:{Lore:["This is a magic wand!"]}}'''		'''/give @p minecraft:carrot_on_a_stick 1 0 {display:{Lore:["This is a magic wand!"]}}'''
		+
		+	[[Category:Tutorial]]

@@ Line 1: / Line 1: @@
 Carrot on a sticks are often used as activators for tools in maps. The reason for this is that a scoreboard objective with the type stat.useItem.carrot_on_a_stick will increment whenever the item is right clicked, regardless of any kind of success condition as is common with other items. Blocks for example need to be placed, and food needs to be eaten. But the carrot on a stick becomes a right click detector with this objective set up, making it extremely useful.
-This tutorial will cover the construction of a simplified version of the class ability system from dungeondash, which is far too unweildy to use as a useful tutorial. It will also feature the ability to have seperate carrot on a sticks that do different things depending on thier lore, creating vast numbers of possible uses for them in a single map. The dungeon dash class system is unfortunatly outdated, and the 1.12 addition of @s would help simplify some of the commands. Other aspects of it will likely be covered in future tutorials.
+This tutorial will cover the construction of a simplified version of the class ability system from [[Dungeon Dash]], which is far too unweildy to use as a useful tutorial. It will also feature the ability to have seperate carrot on a sticks that do different things depending on thier lore, creating vast numbers of possible uses for them in a single map. The dungeon dash class system is unfortunatly outdated, and the 1.12 addition of @s would help simplify some of the commands. Other aspects of it will likely be covered in future tutorials.
 ==Commands==

@@ Line 9: / Line 9: @@
 *say
 *give
 ==The Tutorial==
@@ Line 55: / Line 56: @@
 '''/scoreboard players set @a[score_UseStick_min=1] UseStick 0'''
 ===Mages Ability===
-The MageAbility tag marks players using thier class ability as a mage. In Dungeon Dash this summons an iron golem, as well as making lots of particles and sound effects. In this example we will just summon an iron golem, as the particles really are not that important. We will also announce use of thier ability in chat using say. This is done by executing on players with the MageAbility tag. Once thier ability is activated, a cooldown time is set and the MageAbility tag removed. Make sure to remove the MageAbility tag or you will constantly summon iron golems on anyone who uses the stick in a situation that is both embaressing and difficult to fix.
+The MageAbility tag marks players using thier class ability as a mage. In Dungeon Dash this summons an iron golem, as well as making lots of particles and sound effects. In this example we will just summon an iron golem, as the particles really are not that important. We will also announce use of thier ability in chat using say. This is done by executing on players with the MageAbility tag. If the say command is executed on a player it will use thier name in chat, followed by the message. Once thier ability is activated, a cooldown time is set and the MageAbility tag removed. Make sure to remove the MageAbility tag or you will constantly summon iron golems on anyone who uses the stick in a situation that is both annoying and difficult to fix.
 '''/execute @a[tag=MageAbility] ~ ~ ~ say I summoned a Rusty!'''
@@ Line 70: / Line 77: @@
 '''/scoreboard players tag @a[tag=MageAbility] remove MageAbility'''

@@ Line 37: / Line 37: @@
 The first command adds the MageAbility tag to players with the tag MageClass, a score in UseStick of 1 or more, and without the tag AbilityCooldown. The execute command is used so we can test for multiple tags at once, as selectors will not do this on thier own. For example, @e[tag=Apples,tag=Bananas] is equivilent to @e[tag=Bananas] as the later parts override the previos ones rather than combining with them in any useful way. At the end of the first command there is a data tag.
 '''{SelectedItem:{id:"minecraft:carrot_on_a_stick",tag:{display:{Lore:["Right click to use your class ability."]}}}}'''
 This is used to check the nbt data of the target of the scoreboard command, so that only players who match with get the tag. This data tag checks that thier selected item (main hand item) is a carrot on a stick with lore "Right click to use your class ability". This enables us to check for different lore on a different item to give another effect.
-The second command is the same as the first command with Mage swapped for Tank, the second class in the example.
+The second command is the same as the first command with Mage swapped for Tank, the second class in this example.
-Notice the first two commands are the same except for @s[tag=MageClass] and adds the MageAbility tag in the first, but it is @s[tag=TankClass] and adds the TankAbility tag in the second.
+'''/scoreboard players tag @a[tag=MageAbility] remove MageAbility'''

@@ Line 4: / Line 4: @@
 ==Commands==
-This tutorial uses 4 commands.
+This tutorial uses 5 commands.
 *scoreboard (tagging, creating objectives, setting scores, testing scores)
 *execute