I'm fairly certain I got these things right, but it might require some fool-proofing:
I use Panels myself each time I need to fit more selectable and/or unselectable lines (i.e. action + comment + space) as Panels allow you to have lines which you don't need to assign a number to. For example, in a Panel you can have:
HTML Code:
Panel Title
1. Slay all
Slays all players on the server
-
2. Kick all
Kicks all players from the server
-
3. Heal all
Heals all players on the server
-
4. Info
Display additional commands
And you can have everything which doesn't have a number to be completely unselectable. A thing to note about Panels is that their handles are not tied to a specific callback, which means you create a Panel handle and tie it to manager callback when you're sending it to a client. This might not necessarily be a good thing as you are left to clean up after the Panel yourself.
But in a menu each of those line must have their number assigned to them. You can choose it to hide it, but you can't reuse it nonetheless; "Slay all" will be 1, "Kick all" will be 4, "Heal all" will be 7 and the limit is
usually here.
The advantages of Menus, on the other hand, is that, although they can't offer raw text, they do offer a better item managing, by which I mean pagination. This basically means that Menus can have a very large amount of items in them and they will be nicely formatted however you tell them to. In paginated Menus, 3 last keys will be taken and replaced by the navigation items: 8 - "back/previous page", 9 - "next page", 0 - "exit". They will update automatically depending on whether the client is viewing the first or the last page of items. As mentioned in Panels, Menu handles' callbacks are tied to them upon their creation.
Linear Mode
