Sebastian Neubauer

Is what you need implemented in #231? :)

If it is about command arguments, I can help out, we have [a list of them](https://github.com/ReSpeak/tsdeclarations/blob/72656072ccbd2d9e84b81ec24dfcd6c5f69bd0c6/Messages.toml#L628-L630). Your channel property names might not match with the names that the server expects...

Hi, I have to say the same as on #61, I don’t see anything wrong with the code you posted. We have a testcase that might be helpful, you can...

It is the right function. You’re right, it only returns a packet and that packet then needs to be sent to a connection. (It’s a two-step process otherwise all these...

Hi, on the client, the shared secret is calculated through `next_public_key * client_private_key`. Therefore, the shared secret on the server needs to be calculated symmetrically with `next_private_key * client_public_key`. The...

As you say, the next public key of a block is computed through ``` next_public_key = public_key * clamp(sha512(block[1...]) [0..32]) + parent_public_key ``` To compute the public key, you need...

Thanks for the report. TeaSpeak sends the `notifypermissionlist` before the `initserver`, which caused the weird error message. Apart from that, some arguments are not sent on TeaSpeak (e.g. the PermissionId,...

> Should I open a separate issue or keep discussing it here? Keeping this issue is fine. > TS3Audiobot (which if I understand correctly shares the tsdeclarations with this project)...

Thanks for your comments Wolverin. > Yes that's right, but except here it does not causes any issues at all ;) Right, I guess I need to write my code...

Ah, I see now that `invokerid=0 invokername=undefined invokeruid=undefined` is sent while the TeamSpeak server just omits them. The uid failed to parse as a valid uid of course. > BTW...