So really, all this is more pointing out a direction for how it's demonstrated/applied than actually what to do with it.īut whatever you do with it, nice to see another example of an application of an uncommonly thought of and highly overlooked resource out there.
#RAGE PLUGIN HOOK JULY 2021 CODE#
You'd then be giving a good idea of a use for the menu, by it's proof of principle application as a trainer, doing it a little differently on two levels on how it's delivered, and assuming you open the code to it - giving a further educational resource where people can see how the menu system works, and how you cleverly applied uncommon approaches by integrating lots of commonly used single functions.
So you could pick, as a simple example, a handful of common trainer functions all commonly used together, give them a group name (for single menu entry purposes per 'group') and selecting the 'group' by it's menu entry enables all in the group or none - giving a bit of hotkey simplicity to pre-selecting a lot of commonly grouped functions.
#RAGE PLUGIN HOOK JULY 2021 MOD#
So maybe think along the lines of cumulative purpose-related group features as menu entries?Īn example of that, which you could use for reference, is stuff like the 'i' series mods and the ones that came before them - where each was enabling a specific set of related functions highly focused to the theme of the mod as a modular or standalone thing. It's all well and good 'reinventing the wheel' by adding common trainer features to the menu (and i respect there is value to it for educational reasons without a doubt), but doing it a bit differently would make it stand out as both another decent example of RageHook use (of which the few really decent ones wouldn't use all the fingers on one hand - and i don't need to quote the good ones).
Since this is deeply a development rather than a ready mod, if you are going to consider 'trainer' features to demo the menu with - try thinking laterally :)
0 kommentar(er)
