This command would allow you to /tellraw except for the fact that it would stay for a certain amount of time, then disappear from chat completely, or from a "second chat," which is disabled by default. The "second chat" settings would be found in Multiplayer, and has several different modes. These would be "Combine with main chat," "Bottom right," and "Hide." There would also be an option to place all command block output (e.g. "Block Placed") and command related things (like /say, /tellraw, setting a command block's command, etc.) inside of the second chat. The /tellwaitraw commands would always stay at the bottom, in order of execution. Second chat, when the "Hide" setting is selected, will still hide the command block output and setting a command block's command, but executed commands that say something specifically to the chat, like /say, /tellraw, and /tellwaitraw, will still show up in normal chat.
The <player> parameter tells the command who to show the message to.
The <seconds shown> parameter tells the game engine to show the message to the player described before for a certain amount of time (in seconds). Any value higher than 3600 lasts infinitely.
The <condition> parameter would check the player being sent the message meets a certain condition, like [score_Level=1,score_Level_min=1], and the message disappears when the condition is no longer met, checked every 5 seconds.
The <raw JSON message> parameter uses JSON format to tell a message, exactly similarly to /tellraw
You do realize you put in two different suggestions in the same thread. That's sorta agenst the rules but anyway I think it would be and OK idea but why do you need a brand new command that does the same thing as tellraw except with a delay. Mojang doesn't need to code in a whole NEW command just add onto the existing one. The second chat idea is pretty interesting but you do realize in normal minecraft there's a gamerule that stops command blocks from giving out feedback.
For the tellwaitraw, you could have two scoreboards, Level and coins. With the tellwaitraw, you can use /tellwaitraw score_Level=1,score_Level_min=1,score_coins_min=200 JSON_message. The JSON_message would, on click, increase the level and take 200 coins, then disappear, as the conditions are no longer met. Then a new tellwaitraw would be run just once using a testfor (checking for level 2) and a comparator leading into a command block containing a command that is formatted as: /tellwaitraw score_Level=2,score_Level_min=2,score_coins_min=800 JSON_message.
For the second chat, I know about /gamerule commandBlockOutput false, but this would also hide other things (configurable), like setting a command. This would also work well to keep all console/admin/important chats in one place.
Now your bringing in coins?! So your making a lot of random things that minecraft doesn't really need. Again if mojang did add this all you need is just to edit the existing /tellraw command. So I have pretty much no support for the /tellwaitraw but the second chat idea is fine.
No, @TheDiamondDragonKing, the coins and level are Scoreboards. I am using them as example conditions and commands. They are already "in" minecraft as soon as you do:
Yeah I understand about everything now and it wasn't a new feature. But honestly have full support for the second chat but lets be realistic here, why make a new command that does the SAME THING as the /tellraw command except for the delay part! It honestly is just a waste of time coding in a new command insted of upgrading the current /tellraw command which would take a lot less time.
/tellraw and /title are very similar in nature. What we are doing is similar to what they did when they made the /title or /tellraw command, whichever came after. They are basically the same except for a few things (position, size, clickability). I believe this is what AThingWithAThing meant. If not, AThingWithAThing, please correct me.
This needs more information! Please add more or no support!
Please give me specific feedback on how I can improve my thread.
You do realize you put in two different suggestions in the same thread. That's sorta agenst the rules but anyway I think it would be and OK idea but why do you need a brand new command that does the same thing as tellraw except with a delay. Mojang doesn't need to code in a whole NEW command just add onto the existing one. The second chat idea is pretty interesting but you do realize in normal minecraft there's a gamerule that stops command blocks from giving out feedback.
For the tellwaitraw, you could have two scoreboards, Level and coins. With the tellwaitraw, you can use /tellwaitraw <player> score_Level=1,score_Level_min=1,score_coins_min=200 JSON_message. The JSON_message would, on click, increase the level and take 200 coins, then disappear, as the conditions are no longer met. Then a new tellwaitraw would be run just once using a testfor (checking for level 2) and a comparator leading into a command block containing a command that is formatted as: /tellwaitraw <player> score_Level=2,score_Level_min=2,score_coins_min=800 JSON_message.
For the second chat, I know about /gamerule commandBlockOutput false, but this would also hide other things (configurable), like setting a command. This would also work well to keep all console/admin/important chats in one place.
Now your bringing in coins?! So your making a lot of random things that minecraft doesn't really need. Again if mojang did add this all you need is just to edit the existing /tellraw command. So I have pretty much no support for the /tellwaitraw but the second chat idea is fine.
No, @TheDiamondDragonKing, the coins and level are Scoreboards. I am using them as example conditions and commands. They are already "in" minecraft as soon as you do:
Yeah I understand about everything now and it wasn't a new feature. But honestly have full support for the second chat but lets be realistic here, why make a new command that does the SAME THING as the /tellraw command except for the delay part! It honestly is just a waste of time coding in a new command insted of upgrading the current /tellraw command which would take a lot less time.
/tellraw and /title are very similar in nature. What we are doing is similar to what they did when they made the /title or /tellraw command, whichever came after. They are basically the same except for a few things (position, size, clickability). I believe this is what AThingWithAThing meant. If not, AThingWithAThing, please correct me.
Your confusing me but technicly speaking tittle and tellraw are pretty much the same except you can only make one clickable and one appears on the screen. Are you not including the fact that tittle nor tellraw has anything to do with delay and that is exactly what /tellwaitraw does? Everything else you just said is the factors of the "second chat" not the command.
the /tellwaitraw, unlike other chats and /tellraw, does not fade until the time reaches 0 or the condition is no longer met, and when it fades, it disappears completely, to avoid being clicked again (if clickable) and can be used to give a set of directions or coordinates, and you never have to open your chat again to see it. This would also work effectively for server join messages. (i.e. The message you receive in chat when you join a server with essentials)
Yeah I understand about everything now and it wasn't a new feature. But honestly have full support for the second chat but lets be realistic here, why make a new command that does the SAME THING as the /tellraw command except for the delay part! It honestly is just a waste of time coding in a new command insted of upgrading the current /tellraw command which would take a lot less time.
I agree with DIamondKing, theres no need to put mojang through all the work of making a whole new command, just make it so that the /tallraw command can have a "wait" tag.
And also, theres no need for a second chat, if this is just a delayed input of text it doesn't need another chat taking up the gameplay screen.
/tellraw @p {"text":"Hi there!!","wait":10}
Time is in ticks
What would this do?
This command would allow you to /tellraw except for the fact that it would stay for a certain amount of time, then disappear from chat completely, or from a "second chat," which is disabled by default. The "second chat" settings would be found in Multiplayer, and has several different modes. These would be "Combine with main chat," "Bottom right," and "Hide." There would also be an option to place all command block output (e.g. "Block Placed") and command related things (like /say, /tellraw, setting a command block's command, etc.) inside of the second chat. The /tellwaitraw commands would always stay at the bottom, in order of execution. Second chat, when the "Hide" setting is selected, will still hide the command block output and setting a command block's command, but executed commands that say something specifically to the chat, like /say, /tellraw, and /tellwaitraw, will still show up in normal chat.
What parameters would the command take?
Usage: /tellwaitraw <player> <seconds shown|condition> <raw JSON message>
The <player> parameter tells the command who to show the message to.
The <seconds shown> parameter tells the game engine to show the message to the player described before for a certain amount of time (in seconds). Any value higher than 3600 lasts infinitely.
The <condition> parameter would check the player being sent the message meets a certain condition, like [score_Level=1,score_Level_min=1], and the message disappears when the condition is no longer met, checked every 5 seconds.
The <raw JSON message> parameter uses JSON format to tell a message, exactly similarly to /tellraw
Support:
Small Support for the Second Chat @TheDiamondDragonKing
Support @AThingWithAThing
Responses and replies
This needs more information! Please add more or no support!
Please give me specific feedback on how I can improve my thread.
You do realize you put in two different suggestions in the same thread. That's sorta agenst the rules but anyway I think it would be and OK idea but why do you need a brand new command that does the same thing as tellraw except with a delay. Mojang doesn't need to code in a whole NEW command just add onto the existing one. The second chat idea is pretty interesting but you do realize in normal minecraft there's a gamerule that stops command blocks from giving out feedback.
Small Support for the Second Chat
@TheDiamondDragonKing
For the tellwaitraw, you could have two scoreboards, Level and coins. With the tellwaitraw, you can use /tellwaitraw <player> score_Level=1,score_Level_min=1,score_coins_min=200 JSON_message. The JSON_message would, on click, increase the level and take 200 coins, then disappear, as the conditions are no longer met. Then a new tellwaitraw would be run just once using a testfor (checking for level 2) and a comparator leading into a command block containing a command that is formatted as: /tellwaitraw <player> score_Level=2,score_Level_min=2,score_coins_min=800 JSON_message.
For the second chat, I know about /gamerule commandBlockOutput false, but this would also hide other things (configurable), like setting a command. This would also work well to keep all console/admin/important chats in one place.
Thanks!
This will be edited into the original message.
Now your bringing in coins?! So your making a lot of random things that minecraft doesn't really need. Again if mojang did add this all you need is just to edit the existing /tellraw command. So I have pretty much no support for the /tellwaitraw but the second chat idea is fine.
No, @TheDiamondDragonKing, the coins and level are Scoreboards. I am using them as example conditions and commands. They are already "in" minecraft as soon as you do:
Yeah I understand about everything now and it wasn't a new feature. But honestly have full support for the second chat but lets be realistic here, why make a new command that does the SAME THING as the /tellraw command except for the delay part! It honestly is just a waste of time coding in a new command insted of upgrading the current /tellraw command which would take a lot less time.
Explain to me how it uses the /title command please, I am not following.
/tellraw and /title are very similar in nature. What we are doing is similar to what they did when they made the /title or /tellraw command, whichever came after. They are basically the same except for a few things (position, size, clickability). I believe this is what AThingWithAThing meant. If not, AThingWithAThing, please correct me.
Your confusing me but technicly speaking tittle and tellraw are pretty much the same except you can only make one clickable and one appears on the screen. Are you not including the fact that tittle nor tellraw has anything to do with delay and that is exactly what /tellwaitraw does? Everything else you just said is the factors of the "second chat" not the command.
the /tellwaitraw, unlike other chats and /tellraw, does not fade until the time reaches 0 or the condition is no longer met, and when it fades, it disappears completely, to avoid being clicked again (if clickable) and can be used to give a set of directions or coordinates, and you never have to open your chat again to see it. This would also work effectively for server join messages. (i.e. The message you receive in chat when you join a server with essentials)
I agree with DIamondKing, theres no need to put mojang through all the work of making a whole new command, just make it so that the /tallraw command can have a "wait" tag.
And also, theres no need for a second chat, if this is just a delayed input of text it doesn't need another chat taking up the gameplay screen.
/tellraw @p {"text":"Hi there!!","wait":10} Time is in ticksNo support.
My Youtube Channel: https://www.youtube.com/channel/UCd_JoIjCmRRjG7S5vR4hYig/