-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add wa_purge #3
Labels
Comments
Doing this alongside making wa_enable halt the server from sending useless net messages |
Vurv78
added a commit
that referenced
this issue
Apr 30, 2021
* Added wa_purge. Instantly kills and stops receiving data from every currently running stream on your client. * Added setRadius, allows you to set the radius in which the stream can be heard from. Along side this comes the convar: * wa_radius_max * On the lua (api) side, added static methods to streamline the stuff going on in the code. You should check out all of the new methods. * wa_enable now has the same functionality as doing wa_purge if you set it to 0, no longer receiving any net messages from currently running streams and any future streams until you reenable it. Fixes #3 #4 #6
Vurv78
added a commit
that referenced
this issue
Apr 30, 2021
* Refactor a lot of stuff & Add a lot of functionality * Added wa_purge. Instantly kills and stops receiving data from every currently running stream on your client. * Added setRadius, allows you to set the radius in which the stream can be heard from. Along side this comes the convar: * wa_radius_max * On the lua (api) side, added static methods to streamline the stuff going on in the code. You should check out all of the new methods. * wa_enable now has the same functionality as doing wa_purge if you set it to 0, no longer receiving any net messages from currently running streams and any future streams until you reenable it. Fixes #3 #4 #6 * Remove unused variables
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
Just loop through all clientside wa receivers in the Audios table and run IGmodAudioChannel:Stop() on them.
Also need to check the Enabled convar in the
wa_modify
net message so people can't modify audios if you set wa_enable to 0 after they made the object, which would cause errors with these stopped bass objects.The text was updated successfully, but these errors were encountered: