First, I apologize for the weird and probably undescriptive topic name, but I can't think of a better phrase to describe it.

I'm trying to make a system where, instead of text being displayed for a certain interval (like it does in StarCraft normally), it stays on the screen indefinitely until the player presses a key.
In other words, something like this:

where the player presses a button to advance each piece of text, allowing them to read it at their own pace.


Getting the text to stay on the screen until a key is pressed isn't the problem; I accomplished that pretty easily by triggers that looked something like this:



The problem arises when I have multiple Transmission actions; since each Transmission acts like a Wait, the 9999999 millisecond duration that I use to make the text stay on the screen causes a huge wait block, which results in only one Transmission action ever being run. How should I solve this, and get it to work properly? Is there a way to have text stay on the screen indefinitely, without using the Transmission action?

I'm sorry if that was confusing; if you need any details or have any questions, go ahead and ask.

Thanks in advance!

Have you considered "Display Text Message"? 11 new lines to clear the screen, and apply the text you want to show after clearing the screen.

This will, of course, hinder conversation between players. You can set it to a somewhat slow refresh rate so players get a decent glimpse of others talking most of the time.

This is a single-player map I'm making, so the second point is moot.

The problem with Display Text Message is that any text displayed with it won't stay on the screen longer than a few seconds. I need it to stay displayed until a key is pressed. I've tried just refreshing it every few seconds, but the text flashes briefly whenever it's refreshed. I'd like to avoid that if possible, as it looks unpleasant.

It shouldn't flash, unless Single Player handles Display Text Message differently.

If it's not a problem to mass refresh, just do that. Create 11 new lines at the beginning of each trigger cycle, and whenever text should appear, refresh it every trigger loop as well.



\n is just notation for a new line. Don't literally enter \n
The second trigger should have whatever condition you're using to determine if the text should be displayed; I used a switch purely for example's sake.

In single player you can skip transmission and wait times by pressing ESC. So make the key to be pressed ESC and problem should be solved.

Ah, that should work. I'll test that out now and see if there's any problems. Thanks!