Would you like to add a native that can change the position of choice for each client?

Yeah that could be added, what's your use case for that though?

You mean something like:

1
2
3
4

and then you do menu.SwapClient(client, 0, 2); and get:

3
2
1
4

Since I would like to show different clients with different predetermined orders, and a swap will make thing a little bit complicated, a direct call to set all options or a callback like typedef OnSetMenuOptions = function void(int client, int pos[], int options) will make it easier.

// Assume we have menu has 6 options
Menu menu;
int choice[6];

GetChoiceForClient(client, choice, sizeof(choice)); // return: choice = {2, 1, 0, 4, 5, 3};
menu.SetOptionsPos(client, choice, sizeof(choice));

/*
Vote menu for client:
2
1
0
4
5
3
*/

That extra native seems out of scope for this PR.
What's the use case for different predetermined menu item orders over just randomizing all items per client?

@peace-maker
To your concern, you may want to recommend some choices on a per user basis or use predetermined order to manipulate the voting results since too many people just press first item on map voting.

User tailored menu option order sounds cool.
Can't mix it with the integrated random shuffling right now though. Like putting your own nomination on top but shuffling the rest.
But no problem to do this in the plugin.

Putting your favorite map to slot 1 should be done by inserting it first and not per client.

In fact, the voting API should have more customizations, or move all the functionality to a SM plugin (like MapChooser) instead of a SM module; but I dont think it is worth it to open a PR for it since right now is more than enough for everyone.

And the part was just make up by me, if you just want to do so, I, however, will suggest only make part of the voters have it on the first place thus nobody will noticed it xD.

In my example A0 will be the first item for everyone, since I specified start to be 1 instead of 0.
so you can do:

menu.AddItem("bestmap", "bestmap");
menu.AddItem("okaymap", "okaymap");
menu.AddItem("badmap", "badmap");
menu.AddItem("badmap", "badmap");
menu.AddItem("badmap", "badmap");

menu.ShufflePerClient(2);

that should put bestmap on top, okaymap as 2nd and the badmaps will be randomized.

I use the end param to not randomize the extend option for example, so it is always on number 9.
And if you had some text on line 1 then you'd set the start param to 1 to not randomize entry 0.

I don't think this needs to be securely shuffled. Think we can just "shift" the options per client index? if they're client 9 -> shift all elements by 9 on a circular buffer.

Sure but this is barely any more complex, doesn't use much memory and enables setting options to fixed slots per client with the new native.
And most importantly it's already implemented and works as expected.
Also real random is just better :p