@Ethan re: github.com/ShearOfDoom/Cactus/commit/…: I did it that way so they knew that 1.) they didn't do something wrong 2.) they wouldn't be asked to submit a Cactus bug report when the developer should be the one submitting it 3.) wouldn't be asking us for support for a developer's bug
I was thinking that the game developer could contact us themselves, and give us more helpful information than the average player
> Something wrong internally happened (not your fault!). This may be an issue with the game itself, or the underlying components. To help fix this issue, please contact the developers of the game with the error report in this location:
Also, RE: github.com/ShearOfDoom/Cactus/commit/…: I'm confused on if this is a constant or not. The class doesn't mutate itself, but it mutates the internal components
I think by constants that they mean literal stuff like PI = 3.14
@EthanBierlein ok
I'm actually really excited with this error-handling thing. It's a cool feature that we might want to advertise ("gracefully generates error logs when exceptions thrown, and gracefully notifies the user to send in the error report")