Open GoogleCodeExporter opened 9 years ago
I see three possible options of where to pick the random map from: current vote
choices, all nominatable maps (gal_nom_mapfile), and all vote fill maps
(gal_vote_mapfile). I can make it a setting, but I would still need to default
it to the "best" option. Hmm...
Original comment by jones.p....@gmail.com
on 7 Jan 2011 at 10:58
I like the thought of this option, but not enough to let it have its own spot
in the already limited option list, so I would probably not enable this option
on my servers.
However. One thing thing that always bothered me is how surprisingly many
players seem to just hit "1." every time a vote is displayed, I guess they just
want to get done with the vote and continue playing/avoid dieing. So how to
deal with that?
I would like to be able to configure Galileos first displayed option with a
separate cvar, an option like: "The first vote option is always:"
a) Blank vote aka "Whatever" aka Let the others decide
b) Random map from current vote/cycle/pool
c) The map this player nominated/the first nominated map
So if this tracker item could fit into that first slot as an option I welcome
it, otherwise not, since I regard the "first slot option"-issue as way more
important.
Original comment by ccond...@gmail.com
on 8 Jan 2011 at 9:18
One of the things I plan on having done for the next release is randomizing the
displayed choices. That should somewhat alleviate the problem of players always
pressing "1" (though on my servers, I haven't experienced that problem).
http://code.google.com/p/amxx-plugin-galileo/issues/detail?id=8
Back to THIS issue...
re: already limited option list
You know you can have up to 8 choices, right? gal_vote_mapchoices
Of the three options I gave for this feature in comment 1, I think the only
viable one is from the "current vote choices". Otherwise, it's extremely
unlikely a random map would ever win.
I could allow this option to be placed as the first option in the vote. I'll
have to think about that.
Original comment by jones.p....@gmail.com
on 8 Jan 2011 at 4:37
Oh, I thought the "random" option would be more like a wildcard. The wildcard
would be set per vote, so every player who choose to vote for the wildcard
actually do vote for the same map, just that they don't know which until vote
end. If feasible, lower the rtv-wait time if the wildcard wins, people may
regret their choice.
I cannot recall right now if there is a way to fill x vote options from cycle,
and then fill the remaining options up to gal_vote_mapchoices with random
choices from the nominatable pool, but that is probably the configuration I
would be willing to try out. That would make the choices a bit less
static/repetetive over time, but also renders the literal "random" option a bit
useless IMO.
Sorry for ranting on about offtopic, but give me the "blank/whatever" option as
line 1 and I'll be a happy camper and will not miss a "random" option. :)
Original comment by ccond...@gmail.com
on 8 Jan 2011 at 7:04
Oh! That's a great idea, ccondrup! I never thought of it like that, but it's
brilliant! Wildcard it will be. I probably won't touch RTV wait time if the
wildcard wins. I could conceivably force a runoff vote whenever the wildcard
wins, even if the vote doesn't otherwise meet the criteria for a runoff.
I agree that the "random" option is useless. It'd be more of a fun and
adventurous feature.
Currently, Gal will throw the nominated maps into the vote, and then will fill
remaining slots with the maps specified via the gal_vote_mapfile CVAR. In
theory, you could use the "groups" feature but documentation for it is sparse
(docs on this site [check the wiki] are for the unreleased version and are
incomplete) and I've heard reports of it not working in 1.1.290. But yes, in
theory, you could use the "groups" feature to do as you suggested.
Original comment by jones.p....@gmail.com
on 8 Jan 2011 at 7:27
Original issue reported on code.google.com by
jones.p....@gmail.com
on 24 Dec 2010 at 11:42