From d30e7d63aed4c9a92e1c1d7126bff19ac4fa7c32 Mon Sep 17 00:00:00 2001
From: Homuki <61800700+Homuki@users.noreply.github.com>
Date: Thu, 5 Feb 2026 15:12:38 +0100
Subject: [PATCH] Update to Requesting Review rules

Updated requirements for requesting a review, including having an set plan approved, and linking to the set plan thread.
---
 docs/developer-docs/am-i-ready-for-review.md | 3 ++-
 1 file changed, 2 insertions(+), 1 deletion(-)

diff --git a/docs/developer-docs/am-i-ready-for-review.md b/docs/developer-docs/am-i-ready-for-review.md
index 92e035db..3d23dc2f 100644
--- a/docs/developer-docs/am-i-ready-for-review.md
+++ b/docs/developer-docs/am-i-ready-for-review.md
@@ -15,9 +15,10 @@ Tips for testing:
 # Requesting a Review
 
 Before you request a review on your set, it must be clear of bad practices. In particular, you must use [AutoCR](https://authorblues.github.io/retroachievements/AutoCR/) and go through every issue it flags. As with any automatic feedback tool, it is not perfect, and flags can sometimes be ignored. It is still invaluable to identify issues with your set, especially while you are still learning. In your Ready for Review post on #jr-devs-request, you must:
-- Have had the claim for at least 7 days
+- Have an approved Set Plan for at least 7 days
 - Explain your testing process
 - Link to the Unpublished achievement page for your game
+- Include a link to Set Plan Review thread
 - Link to the AutoCR page for the set (using the Load by Game ID feature)
 - Explain why any issue flagged by AutoCR has been ignored