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
The idea is for mod authors to be able to instantly test the crashing environment by using the Minecraft instance that crashed.
Required data:
User input: what did you (the user) do to trigger the crash?
Save of crashing world
Mods
All config
More? Need to research what other context a Minecraft instance can have
Performance notes:
Since mods are very large, optimize by only saving id + version and downloading the mod itself later
Perhaps use GitHub Issues as hosting solution, that allows up to 25MB gzipped.
In cases where we must host it ourselves, the limit must be 1MB gzipped per crash.
Usability notes:
Must be explicitly opt-in, don't leak user's data
Must be very easy to use / obvious for high usage, context is very important.
I think, have a screen that allows uploading crash context (+crash) to the issues page of any GitHub repo. Prioritize uploading to suspected mods.
Where Github issues is not possible, have some way to upload to a custom issue tracker ( low priority )
In a perfect world where you can have the entire context in a very small file (<1MB), the best solution is to have it be part of Crashy. There would just be a 'try it yourself!' button.
The text was updated successfully, but these errors were encountered:
natanfudge
changed the title
Method for applying the entire Minecraft instance to crash reports
Method for attaching the entire Minecraft instance to crash reports
Sep 12, 2021
The idea is for mod authors to be able to instantly test the crashing environment by using the Minecraft instance that crashed.
Required data:
Performance notes:
Usability notes:
The text was updated successfully, but these errors were encountered: