[EiresJason]

Quote:

Originally Posted by Abagail This isn't a good enough reason to use stock, you can even simply do something such as this: pawn Code: #define SetPlayerLevelEx FUNC_SetPlayerLevel pawn Code: FUNC_SetPlayerLevel(playerid, level) {    // .. code Then you can just search for "FUNC_Functionname", - calling the function throughout the script as "SetPlayerLevelEx". If it gets on your nerves so much try this or another method, but as I said this is NOT A GOOD REASON TO USE STOCK!

Could you explain why it isn't good enough though? At the moment though , when I'm going to compile my GM, I just replace all instances of "stock " with "" so it removes the stock modifier at compile time and I have the easy search functionality when I'm scripting.

Thanks for the suggestion but it doesn't seem reasonable to do that for every single function I use

EDIT: So yeah.. it literally makes no difference? XD