I am thinking of pushing common memory hacks used in Outpost 2 missions into HFL. In the process, I wanted to provide a more general framework for future mission specific hacks. I think this already exists in the HookHelper contained in CCF2 and I'm assuming a lot of the other survivor missions. I think modifying and including HookHelper would work much better than antyhing I created on my own.
After pushing the HookHelper into HFL, I was going to push several of the general memory hacks contained in CCF2 into HFL and allow toggling them from a mission's main function. It would look something like:
BOOL APIENTRY DllMain(HINSTANCE hinstDLL, DWORD fdwReason, LPVOID lpvReserved)
{
if (fdwReason == DLL_PROCESS_ATTACH)
{
DisableThreadLibraryCalls(hinstDLL);
HFLInit();
DissableInitialAllyMessages(); // Stop each player from receiving ally messages at game start for coop missions
HookPostMissionVideo(); // Show a movie at mission conclusion
}
else if (fdwReason == DLL_PROCESS_DETACH)
{
HFLCleanup();
}
return true;
}
The target hacks would be optional items that one wouldn't want for every mission, but may be good to enable in specific instances. I wanted to add post mission videos to several of my missions, and this would allow that sort of activity without copy pasting the code everywhere.
All this would just be me formalizing things already created by others. I'm not sure if anyone minds?
I guess I'm asking if there is input from the community, (especially Arklon, sirbomber, or Hooman) before getting more in earnest in the work.
I have HFL toggling DissableInitialAllyMessages on my local copy of HFL, so it is certainly possible without a lot of work.
Thanks,
-Brett