#Crash-reports database + more easy-to-read crashes

1 messages · Page 1 of 1 (latest)

finite bramble
#

Mods like to crash. Very often. More often than we want.

While crash-report for us, developers, kinda easy to understand, for regular players it can be something unknown and difficult. Or even player see any kind of crash-reports for first time.
But this is not a main problem. For most crashes solution can be found: update mod, update lovely, update Steamodded, etc. But this doesn't guarantees that user will search for same issue and use this already found solution.

That's why I'm thinking about mod/library/steamodded module, which main goal is (at least try to) resolve this problem.
If this crash have known solution (mod updating, new lovely version, etc), add this information to crash-log so user immidiately will know what to do.
If crash is unknown but general one (for example some field is nil or card doesn't have edition object), make it more self-explanatory to regular user.

Ideally, some database should exist which everyone can edit. Modded balatro wiki can be used, and mod will get information from wiki page about all known issues.

This might sound like a lot of work, because it is. But this can make modded expirience for new players more smooth.

What you think?