Why in-game timer ?

Using real-time clock would create a barrier of entry, not everyone has the mean to reliably time their runs. It would also make runs verification harder, and cheating easier. Real-time clock would also make segmented runs impossible (see next point). The in-game timer is precise enough (down to the second), a full run lasts long enough to make ties extremely rare. And to quote RWhiteGoose - a famous GoldenEye 64 runner - : "who are we to contradict the game ?!". On that note, I invite you to watch his video on this topic as it fits Blue Stinger too :

Why segmented runs are allowed ?

Again, I don't want to create a barrier of entry for (new) runners. Not everyone can sit and play for 2-3 hours at once, I don't want to prevent people with medical condition or kids from playing this game when there is no valid reason to ban segmented runs. Plus, segmented runs don't give any advantage, if anything, the need to save the game makes you lose time.

Missing categories ?

Ideally, the game should be divided in a huge amount of different categories. Easy, Normal, Hard, Easy NG+, Normal NG+, Hard NG+, Easy NG+ Mad mode, etc etc etc. Not an issue in and of itself, but Blue Stinger community is pretty small, everyone would be first with no competition and competition is what most likely brings you here in the first place. If a category is currently missing (NTSC-J Normal NG+ no mad mode for instance) and you desire to run it, I will create the category. In the mean time, I think it's better to keep the leaderboard as tidy as possible so long as there are only a handful of runners.

How does the verification process works ?

Again, we are just a handful of runners so far, so I can get to know and remember each one of us. If I can establish that you have the skill and knowledge to do a low time, then I won't ask for as much proofs for all subsequent runs. If you made a well documented run and beat your time the "next day" with only a picture of the in-game timer screen, I will trust you. Keep in mind that someone can question one of your runs and if I can't make a strong case in your favor then I won't have any choice but to notify you that I will reject your run. Though, you will be notified in advance and have a chance to defend yourself and provide further proof(s).

What about emulated runs ?

They will have to be in a different category. As an example, if the emulator is off by 0.1Hz, you could get a few second (dis)advantage compared to people who play on Dreamcast hardware.

I hope everything makes sense to you, that you can understand where I'm coming from and what motivated my choices when creating the rules. Nothing is set in stone (I won't change the rules overnight though, it wouldn't be fair), I'm willing to discuss or argue any point in this list and find a consensus.

Sorry for the late reply, I didn't get a notification, I saw your post randomly. I've just changed the rules, from now on, we'll have to have a video proof. I've been operating on trust so far, for instance, Neon made a run on emulator for me so he could show me that he had the knowledge/skill to actually make such a low time. That's why I accepted his time, he has since beat it anyway.

As for Goose's video, not everything was relevant, but there were some good points that I was afraid that I missed in my post. That's why I thought it would be a good idea to link it.