I have a title that has a fade and stay. I think the comparator should not turn on until the command is finished. I set a 5 second time for title. the comparator should turn on after the 5 seconds. If I have a sequence of text that requires more than one line, it would be nice to chain the command blocks with simple comparators. For now, I will have to set up independent timers between to make these work.
"text on screen here" *pause to read* "next line of text on screen here" *pause to read*
I want a few sentences of text on the screen. Currently, I have to place a command block with title command and delay seconds. Then a bank of repeaters for a delay of the next line. Then place another command block. Repeat until story is told. The pause is established in the title command and the next line of text has to be passed at the same pause length to make the next line start on the screen.
I tried to use a command block, then comparator, then command block, repeat. It flashes all text almost at once. I was in hopes that the "true" signal would be sent after the command was completed. then I would not need a million repeaters between each command block.
This can be easily achieved with scoreboard objectives. Connect the title commands to a fill clock but add an execute @e[score_timer_min=0,score_timer=0] infront of the title command for the first line, and change the 0's to lineNumber*20*delay for each following line. So 100 for the second line, and 200 for the third and so on. At the end of the fill clock add 1 to the timer objective.
Wow, Sometimes it is hard to see the big picture when trying to overcome an issue. I actually did this for the first line of text as a countdown to 0 timer. I did not think to assign different lines to different values. I was going to place the timer between each line. Then started weighing the cost verses repeaters. I like you solution. It is still a workaround. I think it would still be a good idea to make the comparator trigger true after completion of code. I know that this would then be used/abused as a redstone timer for limitless options.
hmm, The Idea could be interesting, but as we all know Command blocks aren't exactly for people who don't know or don't feel like learning a lot about MC logic and mechanics.
So what I'm saying is, for map creators and other redstone nerds, commands like these can be learned via MCwiki or forumwise, or even on your own, normal people wouldn't even bother to search up such a command, making this feauture suefull only for certain people.
Rollback Post to RevisionRollBack
While alive, you have a 100% chance of dying, so don't sweat it.
Roleplay characters:
Death (me)
War
Pestilence
Famine
"Yet another stands before me... Then so be it. For the curse of life, is the curse of want. And so, you peer... Into the fog, in hope of answers."
Roleplay characters:
Death (me)
War
Pestilence
Famine
I want a few sentences of text on the screen. Currently, I have to place a command block with title command and delay seconds. Then a bank of repeaters for a delay of the next line. Then place another command block. Repeat until story is told. The pause is established in the title command and the next line of text has to be passed at the same pause length to make the next line start on the screen.
I tried to use a command block, then comparator, then command block, repeat. It flashes all text almost at once. I was in hopes that the "true" signal would be sent after the command was completed. then I would not need a million repeaters between each command block.
So what I'm saying is, for map creators and other redstone nerds, commands like these can be learned via MCwiki or forumwise, or even on your own, normal people wouldn't even bother to search up such a command, making this feauture suefull only for certain people.
Roleplay characters:
Death (me)
War
Pestilence
Famine