[343N]

So this is the my first plugin ever. I want a menu to let clients select a config for the models they'll use for their weapons, but the problem is I need to somehow keep track of each clients selection in the menu, since I'll have another plugin making callbacks depending on what option was picked in the menu. How would I go about storing a users selection/choice in a menu so that another plugin/part of my plugin can make sure to do the correct thing for each client?

Basically, how would I do this?

public bool AlwaysExecutingCallback(int client){

If (getSelectedOptionFromMyMenu(client)) { // <--- how do I get something like this
//do blah
}

}

I hope this is a good enough explanation of what I want to do.

[friagram]

A param in the menu handler is the item number. You can use or store that to calculate the return menu item, just divide by 7

[343N]

Originally Posted by friagram A param in the menu handler is the item number. You can use or store that to calculate the return menu item, just divide by 7

Okay, the divide by 7 part just confused the hell out of me. Does the menu itself store the options chosen by each user, why would I need to divide by 7? (unless you're talking about paged entries)

If you're talking about pages, I might have made a miscommunication, I'm not worrying about pages. I'm just wondering, how would I get/store X client's chosen option on the menu to execute an appropriate action based on their setting in a constantly firing callback. (If that makes sense). Does the menu handler store the chosen option by each client for the handlers lifetime? And if so, how would I retrieve a specific clients chosen menu option?

[nosoop]

Create a globally-scoped player-indexed array to store the options chosen by each client (use GetItem() to get the menu info), then just pull the data from the array when you need it.

[friagram]

Originally Posted by 343N Okay, the divide by 7 part just confused the hell out of me. Does the menu itself store the options chosen by each user, why would I need to divide by 7? (unless you're talking about paged entries) If you're talking about pages, I might have made a miscommunication, I'm not worrying about pages. I'm just wondering, how would I get/store X client's chosen option on the menu to execute an appropriate action based on their setting in a constantly firing callback. (If that makes sense). Does the menu handler store the chosen option by each client for the handlers lifetime? And if so, how would I retrieve a specific clients chosen menu option?

Oh, the menu gives you the selection in the handler when it is type MenuAction_Select
https://wiki.alliedmods.net/Menu_API...od)#Basic_Menu
Param1 will be the client index, param2 is the menu item.
You can get the strings from the item if you need there too.

[OSWO]

Param2 will always yield the position of the item in a MenuAction_Select.

Position of an item =/= the button (number) it was pressed.

If you want to return the "Page" to be used in a https://sm.alliedmods.net/new-api/menus/Menu/DisplayAt function, you can use https://sm.alliedmods.net/new-api/menus/Menu/Selection

[343N]

Originally Posted by nosoop Create a globally-scoped player-indexed array to store the options chosen by each client (use GetItem() to get the menu info), then just pull the data from the array when you need it.

Ah, thought so. This was what I was looking for, I thought there might be a more elegant solution to this. How would I go about storing this data so that when the map changes/server crashes, the data is retained?

[nosoop]

Originally Posted by 343N How would I go about storing this data so that when the map changes/server crashes, the data is retained?

You'd likely want to store it in a database. The easiest way to store account-specific information persistently would be to use the Client Preferences API, which abstracts SQL / SQLite database storage.

[343N]

Originally Posted by nosoop You'd likely want to store it in a database. The easiest way to store account-specific information persistently would be to use the Client Preferences API, which abstracts SQL / SQLite database storage.

Looks good, thank you for your help, much appreciated.