[Emmet_]

Quote:

Originally Posted by [uL]Pottus I think this look pretty good one thing I think could have been done differently is this. Doing this looks ugly to me and doesn't really make sense given the way dialogs are organized with your include in this manner. pawn Code: public OnDialogReceived(playerid, dialog[], success) {     if (!strcmp(dialog, "WeaponMenu") && IsPlayerInAnyVehicle(playerid))     {         SendClientMessage(playerid, -1, "You must be on-foot to spawn a weapon.");         return 0;     }     return 1; } This makes a lot more sense to me pawn Code: DialogRecieved:WeaponMenu(playerid, success)

That's a better concept than mine, thanks!

I was thinking that "WeaponMenu" for example could be a real constant ID rather than a disguised string, so then I can do something like:

pawn Code:

public OnDialogReceived(playerid, dialog, response)
{
    if (dialog == WeaponMenu)
    {
        // code
    }
    return 1;
}