Hello redstoners and map makers.
I was working on my PvP map and I thought it would be cool if Jeb or Dinnerbone added some new command block commands that would be really helpful for you, map makers.
So, there are the commands I have in mind:
-Output and Input:
That command would let you output a redstone signal from a command block to another probably far away from this, using a certain code. Using a random code that I named "pig" I can make wireless circuits easily, if you wrote something like:
If the C.B. number 1 was activated by redstone, the second one will output a signal, even if it is far far away.
-"Mark" command:
Its very useful for PvP maps, and Team Vs Team maps... Basicly you can tag any player or a group of players with a certain tag, that can say who is from team blue and who is from team red. You can also tag someone with more than one tag. For example:
Tag #1: blue and red - the teams.
Tag #2: Who is dead, whos not.
Tag #3: Who is with the bomb, whos not.
Tag #4: Whos the admin.
That would be the command:
/mark @p "team" blue
/mark @a[m=1] "admin" yes
/mark @r "bomb" true
/mark @a[m=1] and "admin" == not "dead" yes
Because tag with levels is not enough!
-"If" prefix implemented:
If you already know some codes like Java, ActionScript or ComputerCraft language, you must know what "if" prefix is... For those who don't know yet:
If makes any determinated fuction true or false, IF some other thing happens. Example: If this happens, this will happen then... With that I could make a command block that says:
/say "Its raining!!!" if weather==rain
/time set 0 if time>12500
/weather clear if weather=~clear
/input "door" if output "key"==true
/say Time's up if output "playeronline"==ture and output "time"==true
etc etc etc
- "and", "or" and "else":
"and" and "or" are from scripts that already exist, and they are auto-explainable. Else is used when the function "if" is not true. Like:
/say "Hello!" if output "cookie" == true
Output is true:
Result: The chat will say hello because the "cookie" code is true at the momentBut you can add an "else":
/say "Hello!" if output "cookie" == true else /say "Bye bye!"
Output is false:
Result: The code "cookie" is not true, so it won't say "Hello!", it will say "Bye bye!"
If you have any suggestions of codes or commands you can post I will aprecciate.
Give me your feedback, so I will know if you liked my ideas or not.
Bye. :-( ):
I have a suggestion for a command that I think Adventure map makers would LOVE.
Similar to your 'Tag' command, it would be nice to have a 'Store' comand.
/store (playername) (playerx)
It stores what ever player name you wish using existing comands (closeset player in particular) in a slot designated by the comand block.
For example:
On my private SMP server, we wanted to make a sky rail system for visitors and newcomers in order to show off the server. But we came up with a better idea... What if you could use comand blocks to send them around to areas you designate.
Player Newcomer enters the server
Newcomer clicks the 'Tour' button which activates a comand block that stores the name Newcomer in server memory or file as Player 12.
/store @p Player12
The next comand block puts Player 12 into Adventure mode (for safety reasons).
The next comand block in line uses the tp comand to transport Player 12 to a certian area far away. (More than likely far enough away from the original comand block that it is no longer rendered and can't continue activating comands)
They tp above a pressure plate that sends a delayed signal to the next comand block, giving Player 12 (Newcomer) a little time to explore before the comand block is finaly activated, sending Player 12 to the next area.
This continues untill the tour is complete, giving any directions to Newcomer along the way with acitvated comand blocks, and the last few comand blocks would put Player 12 back into Survival mode, TP them back to the begining, and clear the Player 12 slot so it could be used at another time.
Basicly, it alows you to enter generic player identifications for specific reasons that can be activated with out needing to re-edit each block every time. Turn Newcomer into a Variable that can be called upon easier.
If you understand what I am getting at and can explain it better, feel free.
Actually, now that I think about it, your Tag idea would work even better. You could Tag Newcomer, and just reference the tag in each successive command block, and remove the Tag when done.
Rollback Post to RevisionRollBack
To post a comment, please login or register a new account.
I was working on my PvP map and I thought it would be cool if Jeb or Dinnerbone added some new command block commands that would be really helpful for you, map makers.
So, there are the commands I have in mind:
-Output and Input:
That command would let you output a redstone signal from a command block to another probably far away from this, using a certain code. Using a random code that I named "pig" I can make wireless circuits easily, if you wrote something like:
If the C.B. number 1 was activated by redstone, the second one will output a signal, even if it is far far away.
-"Mark" command:
Its very useful for PvP maps, and Team Vs Team maps... Basicly you can tag any player or a group of players with a certain tag, that can say who is from team blue and who is from team red. You can also tag someone with more than one tag. For example:
Tag #1: blue and red - the teams.
Tag #2: Who is dead, whos not.
Tag #3: Who is with the bomb, whos not.
Tag #4: Whos the admin.
That would be the command:
Because tag with levels is not enough!
-"If" prefix implemented:
If you already know some codes like Java, ActionScript or ComputerCraft language, you must know what "if" prefix is... For those who don't know yet:
If makes any determinated fuction true or false, IF some other thing happens. Example: If this happens, this will happen then... With that I could make a command block that says:
- "and", "or" and "else":
"and" and "or" are from scripts that already exist, and they are auto-explainable. Else is used when the function "if" is not true. Like:
If you have any suggestions of codes or commands you can post
Give me your feedback, so I will know if you liked my ideas or not.
Bye. :-( ):
Similar to your 'Tag' command, it would be nice to have a 'Store' comand.
/store (playername) (playerx)
It stores what ever player name you wish using existing comands (closeset player in particular) in a slot designated by the comand block.
For example:
On my private SMP server, we wanted to make a sky rail system for visitors and newcomers in order to show off the server. But we came up with a better idea... What if you could use comand blocks to send them around to areas you designate.
Player Newcomer enters the server
Newcomer clicks the 'Tour' button which activates a comand block that stores the name Newcomer in server memory or file as Player 12.
/store @p Player12
The next comand block puts Player 12 into Adventure mode (for safety reasons).
The next comand block in line uses the tp comand to transport Player 12 to a certian area far away. (More than likely far enough away from the original comand block that it is no longer rendered and can't continue activating comands)
They tp above a pressure plate that sends a delayed signal to the next comand block, giving Player 12 (Newcomer) a little time to explore before the comand block is finaly activated, sending Player 12 to the next area.
This continues untill the tour is complete, giving any directions to Newcomer along the way with acitvated comand blocks, and the last few comand blocks would put Player 12 back into Survival mode, TP them back to the begining, and clear the Player 12 slot so it could be used at another time.
Basicly, it alows you to enter generic player identifications for specific reasons that can be activated with out needing to re-edit each block every time. Turn Newcomer into a Variable that can be called upon easier.
If you understand what I am getting at and can explain it better, feel free.