Most of those are "fake" errors. e.g. "No quests found with condition type items-at-rank-3" isn't actually an error as I never added any quests for ranking up items to rank 3 (silver stars). The code was written for use under the assumption that I (or anyone else using it) would know beforehand if there are any quests under a certain category before trying to reference which ones they are. And that's a good thing usually. I just never added a complementary function to test whether there are any such quests, something like quests.quests_exist_for_condition_type(condition_type). Then, the "errors" can be silenced without removing that assumption.
That said, only one of those errors looks like a real, critical error to me, the negative coin values one. That sounds to me like I may not have checked whether a coin subtraction operation was valid before doing so (a - b should only happen when a >= b in that context). I'll have to find out where that is. And the "tried to define rank for ... hex-coin" is slightly concerning as it indicates a misuse of data somewhere, but nothing should be broken.
The "no items found near value ..." usually occurs on Aquilo because item values are very spread apart. It means that some hex cores on Aquilo will have fewer trades than normal in them, which is partly a bad thing, but also partly not the worst thing ever because at that point, you can rank anything up to silver rank and find any item you want on Aquilo or any other planet. I should probably just suppress the error and call it a day, lol. No one will know the difference xD!
Thanks again for the reports!
