Bagu
03-02-2024, 10:04 AM
Since newer builds include a ZString Command "End String" to close Strings or go to next, which is esspecially useful for cutscene messages...
...I found it would make sense to have a command that disables manual speed up message advancing or skipping messages.
So quest developers could create precise and sychronized (screen performance, music, sfx, screen messages) cinematic cutscenes, that ignore button inputs.
Currently I use a very simple generic script for that function.
It disables the "Message Freeze ScreenAction" Rule, if it's enabled and enables it otherwise.
So I use it in combination with a custom Button Disabler script.
But having String commands for that features would be cool.
Especially the "Wait" Command might be very helpful...
...it would delay string advancing (so also reading the "End String" Command)
So you could decide who long a string remains (after advancing), before changing to next on (or End)
I know you can also do simialar things by changing the Message Speed, but this always requires a second Command to restore previous Speed
(within concted Strings). And That's unnecessary effort.
Almost forgot to mention: Yes, generic scripts, called by SC Codes can write to String related Quest Rules, without any issues.
...very good to know :)
...I found it would make sense to have a command that disables manual speed up message advancing or skipping messages.
So quest developers could create precise and sychronized (screen performance, music, sfx, screen messages) cinematic cutscenes, that ignore button inputs.
Currently I use a very simple generic script for that function.
It disables the "Message Freeze ScreenAction" Rule, if it's enabled and enables it otherwise.
So I use it in combination with a custom Button Disabler script.
But having String commands for that features would be cool.
Especially the "Wait" Command might be very helpful...
...it would delay string advancing (so also reading the "End String" Command)
So you could decide who long a string remains (after advancing), before changing to next on (or End)
I know you can also do simialar things by changing the Message Speed, but this always requires a second Command to restore previous Speed
(within concted Strings). And That's unnecessary effort.
Almost forgot to mention: Yes, generic scripts, called by SC Codes can write to String related Quest Rules, without any issues.
...very good to know :)