0000700: Random Captains function (callvote randomcaptains)

(0002761)
Watermelon (developer)
2012-03-06 19:19

As a note: when you use 'randcaps', it just prints to the screen two available players in game. Sorry for not attaching this piece of info

(0002762)
TIHan (reporter)
2012-03-06 19:51

> This would help bring more people to testing 98e as well.

That's quite a statement. Perhaps you need to get more people in here to support this request.

(0002765)
bluewizard (reporter)
2012-03-07 03:10

Needs to be added to priv CTF, if there is a way, there should be an option for it to filter out names that end with a * (Because in priv CTF if you end your name with a star, it means you're afk or cannot play).

(0002776)
Torr Samaho (administrator)
2012-03-11 01:37

So you just want this function to print the names of two randomly chosen players (taking into account spectators)?

(0002778)
Dusk (developer)
2012-03-11 01:52

I feel that having a generic system for defining vote types (VOTEDEFS, anybody?) instead of a bunch of very specific ones like this. The actual cointoss is easily doable in ACS, it's just the voting part that ACS cannot do.

(0002792)
Torr Samaho (administrator)
2012-03-11 19:25

> The actual cointoss is easily doable in ACS

From the top of my head I don't know a way to select a random, connected client with ACS. Selecting a random in game player is easy, but I don't see how to include spectators in the selection.

>I feel that having a generic system for defining vote types (VOTEDEFS, anybody?)

Do you have a good and easily implementable idea on how to extend ACS to handle voting? BTW: For voting it is absolutely crucial to rigorously check the voting command and its arguments.

(0002794)
Dusk (developer)
2012-03-11 20:20

> > The actual cointoss is easily doable in ACS

> From the top of my head I don't know a way to select a random, connected client with ACS. Selecting a random in game player is easy, but I don't see how to include spectators in the selection.
Actually scratch that. ACS can't differentiate between spectators and non-existing clients.

> Do you have a good and easily implementable idea on how to extend ACS to handle voting? BTW: For voting it is absolutely crucial to rigorously check the voting command and its arguments.
I was thinking about going in the other direction - make voting more generic. Say:
alias "randcaps" "puke 600"
votetype "randcaps" <details go here, including disable-cvars and stuff like that>

I might look into this in the future on my end. :)

(0002798)
Torr Samaho (administrator)
2012-03-11 21:24

> Actually scratch that. ACS can't differentiate between spectators and non-existing clients.

And that is something that is actually missing, but also something I can easily add a new ACS function for.

> I might look into this in the future on my end. :)

Feel free to do that :).

(0004917)
Watermelon (developer)
2012-10-02 18:51

I think this can be closed, since so far we have a working randcaps function that everyone seems to like.

As now there is more support for checking if players are spectators and I can access names to check for *'s (AFK players) with strparam, I don't think anything like this needs to be made.
Now if it forked off into a custom voting system, that'd be neat.

(0004924)
Dusk (developer)
2012-10-03 12:10

If I ever make such a voting system, I'll make a new ticket for that.

Closing this, then.

This issue is already marked as resolved. If you feel that is not the case, please reopen it and explain why.
Supporters:	No one explicitly supports this issue yet.
Opponents:	No one explicitly opposes this issue yet.

Notes
(0002761) Watermelon (developer) 2012-03-06 19:19	As a note: when you use 'randcaps', it just prints to the screen two available players in game. Sorry for not attaching this piece of info

(0002762) TIHan (reporter) 2012-03-06 19:51	> This would help bring more people to testing 98e as well. That's quite a statement. Perhaps you need to get more people in here to support this request.

(0002765) bluewizard (reporter) 2012-03-07 03:10	Needs to be added to priv CTF, if there is a way, there should be an option for it to filter out names that end with a * (Because in priv CTF if you end your name with a star, it means you're afk or cannot play).

(0002776) Torr Samaho (administrator) 2012-03-11 01:37	So you just want this function to print the names of two randomly chosen players (taking into account spectators)?

(0002778) Dusk (developer) 2012-03-11 01:52	I feel that having a generic system for defining vote types (VOTEDEFS, anybody?) instead of a bunch of very specific ones like this. The actual cointoss is easily doable in ACS, it's just the voting part that ACS cannot do.

(0002792) Torr Samaho (administrator) 2012-03-11 19:25	> The actual cointoss is easily doable in ACS From the top of my head I don't know a way to select a random, connected client with ACS. Selecting a random in game player is easy, but I don't see how to include spectators in the selection. >I feel that having a generic system for defining vote types (VOTEDEFS, anybody?) Do you have a good and easily implementable idea on how to extend ACS to handle voting? BTW: For voting it is absolutely crucial to rigorously check the voting command and its arguments.

(0002794) Dusk (developer) 2012-03-11 20:20	> > The actual cointoss is easily doable in ACS > From the top of my head I don't know a way to select a random, connected client with ACS. Selecting a random in game player is easy, but I don't see how to include spectators in the selection. Actually scratch that. ACS can't differentiate between spectators and non-existing clients. > Do you have a good and easily implementable idea on how to extend ACS to handle voting? BTW: For voting it is absolutely crucial to rigorously check the voting command and its arguments. I was thinking about going in the other direction - make voting more generic. Say: alias "randcaps" "puke 600" votetype "randcaps" <details go here, including disable-cvars and stuff like that> I might look into this in the future on my end. :)

(0002798) Torr Samaho (administrator) 2012-03-11 21:24	> Actually scratch that. ACS can't differentiate between spectators and non-existing clients. And that is something that is actually missing, but also something I can easily add a new ACS function for. > I might look into this in the future on my end. :) Feel free to do that :).

(0004917) Watermelon (developer) 2012-10-02 18:51	I think this can be closed, since so far we have a working randcaps function that everyone seems to like. As now there is more support for checking if players are spectators and I can access names to check for *'s (AFK players) with strparam, I don't think anything like this needs to be made. Now if it forked off into a custom voting system, that'd be neat.

(0004924) Dusk (developer) 2012-10-03 12:10	If I ever make such a voting system, I'll make a new ticket for that. Closing this, then.

Issue History
Date Modified	Username	Field	Change
2012-03-05 23:56	Watermelon	New Issue
2012-03-06 19:19	Watermelon	Note Added: 0002761
2012-03-06 19:51	TIHan	Note Added: 0002762
2012-03-07 03:10	bluewizard	Note Added: 0002765
2012-03-11 01:37	Torr Samaho	Note Added: 0002776
2012-03-11 01:37	Torr Samaho	Status	new => feedback
2012-03-11 01:52	Dusk	Note Added: 0002778
2012-03-11 19:25	Torr Samaho	Note Added: 0002792
2012-03-11 20:20	Dusk	Note Added: 0002794
2012-03-11 21:24	Torr Samaho	Note Added: 0002798
2012-10-02 18:51	Watermelon	Note Added: 0004917
2012-10-02 18:51	Watermelon	Status	feedback => new
2012-10-03 12:10	Dusk	Note Added: 0004924
2012-10-03 12:10	Dusk	Status	new => closed
2012-10-03 12:10	Dusk	Resolution	open => no change required
2013-07-21 00:59	Dusk	Relationship added	related to 0001420