[BAILOPAN]

We're trying to decide how to best design admin menus for SourceMod. There will be a "main" admin menu with a few big categories like "Player Commands," "Server Settings," etc, and then plugins will be able to add to those menus.

The poll question is, let's say you're in a sub menu and you "complete" the sub-menu by selecting "Exit" or selecting an item. What should happen?

The sample menu you should consider is:
First level:
1. Player Commands
0. Exit

Second level:
1. Kick Player
0. Exit

Third level:
1. Player X
2. Player Y
3. Player Z
0. Exit

[sslice]

I chose other... this would use up a key but there should probably be an Exit option as well as a Back option... Back would go up one level, Exit would exit the entire menu chain (and the same for a selection). Although, this might just make the menu more cumbersome to use. If that is the case I would choose "Re-display on selection; exit goes up one level".

[FlyingMongoose]

I agree with the "first explanation" sslice pointed out

[sessus]

Why not just use the implementation within the latest Mani release: unambiguous, well known

[Brad]

I'd also like to suggest for consideration, having a "Done" option.

Using BAIL's sample menu:

First level:
1. Player Commands
0. Exit

Second level:
1. Kick Player
0. Done

Third level:
1. Player X
2. Player Y
3. Player Z
0. Done

This would be helpful if you want to perform an action on a number of players. Say you want to kick players Y an Z. You would press "3" to kick the first player and then "2" to kick the next player. Finally, you'd click "Done" which would bring you to the previous menu.

Essentially, "Done" would be like "Back" while "Exit" would cancel the entire chain.

[L. Duke]

I voted other. It seems like the plugin should decide when it calls a menu to open which behavior is appropriate for that specific menu.

[BAILOPAN]

sslice: There's only space for 3 control options, I don't think I'd want to sacrifice any more slots for a fourth.

sessus: I have no idea what Mani does so you will need to describe it.

LDuke: Certainly, but the poll was about a specific case ;)

Brad: I like your idea. We'd have to add an API call to change the word "Exit" to "Done," but I don't see that as too troublesome.

[^BuGs^]

I am with Re-display on selection; exit goes up one level and the idea of Brad. However, selecting more than one "option" would only be good for players and certain settings that don't need the server to restart the map. However, it could be used in "vote for "these map selections" and there would need to be a limit. So using Brad and BAIL's sample menu...

First level:
1. Player Commands
2. Server Commands
0. Exit

Player Menu level:
1. Kick Player
0. Exit

Server Menu level:
1. Map Vote
2. Map Change
0. Exit

Map Vote Menu level
1. de_dust2
2. de_train
3. cs_office
9. Done
0. Exit

Map Change Menu level
1. de_dust2
2. de_train
3. cs_office
0. Exit

Player Menu level:
1. Player X
2. Player Y
3. Player Z
9. Done
0. Exit

[BAILOPAN]

We can't have both "Done" and Exit." It would take up 4 slots if there was Back/Next being displayed.

I'm a bit hesitant to do that because then there would only be six options per page, or four for a Valve menu.

[tcviper]

As Mani has it, thats the best IMO.