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 22: | Line 22: | ||
##: 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 | ||
# | # 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. | ||
# The first command block should be: | # The first command block should be: | ||
#; 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. | |||
# The next command block: | # The next command block: | ||
#; 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. | |||
# The next command block: | # The next command block: | ||
#; 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. | |||
# The next button controls a string of command blocks: | |||
## The first command should be: | |||
##; tp @a[team=''Team 1''] ''x'' ''y'' ''z'' | |||
##: This command teleports the 1st team to their area. | |||
##: Note: If you are doing a solo event where all players should spawn at the same place then this command should be used instead: | |||
###; tp @a[tag=event] ''x'' ''y'' ''z'' | |||
'''WIP''' | '''WIP''' |
Revision as of 21:15, 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:
- In your spawn room, select areas for people to join the event.
- 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. - The first command block should be:
- 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.
- The next command block:
- 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.
- The next command block:
- 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 command should be:
- tp @a[team=Team 1] x y z
- This command teleports the 1st team to their area.
- Note: If you are doing a solo event where all players should spawn at the same place then this command should be used instead:
- tp @a[tag=event] x y z
- The first command should be:
WIP