Change Details

using `_fnc_scriptName` within a cfgFunctions Function works great. It would be even more amazing if `_fnc_scriptName` would pickup the `key` value when methods are being executed. Alternative: introduce 2 new magicVariables 1. `_meth_scriptName` specifically to work inside methods 2. `_scriptName` to work universially, within CfgFunctions and HMO Methods.

using `_fnc_scriptName` within a cfgFunctions Function works great. combined with diag_log it can produce some quite informative debug lines: `[storm][fx_sound](storm_fx_sound_fnc_remote_3d) FX_Sound HMO created - [...]` It would be even more amazing if `_fnc_scriptName` would pickup the `key` value when methods are being executed. `[storm][fx_sound](any) Helper Created` vs. `[storm][fx_sound](#create) Helper Created` Alternative: introduce 2 new magicVariables 1. `_meth_scriptName` specifically to work inside methods 2. `_scriptName` to work universially, within CfgFunctions and HMO Methods.

using `_fnc_scriptName` within a cfgFunctions Function works great. combined with diag_log it can produce some quite informative debug lines: `[storm][fx_sound](storm_fx_sound_fnc_remote_3d) FX_Sound HMO created - [...]` It would be even more amazing if `_fnc_scriptName` would pickup the `key` value when methods are being executed. `[storm][fx_sound](any) Helper Created` vs. `[storm][fx_sound](#create) Helper Created` Alternative: introduce 2 new magicVariables 1. `_meth_scriptName` specifically to work inside methods 2. `_scriptName` to work universially, within CfgFunctions and HMO Methods.