[PartialCloning]

I'm trying to run a few checks when a player starts spectating a different player but I can't find a reliable method to hook it. The events do not seem to be called, and spec_next/prev do not work if you're in first person mode and you use your mouse to switch targets. Are there any other commands/events associated with spectating?

[Grey83]

Try to look for the desired function in the code of this plugin

[blaacky]

If the game supports the SendProxy manager you can hook the "m_hObserverTarget" netprop change in clients.

spec_next should work, however you might need to wait 1 tick in order to see the actual change. Or you might be able to predict what the player's next observer target is. I believe it is always the next living client index and it loops around to 0 whenever it hits the highest client index and on spec_prev it's the other way around

[PartialCloning]

Originally Posted by Grey83 Try to look for the desired function in the code of this plugin

It runs a timer to check the target the player is aiming at.

Originally Posted by blaacky If the game supports the SendProxy manager you can hook the "m_hObserverTarget" netprop change in clients. spec_next should work, however you might need to wait 1 tick in order to see the actual change. Or you might be able to predict what the player's next observer target is. I believe it is always the next living client index and it loops around to 0 whenever it hits the highest client index and on spec_prev it's the other way around

Sendproxy is crashing the server even when I only use the provided examples in the thread's main page. But it prettymuch checks the value of the netprop on every frame and reports back when it changes.

As for spec_next / spec_prev they're not called if you're spectating on first person mode and you use your mouse buttons to change your target.

[blaacky]

I guess it's a CS:GO thing because it works for me in CS:S. Do you want to make it so spectators can't spectate others or something like that? If that's the case I recommend hooking SetTransmit with SDKHooks and blocking information that way. If that doesn't work I don't know :/

EDIT: Actually you can try checking for a change in the buttons parameter for IN_ATTACK under OnPlayerRunCmd. And if the player changes observertarget without changing their buttons parameter (spec_next in console) you can punish them