You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jul 24, 2020. It is now read-only.
Get an input prompt working, however my main concern is the extra usage of IO, as well as the interference with the sonic boom module, which allows logging to be less costly. If this has impact on throughput, I will not include it as a v1 feature and instead just create a CLI rcon client which relays logs. If such a thing is enabled, the default recommendation for logs will be for it to be stored in a file instead, however both stdout and a file can be used but the config will have a comment warning against such a thing.
Ideas for it:
Whenever something gets logged, it freezes the input prompt, buffers what was in the middle of being typed (if any), moves the cursor before the prompt (\r), logs, moves the cursor back to where it was and then puts the stdin text there.
Get an input prompt working, however my main concern is the extra usage of IO, as well as the interference with the sonic boom module, which allows logging to be less costly. If this has impact on throughput, I will not include it as a v1 feature and instead just create a CLI rcon client which relays logs. If such a thing is enabled, the default recommendation for logs will be for it to be stored in a file instead, however both stdout and a file can be used but the config will have a comment warning against such a thing.
Ideas for it:
Whenever something gets logged, it freezes the input prompt, buffers what was in the middle of being typed (if any), moves the cursor before the prompt (
\r), logs, moves the cursor back to where it was and then puts the stdin text there.