Before updating the spell again, please be sure
the following changes are made.
1. Provide a configuration trigger.
Users should be able to easily configurate your spell in there.
This should cover abilityId, damage, distance, speed, aoe, .....
2. Use the data complexity which fits the situation
Use arrays wherever they are required. For example in
Point_Caster a non-array could and should be used ( clean coding, memory, speed ).
Another example would be when you do a group enumeration.
3. Remove all hardcoded stuff
All of this should be covered in the config trigger and stored into variables.
I think it will take time and updates until this spell can be approved.
For now: Set to Need Fix