Hmmm. I missed the memo on that item. However, if he used the UniBeast/MultiBeast installation method, FakeSMC is in the /L/E/ folder. But, what does FakeSMC have to do with his moving HACKNVMe kext? I've lost lock on this problem (pilot talk).
FakeSMC.kext in /Library/Extensions means FakeSMC.kext is in kernel cache. As a result, Clover will not inject any kexts from Clover/kexts. Assuming InjectKexts=Detect, placing HackrNVMe* into Clover/kexts/Other will have no effect (except for scenarios where FakeSMC is not in cache: the recovery partition, booting the installer, etc).
Also, for 10.12, HackrNVMeFamily cannot be used when IONVMeFamily is present. So in final install IONVMeFamily needs to be removed, and Clover hotpatch (KextsToPatch) needs to be used for the installer/recovery scenarios.
For proper setup in the typical Unibeast/Multibeast setup (eg. FakeSMC.kext installed to the system volume, InjectKexts=Detect):
- USB installer uses KextsToPatch for IONVMeFamily that match the version of OS X/macOS on the USB
- EFI/Clover on HDD/SSD uses KextsToPatch for IONVMeFamily that match the version of OS X/macOS you plan to boot with it (can vary depending on whether you're doing an upgrade install or recovery boot, etc)
- HackrNVMeFamily installed to the system partition
- IONVMeFamily removed from the system partition
In order to arrive at these set of rules, you need to have only basic knowledge:
- the conditions under which Clover kext injection is performed
- the fact that IONVMeFamily cannot be combined with HackrNVMeFamily in 10.12
- realizing the scenarios where HackrNVMeFamily cannot be used, and using KextsToPatch instead