The games error reporting needs a lot of work. For example, in some cases adding a single line to an xtbl can exceed the max size of a string pool. This is a problem and can cause bugs, but it doesn't always crash the game, and it doesn't notify the users. To fix this I imagine something like this:
- [ ] When problems like this are detected log them (see #44) and then display them in a warnings/error window in the reconstructor overlay.
- [ ] For serious problems display a notification is one of the corners of the screen (make this toggleable)
- [ ] Attempt to provide solutions to the problem. E.g. if we detect a mempool overrun tell the user to close the game, edit the pool size in the config file (complete #49 first), and start the game again.
The games error reporting needs a lot of work. For example, in some cases adding a single line to an xtbl can exceed the max size of a string pool. This is a problem and can cause bugs, but it doesn't always crash the game, and it doesn't notify the users. To fix this I imagine something like this:
- [ ] When problems like this are detected log them (see #44) and then display them in a warnings/error window in the reconstructor overlay.
- [ ] For serious problems display a notification is one of the corners of the screen (make this toggleable)
- [ ] Attempt to provide solutions to the problem. E.g. if we detect a mempool overrun tell the user to close the game, edit the pool size in the config file (complete #49 first), and start the game again.