-
-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Pass RATSIGNAL as command parameter #51
Labels
Comments
alterNERDtive
added a commit
that referenced
this issue
Jul 31, 2020
Basically done, waiting for next VA release. |
Turns out invoking commands from the command line is not thread safe and can run havok all over your parameters if invoked in rapid succession. Will have to halt this for now. |
alterNERDtive
added a commit
that referenced
this issue
Jul 31, 2020
Passing parameters to VoiceAttack through the command line is not thread safe. For RATSIGNALS coming in in rapid succession (either because, well, several cases at once or when using an IRC bouncer, like I do) it completely messes up the data. see #51
Obsolete, see #62. Invoking a helper tool and doing IPC instead. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
VoiceAttack β 1.8.6.5 supports this.
Leave current way of passing through a file in, mark as deprecated.
The text was updated successfully, but these errors were encountered: