Dear Epic,
I must admit the move to prevent users from closing the crash reporter has kind of ■■■■■■ me off.
It makes it take longer for me to close crash reporter for crashes in my own game code, which have nothing to do with you, are not your fault, do not benefit you to know about, and just clog your own systems anyway with useless info about what is going in my own game code.
Not to mention that my perhaps sensitive game code is now going into your data base and perhaps I dont want that?
Please make it an option that I can re-enable the x-button in the crash reporter.
For those of you not sure what I mean, please see this picture
Rama, why dont you post this in forum feedback?
I am sufficiently angry about this that I dont trust myself to post in the public forum about this.
It really inconveniences me, feels rather Draconian, and also leaks my perhaps sensitive game code to an online database that has no business knowing what I am doing.
Please Allow Me The Option To Not Send My Data To Online Server
Maybe I also dont want to waste my internet connection sending reports that I know are my fault/deliberate design choice as a C++ programmer?
And dont tell me to force-close the window via my task bar
You are limiting my freedom in ways that do not affect BP-only users, but greatly affect me.
There’s no way this change was designed with C++ programmers in mind, as it wouldn’t help you to know about crashes in our game code that are our own doing. You didnt write the code, why would you want to know that it crashed?
Yet now I am forced to take extra measures to avoid publishing crash reports that are not relevant for you to know about and just waste space on your servers.
Your change makes my development cycle take unnecessarily longer, as I crash my games all the time, and it is my responsability to fix it, not yours, but your decision makes my entire development cycle longer with the halt, “oh wait…why is this window not closing? Omg I cant close this window any more… right click on task bar icon, close window, go back to what I was doing…what was I doing again? … I better report this…”
Epic, I love you, but I intensely dislike this decision. note the difference please, Love you, dont like decision.
And I dont want to have to live with your decision on this matter for the rest of my life, cause I will be using UE4 for life.
And I dont want to have to compile a custom engine version just to fix this.
Oh please
Honor my plea
Give me an option to re-enable that xmark
Rama
PS: dont anyone tell me that I spent longer writing this plea than I would right clicking to close the task bar window, I crash my games 20+ times per day sometimes, often deliberately, checking for code execution paths that should never happen. 20 x 365 x 15 seconds = 1,825 minutes per year, and for 100 years that is 3,041.67 hours of Rama lifetime spent closing ue4 crash reporters post 4.12.