Ton's Guide to Create Events: Difference between revisions
Jump to navigation
Jump to search
TonTheKidRS (talk | contribs) No edit summary |
TonTheKidRS (talk | contribs) No edit summary |
||
Line 15: | Line 15: | ||
###; tag a[dx=-1,y='''Y-level of team join platform''',dz=-1] add event | ###; tag a[dx=-1,y='''Y-level of team join platform''',dz=-1] add event | ||
###: This command block adds players on top of it to the event tag, which makes some logistics easier. | ###: This command block adds players on top of it to the event tag, which makes some logistics easier. | ||
###: This command block should be Repeat, Conditional, and Always Active | ###: This command block should be Repeat, Conditional, and Always Active <br /> <br /> | ||
#; '''Solo Event''' | #; '''Solo Event''' | ||
## Under the spawn block of your event, place a command block. | ## Under the spawn block of your event, place a command block. | ||
Line 21: | Line 21: | ||
##; tag a[dx=-1,y='''Y-level of event platform''',dz=-1] add event | ##; tag a[dx=-1,y='''Y-level of event platform''',dz=-1] add event | ||
##: This command block adds players on top of it to the event tag, which makes some logistics easier. | ##: This command block adds players on top of it to the event tag, which makes some logistics easier. | ||
##: This command block should be Repeat, Unconditional, and Always Active | ##: This command block should be Repeat, Unconditional, and Always Active <br /> <br /> | ||
# Now you need to build a control room/area for the admin to run the event. <br /> You will need room for 4 buttons and a lever with space in between. <br /> There should be a large area for the command blocks to stay, preferably out of sight. | # Now you need to build a control room/area for the admin to run the event. <br /> You will need room for 4 buttons and a lever with space in between. <br /> There should be a large area for the command blocks to stay, preferably out of sight. | ||
# | # Command Block 1: | ||
#; eventset x='''coord''' y='''coord''' z='''coord''' world='''name'''. | #; eventset x='''coord''' y='''coord''' z='''coord''' world='''name'''. | ||
#: This sets the place where people end up when they do /event | #: This sets the place where people end up when they do /event | ||
#: This command block should be Impulse, Unconditional, and Triggered by Redstone | #: This command block should be Impulse, Unconditional, and Triggered by Redstone | ||
#: This command block should be powered by its own button. | #: This command block should be powered by its own button. <br /> <br /> | ||
# | # Command Block 2: | ||
#; ea true '''Event Name''' | #; ea true '''Event Name''' | ||
#: This opens the event and announces it in chat | #: This opens the event and announces it in chat | ||
#: This command block should be Impulse, Unconditional, and Triggered by Redstone | #: This command block should be Impulse, Unconditional, and Triggered by Redstone | ||
#: This command block should be powered by its own button. | #: This command block should be powered by its own button. <br /> <br /> | ||
# | # Command Block 3: | ||
#; gamemode adventure @a[tag=event] | #; gamemode adventure @a[tag=event] | ||
#: This makes sure all of the players in the event stay in adventure mode (or whatever gamemode is desired for the event) | #: This makes sure all of the players in the event stay in adventure mode (or whatever gamemode is desired for the event) | ||
#: This command block should be Repeat, Unconditional, and Triggered by Redstone | #: This command block should be Repeat, Unconditional, and Triggered by Redstone | ||
#: This command block should be powered by a lever so it is only on when the event is in progress. | #: This command block should be powered by a lever so it is only on when the event is in progress. <br /> <br /> | ||
# The next button controls a string of command blocks: | # The next button controls a string of command blocks: | ||
## The first set of command blocks should be: | ## The first set of command blocks should be: | ||
Line 44: | Line 44: | ||
###; tp @a[team=''Team 1''] ''x'' ''y'' ''z'' | ###; tp @a[team=''Team 1''] ''x'' ''y'' ''z'' | ||
###: This command teleports the 1st team to their area. | ###: This command teleports the 1st team to their area. | ||
###: This command block should be Impulse, Unconditional, and Triggered by Redstone | ###: This command block should be Impulse, Unconditional, and Triggered by Redstone <br /> <br /> | ||
### Command Block 2 | ### Command Block 2 | ||
###; tp @a[team=''Team 2''] ''x'' ''y'' ''z'' | ###; tp @a[team=''Team 2''] ''x'' ''y'' ''z'' | ||
###: This command teleports the 1st team to their area. | ###: This command teleports the 1st team to their area. | ||
###: This command block should be Impulse, Unconditional, and Triggered by Redstone | ###: This command block should be Impulse, Unconditional, and Triggered by Redstone <br /> <br /> | ||
##; Solo Event | ##; Solo Event | ||
### Solo Events with one spawn: | ### Solo Events with one spawn: | ||
###; tp @a[tag=event] ''x'' ''y'' ''z'' | ###; tp @a[tag=event] ''x'' ''y'' ''z'' | ||
###: This command teleports all players in the event to one location. | ###: This command teleports all players in the event to one location. | ||
###: This command block should be Impulse, Unconditional, and Triggered by Redstone | ###: This command block should be Impulse, Unconditional, and Triggered by Redstone <br /> <br /> | ||
### Solo Events with spread players: | ### Solo Events with spread players: | ||
###; spreadplayers ''Center X'' ''Center Z'' ''Min Distance Between Target'' ''Max Distance Between Targets'' false @a[tag=event] | ###; spreadplayers ''Center X'' ''Center Z'' ''Min Distance Between Target'' ''Max Distance Between Targets'' false @a[tag=event] | ||
###: This command spreads the players randomly around the map based on certain predefined settings. | ###: This command spreads the players randomly around the map based on certain predefined settings. | ||
###: This command block should be Impulse, Unconditional, and Triggered by Redstone | ###: This command block should be Impulse, Unconditional, and Triggered by Redstone <br /> <br /> | ||
## The second set of command blocks should be: | ## The second set of command blocks should be: | ||
##; give @a[tag=event] ''item'' | ##; give @a[tag=event] ''item'' | ||
##: This command give all players in the event certain items. | ##: This command give all players in the event certain items. | ||
##: This command block should be Impulse, Unconditional, and Triggered by Redstone | ##: This command block should be Impulse, Unconditional, and Triggered by Redstone | ||
##: Note: You will need 1 command block for every different item you want to give to the players. | ##: Note: You will need 1 command block for every different item you want to give to the players. <br /> <br /> | ||
## The last command block in this string closes the event so no one can join mid event: | ## The last command block in this string closes the event so no one can join mid event: | ||
##; ea false | ##; ea false | ||
##: This command block should be Impulse, Unconditional, and Triggered by Redstone | ##: This command block should be Impulse, Unconditional, and Triggered by Redstone <br /> <br /> | ||
# The next command block string is again all powered by one button: | # The next command block string is again all powered by one button: | ||
## Command Block 1: | ## Command Block 1: | ||
##; endevent | ##; endevent | ||
##: This command ends the event, clears the players inventory, and returns them to the normal world. | ##: This command ends the event, clears the players inventory, and returns them to the normal world. | ||
##: This command block should be Impulse, Unconditional, and Triggered by Redstone | ##: This command block should be Impulse, Unconditional, and Triggered by Redstone <br /> <br /> | ||
## Command Block 2: | ## Command Block 2: | ||
##; tag @a[tag=event] remove event | ##; tag @a[tag=event] remove event | ||
##: This command removes the event tag from everyone. | ##: This command removes the event tag from everyone. | ||
##: This command block should be Impulse, Unconditional, and Triggered by Redstone | ##: This command block should be Impulse, Unconditional, and Triggered by Redstone <br /> <br /> | ||
## Command Block 3: | ## Command Block 3: | ||
##; team leave @a | ##; team leave @a | ||
##: This command removes all players from any team. | ##: This command removes all players from any team. | ||
##: This command block should be Impulse, Unconditional, and Triggered by Redstone | ##: This command block should be Impulse, Unconditional, and Triggered by Redstone | ||
If you have any other questions fell free to contact me on the Forum, Discord, or In-Game |
Revision as of 21:37, 11 May 2020
In this I will be discussing how to create an event from a technical point of view. Note: this guide uses command blocks that are configured to run all the commands necessary for the event to make the admins lives easier.
Once you have built the physical event, I suggest building some sort of control room for the Admin to go be in during the event.
- Build a spawn or entrance room for people when the first join the event.
- Team Event
- In your spawn room, select areas for people to join the event.
These should be 3x3 areas obviously separated.
Under the center of the 3x3s, you want to place 2 command blocks facing down.
- The top command block should be:
- team join Team @a[dx=-1,y=Y-level of team join platform,dz=-1]
- This command block adds players on top of it to the team they want to join
- This command block should be Repeat, Unconditional, and Always Active
- The bottom command block should be:
- tag a[dx=-1,y=Y-level of team join platform,dz=-1] add event
- This command block adds players on top of it to the event tag, which makes some logistics easier.
- This command block should be Repeat, Conditional, and Always Active
- The top command block should be:
- Solo Event
- Under the spawn block of your event, place a command block.
- This command block should be:
- tag a[dx=-1,y=Y-level of event platform,dz=-1] add event
- This command block adds players on top of it to the event tag, which makes some logistics easier.
- This command block should be Repeat, Unconditional, and Always Active
- Now you need to build a control room/area for the admin to run the event.
You will need room for 4 buttons and a lever with space in between.
There should be a large area for the command blocks to stay, preferably out of sight. - Command Block 1:
- eventset x=coord y=coord z=coord world=name.
- This sets the place where people end up when they do /event
- This command block should be Impulse, Unconditional, and Triggered by Redstone
- This command block should be powered by its own button.
- Command Block 2:
- ea true Event Name
- This opens the event and announces it in chat
- This command block should be Impulse, Unconditional, and Triggered by Redstone
- This command block should be powered by its own button.
- Command Block 3:
- gamemode adventure @a[tag=event]
- This makes sure all of the players in the event stay in adventure mode (or whatever gamemode is desired for the event)
- This command block should be Repeat, Unconditional, and Triggered by Redstone
- This command block should be powered by a lever so it is only on when the event is in progress.
- The next button controls a string of command blocks:
- The first set of command blocks should be:
- Team Event
- Command Block 1:
- tp @a[team=Team 1] x y z
- This command teleports the 1st team to their area.
- This command block should be Impulse, Unconditional, and Triggered by Redstone
- Command Block 2
- tp @a[team=Team 2] x y z
- This command teleports the 1st team to their area.
- This command block should be Impulse, Unconditional, and Triggered by Redstone
- Solo Event
- Solo Events with one spawn:
- tp @a[tag=event] x y z
- This command teleports all players in the event to one location.
- This command block should be Impulse, Unconditional, and Triggered by Redstone
- Solo Events with spread players:
- spreadplayers Center X Center Z Min Distance Between Target Max Distance Between Targets false @a[tag=event]
- This command spreads the players randomly around the map based on certain predefined settings.
- This command block should be Impulse, Unconditional, and Triggered by Redstone
- The second set of command blocks should be:
- give @a[tag=event] item
- This command give all players in the event certain items.
- This command block should be Impulse, Unconditional, and Triggered by Redstone
- Note: You will need 1 command block for every different item you want to give to the players.
- The last command block in this string closes the event so no one can join mid event:
- ea false
- This command block should be Impulse, Unconditional, and Triggered by Redstone
- The first set of command blocks should be:
- The next command block string is again all powered by one button:
- Command Block 1:
- endevent
- This command ends the event, clears the players inventory, and returns them to the normal world.
- This command block should be Impulse, Unconditional, and Triggered by Redstone
- Command Block 2:
- tag @a[tag=event] remove event
- This command removes the event tag from everyone.
- This command block should be Impulse, Unconditional, and Triggered by Redstone
- Command Block 3:
- team leave @a
- This command removes all players from any team.
- This command block should be Impulse, Unconditional, and Triggered by Redstone
- Command Block 1:
If you have any other questions fell free to contact me on the Forum, Discord, or In-Game