[PartialCloning]

Is MENU_EXIT guaranteed to get called when a menu is displayed to a client?

1. A game menu or another menu by a plugin overrides it.
2. A player's hud resets.
3. A player disconnects.
4. Map changes while the player is viewing a menu.
5. Any other scenario? Can I expect MENU_EXIT to always get called?

[Relaxing]

~) Client exited the menu.
~) Menu timeout.
~) After client choosed its option and menu exited.
~) Motd(not sure)

[edon1337]

Originally Posted by PartialCloning Is MENU_EXIT guaranteed to get called when a menu is displayed to a client?

I think yes, because I've seen that in every code, they check

if( iItem == MENU_EXIT )

without using menu_setprop.

[siriusmd99]

You can test, put down some text when item is Menu exit
if(item==MENU_EXIT)
client_print.....
And just toggle some other menu and see what happens with the current one.

[PartialCloning]

I think you misunderstood the question. I can't test if MENU_EXIT is guaranteed to be called at every possible scenario as some are hard to replicate.

The points I listed are examples to clarify the question. What I would like to know is if amxx takes into account every possible case and calls MENU_EXIT when a menu is displayed and no option is selected. If not does that result in leaks or does amxx internally destroy the handles without calling MENU_EXIT in the menu handler.

[Relaxing]

Originally Posted by PartialCloning I think you misunderstood the question...

If MENU_EXIT isn't same as menu_destroy(), then MENU_EXIT will be called only on value output(key trigger)
menu_destroy() forces the menu to remove, in this case all other possibilities.(disconnection, plugin's override...)

[aron9forever]

Even in the unlikely case that it covers some of that list besides when you actually press a button, I wouldn't think it would especially in an instant map change, consider crashes too

[PartialCloning]

Originally Posted by Relaxing If MENU_EXIT isn't same as menu_destroy(), then MENU_EXIT will be called only on value output(key trigger) menu_destroy() forces the menu to remove, in this case all other possibilities.(disconnection, plugin's override...)

MENU_EXIT is called when you override a menu with another. How are you sure it's called in all other cases?

Originally Posted by aron9forever Even in the unlikely case that it covers some of that list besides when you actually press a button, I wouldn't think it would especially in an instant map change, consider crashes too

It does work after an instant map change, if by instant you mean typing map de_dust2 in console. Crashes don't matter, if a server crashes I don't expect plugin_end to be called either.

"client_disconnected is guaranteed to pair with the client_connect()". if one is called so will the other. What I would like to know is if there exists such a connection between menu_display and MENU_EXIT being called in the menu handler function.

[aron9forever]

I think you can only find this in the amxx source wherever newmenus are handled
I'll try having a look as well when I have the time

literally testing for all scenarios might be quicker so I understand why you are looking for someone who can tell you without checking