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 should return ‘Not Scanned.’ If there is no specific step required for reloading the database, it should still return "0" to indicate that the engine is ready.

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 is called to initiate an update of the custom engine. This call should be a synchronous call and wait until the update completes.

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 provides the name of the custom engine. Metadefender Core uses this for display purposes.

This is called when Metadefender Core is shut down. Any resources acquired by your engine will be released and any unsaved data will be stored.

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