You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not familiar with the aforementioned projects but I was wondering if something like Sentry would be a good fit for consuming the crash reports, they have a free self hosted option. For the engine itself, it could be useful to have the information publicly accessible.
You would probably want a way to differentiate between crashes caused by code written by the game developer (which resorts should go to them) versus engine crashes. Maybe they can be triaged and forwarded, can this be deduced from stack traces?
The client that is used to send this data should be configurable as for the server, offering indeed popular options, but also self hosted if people want.
Initially we would want to collect this data, and then have an easy way to specify how this data is uploaded.
If it were to sentry, while maybe industry standard? maybe not, idk, we have to consider also to not lock people in to one option, and offer them option to again self host and receive this data (if they want to)
https://github.com/chromium/crashpad?tab=readme-ov-file
https://github.com/google/breakpad
The text was updated successfully, but these errors were encountered: