Top point... here goes (btw, I suck at PR-related things)...
Basically, an application that (when fed the installation path of Anope) will launch anope services with options "-debug -nofork", redirecting anope's standard output and error streams to a memorystream object for the purposes of collecting such output. When anope quits (for one reason or another), the complete output of Anope that would normally be spat into a cmd window is available for upload to the pastebin (via the click of a button, the app would handle this for the user, including giving them the URL with which to paste into the support channel). Fairly simplistic in most regards.