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 has been archived by the owner on Apr 16, 2023. It is now read-only.
As many users cannot see query connections, it is desirable to automatically establish an additional client connection. This allows users to see and interact with the framework more easily.
All events invoked by this connection should be redirected to the query event dispatching mechanism to avoid parallel data/event flows.
Commands shall not be sent using the voice connection either - as it is supposed to share the same identity, it will show up as the same chat window anyways.
The text was updated successfully, but these errors were encountered:
As many users cannot see query connections, it is desirable to automatically establish an additional client connection. This allows users to see and interact with the framework more easily.
All events invoked by this connection should be redirected to the query event dispatching mechanism to avoid parallel data/event flows.
Commands shall not be sent using the voice connection either - as it is supposed to share the same identity, it will show up as the same chat window anyways.
The text was updated successfully, but these errors were encountered: