A recent post suggests that "the troubleshooting information might give some insight." and a quick search shows that as far back as 2013 "Debug output to a text file" was an issue.
I feel that debugging information is spread over many areas of Everything. A screenshot submission shows the version being used (unless the user has been playing with the title!) but most of the debugging data is in text form. Sadly some of this text is embedded within a pop-up pane, and must be copied to a Notepad text file for submission and the notepad text file saved before moving on to the next chunk of text data. (I understand that this is on a ToDo list somewhere).
But even then a user has to gather the various files and ZIP them in Windows before they can be attached to this installation of phpBB software.
In another post I wrote
a generic set of data that is likely to be of help, then it might
(1) Speed up analysis in a timely manner; many of us have to work around or try to fix the problem locally
(2) Reduce the amount of time you spend (Mea Culpa) in posting a response asking for a set of well-defined data.When a user experiences a problem, that user would be able to execute a single command and know that all text data is safe and secure in a zip file on the user's hard drive.
The user then takes a screen snapshot, composes a message, and attached the zip file.
Voidtools will be provided, probably with an excess of debugging data, but at least, all the debugging data that the user might be expected to collect.
Since the zip file is well-defined by voidtools, voidtools knows where to look to ferret out useful data and can ignore other sections. The size of the file will be insignificant (it is ZIPped text)
Bonus: If voidtools decides that more debugging data will improve problem-solving, capture of that data can be implemented automatically by updating the "zipdebug" command without the user needing to worry about it.
Thanks, Chris