For some reason the error report analytics doesnt always report all warnings or errors even if they happen frequently.
I’ve been trying to fix a save corruption bug for the past 2 years where certain parts randomly disappear and was able to join someone who was currently experiencing the issue.
When i took a look at the developer console i saw warnings i could find in the analytics and for some reason a new warning which i couldnt find in the analytics for some weird reason despite it always being warned alongside the warning i can find.
The crucial info for fixing the bug for some reason is never logged to the analytics.
Hi Rick:
I checked your reporting and found that you have a lot of warnings logging just pure username.
We have limit of 500 unique warnings for now and logging username will quickly use up all the quota and other warnings will be dropped.
I suggest you change your warnings to not log username and see if it helps.
We are working on improving the limit and reduce noise to help better debugging.
Hi. We are working on some improvements for error logging.
A limit bump would also be something we are considering.
But because some creators log random ids/names/coordinates in the log, to make sure they do not explode our system so everyone can have a fast and reliable system, we have to setup a limit.
If you are actively using error log, please try not to log random info in the log so it can populate real useful logs to you in time.
Thanks for reporting this issue.
We will consider adding a user input regex filtering to remove logs you might not think actionable on your side so more important logs can pop up on your dashboard.