Packet editing does this funny thing, when the server receives a flood of abnormal packets it creates a report linked to the user that was sending these packets. In short its much easier to get banned for this activity then for client side modding.
As for your time circle heres what happened to patch the ranged edit;
before the patch this happened-
aiming started
aim created a variable that stored the % aim
this was compared to the max
the system calculated the difference from the max
you hit or miss
by skipping the setting of the variable the system used to compare the max to the max therefore resulting in you hitting with the max aim % possible.
After the patch there was a lingering variable, set to 0, that was always present for values that were not set. In short the system now checks to make sure that the aiming process was initialized, if not it sets the aim value to 0.
For the patch that was just implemented for fireball, a simple check is used that should be easy to circumvent.