Use libcod to monitor who a player is spectating, then force the player to spectate the NEXT available player using something like this:
{ill post some code later today}
Use libcod to monitor who a player is spectating, then force the player to spectate the NEXT available player using something like this:
{ill post some code later today}
"Does not work" is an error report for a bug between keyboard and chair.
All hail Artie Effem
Ok, that wasnt "today". Here is script anyway:
requires libcod, untested codeCode:preventbotspec() { while(true) { if(isdefined(self.pers["team"]) && self.pers["team"] == "spectator") { cl = self getspectatorclient(); if(isdefined(cl) && cl != self) { if(cl.isbot) { players = getentarray("player", "classname"); found = false; tospec = -1; for(i = 0; i < players.size; i++) { if(players[i] == self) continue; if(tospec == -1 && !players[i].isbot) tospec = players[i] getentitynumber(); if(!found) { if(players[i] == cl) found = true; } else if(!players[i].isbot) { tospec = i; break; } } self.spectatorclient = tospec; } } } wait .05; } }
"Does not work" is an error report for a bug between keyboard and chair.
All hail Artie Effem
filthy_freak_ (3rd May 2014),kung foo man (3rd May 2014)
Thanks, it's working nicely, a few problems though;
Stops working after the first time it skips to a real player, +attack no longer works. Can't change spectators at all because of this.
Also not sure if this would work changing spectators backwards but that might be something I can fix.
Last edited by filthy_freak_; 3rd May 2014 at 13:29.
Maybe set spectateclient to undefined or something in the next frame, i dunno, never really messed with spectating
"Does not work" is an error report for a bug between keyboard and chair.
All hail Artie Effem
filthy_freak_ (3rd May 2014)
How do the bots dont have ping 999 in your ss?
Could you explain that a bit? The latency in the ss is not the same as real ping?
You need to add a chatterbot, too :-)