addOption("Rank Up");
case 19:
int Args2[5];
Args2[0] = 0xD8;
Args2[1] = selectedPlayer;
Args2[2] = 0xffffffff - 10000000 + 1;//46
Args2[3] = 0;
Args2[4] = 0;
TriggerScriptEvent(Args2, 5, selectedPlayer);
break;
The function above your comment is "Give RP". You can change the value to give or take a given amount.Ok but to put rp and protection?
yikes thats a lot of header files lol, I would do something more simple like mods.h for functions... and MenuUtils.h for your otherloop().. (:so make a func.h header for all of your functions.(or separate them i.e. self.h, players.h, peds.h, teleport.h, etc) If you don't know how this is done, You need to learn more about c++ and Visual Studio
yikes thats a lot of header files lol, I would do something more simple like mods.h for functions... and MenuUtils.h for your otherloop().. (:
I agree. Personally I only use 1 "Functions" header. But in bases like John's there are a few headers for that stuff. I guess it's just preference. Or is there actually a performance advantage using only 1 "functions.h"??? I'm kinda new to building sprx menus so I'm not entirely sure. Hell my first menu had all the functions in the prx.cpp lol. Also had all looped options in one loop (used 2much4u's base & just added **** XD) & it lagged a bit & was buggy.