Notes:

• Excessive function calls have been detected in the main spell, which could affect performance.
  
  
• The configurability of the spell is practically non-existent. This is important, since the configurability of a spell would be a key factor in how certain resources are imported.
  
  
• This spell could break the synergy with the Death Knight's Animate Dead and derivatives, which may result into unintended spell behavior (Removing a certain animated unit in control of an ally player or an enemy player may fall under foul play, under which may be a specific case of Team Killing, and perceived Hacking respectively.)
  
  
• The concept behind the spell is too simple, and violates certain guidelines of the Spell Submission Rules, which are the following:
  
  

• From the Spell Submission Rules said:

  • Submissions must have an adequate resource description. A changelog must be present in either the resource description or the trigger viewer.
    
    
  • Submissions must be useful. Concepts that do not have a clear purpose, or are extremely simple might be rejected (e.g. a "remove unit on death" system is too simple).
    
    
  • Submissions must have decent performance. Unnecessarily repeating function calls, repetitive group enumerations, overuse of special effects, or other useless overhead, should be avoided to prevent a performance drop.
    
    
  • The documentation must at least contain a listing of the API, external library requirements and importing instructions.

  [*]

  Click to expand...

  The fourth Spell rule isn't too strictly enforced by me, but importing instructions would be very much appreciated.

Verdict:

Status:

• Substandard