The main issue that will probably always keep us from having a glitchless leaderboard here is the difficulty of defining what qualifies as a glitch. There are some obvious restrictions that would be made, but the finer details are contended.

I did some glitchless runs of Spyro 3 Any% last year with a relatively strict ruleset. You can compare to those attempts and look at my routes if you'd like to. I outlined the rules I used for the run in the description of my PB video.

I'm hoping that CabbageDevourer responds to this since I'm only a moderator of this game to make sure the boards are still functioning. I'd like to avoid changing rules if I can since I don't have a nuanced understanding of how any rule change might affect these leaderboards. With that said, the Spyro community is usually fairly strict with which emulators are allowed and we allow DuckStation. It's not perfect, but, for Spyro, it's more accurate than ePSXe. If there are no responses to this thread for 2 weeks, I'll ask around a little bit and then probably change the rules to allow it.

I added you as a moderator.

Sign me up.

General Clarified Submission Rules

I. Visual Evidence Requirements • All new submissions without video evidence require visual evidence. • Accepted forms of visual evidence include screenshots/pictures of the completed splits for full-game categories and, for individual level categories, screenshots/pictures of the in-game results screen. • Visual evidence should be linked in the “Comment” submission section.

II. Video Evidence Requirements • A new submission that achieves a time in the top 50% requires video evidence unless more than 20 unique runners have submitted to the category. In this case, any time within the top 10 requires video evidence. • Videos must be adequately complete. • If the video is composed of multiple parts, only the first should be included in the “Video Link” submission section. The remainder should be included in the “Comment” submission section.

III. General Timing Requirements • The initial and final splits must be consistent with the timing rules of the specific category.

IV. Timing Precision Requirements • Full-game categories require timing precise to the second. • Individual level categories are timed with the in-game timer.

V. Region and Platform Specification Requirements • Region and platform specification is mandatory.

VI. Emulator Indication Requirements • If an emulator was used, indication of that use is mandatory. • If an emulator was used, specification of that emulator is mandatory and should be included in the “Comment” submission section.

VII. Pause Allowance • One untimed pause is allowed for every two hours of gameplay.

VIII. Rejection Appeal Allowance • If you believe your run was unfairly rejected, you may appeal the rejection by messaging a leaderboard moderator privately.

Note: Clarification of emulator rules will be available after the topic has been sufficiently discussed.