Open evandrocoan opened 7 years ago
>=3
better because of knife :)
I would not force it, just let the user set the cvar as it wish. For example, assuming this cvar gal_vote_mapchoices
set to 3:
0) If the gal_vote_shift
set to 0, the menu would be like:
Choose the next map
1. aim_ak-colt
2. aim_headshot
3. awp_city
0. Commands menu
1) If the gal_vote_shift
set to 1, the menu would be like:
Choose the next map
2. aim_ak-colt
3. aim_headshot
4. awp_city
0. Commands menu
2) If the gal_vote_shift
set to 2, the menu would be like:
Choose the next map
3. aim_ak-colt
4. aim_headshot
5. awp_city
0. Commands menu
3) If the gal_vote_shift
set to 3, the menu would be like:
Choose the next map
4. aim_ak-colt
5. aim_headshot
6. awp_city
0. Commands menu
4) If the gal_vote_shift
set to 4, the menu would be like:
Choose the next map
5. aim_ak-colt
6. aim_headshot
7. awp_city
0. Commands menu
5) If the gal_vote_shift
set to 5, the menu would be like:
Choose the next map
6. aim_ak-colt
7. aim_headshot
8. awp_city
0. Commands menu
6) If the gal_vote_shift
set to 6, the menu would be like:
Choose the next map
7. aim_ak-colt
8. aim_headshot
9. awp_city
0. Commands menu
I may have free time on December/January for working on this.
Is this cvar on development? I find it quite useful. If not, is there a clever workaround to solve accidental voting? gal_endofmapvote_ask 1 is nice but it denies weapon switching while the menu is active.
The cvar should be
gal_vote_shift
and its value should shift the voting numbers start.If a value greater than the maximum shifting is used, just shift then until the maximum possible, accordingly to the number of vote map choices avaliable by the cvar
gal_vote_mapchoices
.This is useful because players can still play and change weapons before voting. In that case we would want to shift it 7 positions and have only 3 maps choices.