This was the only working version of this package. The current one left is broken and appears to be abandoned (I didn't flag it earlier as I thought the maintainer was just on temporary hiatus). Some warning would have been appreciated on this rather than just deleting a load of my packages this morning.

This request was filed on the 19th, that's plenty of warning.

My fault, I saw the deletion acceptance and the deletion request email, not the deletion request email.

Not to mention that these are obvious duplicates, and you just systematically ignored the rules.

This wasn't a duplicate. One works, one doesn't. If they were duplicates then that wouldn't be the case. Some of my old temporary packages were fine to be deleted though as the "originals" have since been fixed. But this was not one such case.

This was the only working version of this package. The current one left is broken and appears to be abandoned (I didn't flag it earlier as I thought the maintainer was just on temporary hiatus).

Not a commentary on this specific instance, but as an AUR user it's not fun to have to sort through multiple people's packages of the same software. That isn't how it's supposed to work. If a package is broken, please comment on it. If it doesn't get fixed, flag it to be orphaned. If you are in a hurry for it to work, clone to broken package and fix it. If you want to make it easy for the author to fix and/or others to use pending that fix, post the forked git repo elsewhere. This will also make it realy easy for you to post the fix if it gets orphaned.