Static won't even compile! lol I was in the wrong directory from force of habit. I meant
new const instead of static. Macros do chump a bit but few maps use this ent and only custom ones at that. So like an array repeats everything in it when applied to a native like giving a weapon in this case, you are illustrating by using this as a macro it is a memory chewer? I would have not used a macro beyond small requests and only this one because do not feel comfortable sharing script flat out disabling the USP silently. Thanks for chiming in. Please help me understand further if this is so. Have any supporting documentation or evidence beyond I said so? I need to see this. I pasted what the manual shows on GitHub today.
Quote:
|
you don't need to remember the value between function calls, therefore you do not need a global like variable with local scope.
|
I get it. Did not think it was that big of a deal. Since it is the
same value time and time again why look it up again or define it over and over as a new variable that destroys itself?
__________________