This is called to free allocated memory for wchar **. Metadefender Core calls this after Metadefender Core is finished with the values allocated by your functionality.

This method is used to retrieve additional attributes about the definition files in use by the custom engine.

This is used to retrieve the timestamp of the definition files currently in use by the custom engine. Memory is allocated by Metadefender Core.

This method is used to get engine properties such as extract archive, heuristic.

This method is used to retrieve the expiration date of engine.

This method provides the name of the custom engine. Metadefender Core uses this for display purposes.

This is the first method called. It allows you to initialize your engine. Metadefender Core recognizes your engine only if this method returns successfully (returns 0).

This is called in order to initiate an update of the custom engine. The call is synchronous and waits until the update completes.

This is used to reload any or all specific engine configurations. If there is no specific engine configuration that needs to be reloaded, this function returns "0" without any re-initialization of engines.

This method provides a way for Metadefender Core to explicitly reload the definition database of the engine, especially for a malware engine. During this call, any requests to scan return "Not Scanned." If there is no specific step required for reloading the database, it still returns "0" to indicate that the engine is ready.

This is the main function of the custom engine. The scan result returned from this function call is used by Metadefender Core’s scan-related API.

This method is used to set engine properties such as extract archive and heuristic.