[minimoney1]

For the SourceTV2D, it would be great if you could add a delay (Gotten from a convar like tv_delay) so it would delay the stream.

[nightrider]

Peace-Maker
This is very slick

[el_psycho]

OMG this is awesome! Please tell me it works with L4D2.

[smithy]

Thanks for this very much appreciated

Any chance you could add some color to the message that is displayed to the server when using websocket_test , i have tried myself to no avail , also are you planning on releasing the sourcetv 2d at all in the future looks like an excellent tool

Best regards

smithy

[snelvuur]

Nice work, i assume adding a log_addr like hlsw is doing is causing too much overhead too. (but doesn't use a plugin) i tried the website and tried to connect but i never seem to be clicking when its online. Would like to see the live version.

[jasonfrog]

This is fantastic. Any chance of getting hold of the SourceTV2D plugin?

[Moulijin]

Originally Posted by jasonfrog This is fantastic. Any chance of getting hold of the SourceTV2D plugin?

^

[Moulijin]

Can anyone help me with adding live chat? Thanks

[Thrawn2]

Small feature request: any:data for Websocket_HookChild and its callbacks would be superb.

Edit: Also: another callback for Websocket_HookChild when the ReadyState changes to open would make things easier (e.g. to send a welcome message to the client).
Edit 2: More feature requests Would be nice to be able to register a Subprotocol while opening a WebSocket with Websocket_Open

[Peace-Maker]

Originally Posted by Thrawn2 Small feature request: any:data for Websocket_HookChild and its callbacks would be superb. Edit: Also: another callback for Websocket_HookChild when the ReadyState changes to open would make things easier (e.g. to send a welcome message to the client). Edit 2: More feature requests Would be nice to be able to register a Subprotocol while opening a WebSocket with Websocket_Open

Good ideas, but not as easy and quick to implement as i first thought. Once a childsocket connects to a master socket, a private forward is created and each call to HookChild just adds the plugin's callbacks to the forwards, so it's currently not possible to have different parameters pushed to each plugin.
Having multiple plugins using the same ip:port combo to create their websocket looks like a stupid idea right now.. Why not just error out saying that combo is already in use? I did have a good reason for that back then - can't remember....