From b37186287a19a070d00956c4c05366762094bd26 Mon Sep 17 00:00:00 2001 From: Adrianus Kleemans Date: Wed, 15 Oct 2025 18:23:21 +0200 Subject: [PATCH 1/3] Update leaderboards.md Remove confusing part of sentence --- docs/developer-docs/leaderboards.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developer-docs/leaderboards.md b/docs/developer-docs/leaderboards.md index 2630ccfb..372fb6f9 100644 --- a/docs/developer-docs/leaderboards.md +++ b/docs/developer-docs/leaderboards.md @@ -55,7 +55,7 @@ The best place to start is to look at existing leaderboards and break it down to The **Title/Description** fields are quite obvious. -The **Type** is "Time (Frames)". The value we're tracking updates once a frame, and the Genesis runs at 60 frames per second. (see not below for systems that run at other speeds) +The **Type** is "Time (Frames)". The value we're tracking updates once a frame, and the Genesis runs at 60 frames per second. The **Lower Is Better** flag is checked, then the one who makes the shortest time will be the #1. From a7d29e43bc6f88da8f4aa395ac0f3f558363b645 Mon Sep 17 00:00:00 2001 From: Adrianus Kleemans Date: Wed, 15 Oct 2025 20:16:54 +0200 Subject: [PATCH 2/3] Update leaderboard documentation for frame rate details Clarify the frame rate context for the leaderboard type. --- docs/developer-docs/leaderboards.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developer-docs/leaderboards.md b/docs/developer-docs/leaderboards.md index 372fb6f9..a63e1df4 100644 --- a/docs/developer-docs/leaderboards.md +++ b/docs/developer-docs/leaderboards.md @@ -55,7 +55,7 @@ The best place to start is to look at existing leaderboards and break it down to The **Title/Description** fields are quite obvious. -The **Type** is "Time (Frames)". The value we're tracking updates once a frame, and the Genesis runs at 60 frames per second. +The **Type** is "Time (Frames)". The value we're tracking updates once a frame, and the Genesis runs at 60 frames per second (see note below on [Value Definition](/developer-docs/value-definition) for systems that run at other speeds). The **Lower Is Better** flag is checked, then the one who makes the shortest time will be the #1. From 717de36246815f41761099cd3b4430423af8e5d9 Mon Sep 17 00:00:00 2001 From: Adrianus Kleemans Date: Wed, 15 Oct 2025 20:19:00 +0200 Subject: [PATCH 3/3] Fix link in leaderboards documentation Updated link in the Type section for clarity. --- docs/developer-docs/leaderboards.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/developer-docs/leaderboards.md b/docs/developer-docs/leaderboards.md index a63e1df4..75e6a095 100644 --- a/docs/developer-docs/leaderboards.md +++ b/docs/developer-docs/leaderboards.md @@ -55,7 +55,7 @@ The best place to start is to look at existing leaderboards and break it down to The **Title/Description** fields are quite obvious. -The **Type** is "Time (Frames)". The value we're tracking updates once a frame, and the Genesis runs at 60 frames per second (see note below on [Value Definition](/developer-docs/value-definition) for systems that run at other speeds). +The **Type** is "Time (Frames)". The value we're tracking updates once a frame, and the Genesis runs at 60 frames per second (see note below on [Value Format](/developer-docs/leaderboards#value-format) for systems that run at other speeds). The **Lower Is Better** flag is checked, then the one who makes the shortest time will be the #1.