From ec81ee208840328d905f3e384053d4f91a2dacc9 Mon Sep 17 00:00:00 2001 From: Chloe <25387744+qimiko@users.noreply.github.com> Date: Fri, 7 Aug 2026 22:31:23 -0700 Subject: [PATCH 1/5] Update guidelines.md --- mods/guidelines.md | 22 ++++++++++++++++++---- 1 file changed, 18 insertions(+), 4 deletions(-) diff --git a/mods/guidelines.md b/mods/guidelines.md index 2b73bcf9..c44f27ae 100644 --- a/mods/guidelines.md +++ b/mods/guidelines.md @@ -38,8 +38,8 @@ A mod found breaking any of these rules will be **rejected unconditionally** fro * (`reject-bad-metadata`) The mod **does not have appropriate metadata**. All mods on the Index must have a proper name, description, icon, and tags, [including jokes](#joke-mods). * (`reject-enshittification`) The mod **removes Vanilla features** for no good reason. * (`reject-runtime-code`) The mod **installs and runs arbitary code**. You are not allowed to install other mods from outside the Geode index. There are two exceptions to this rule: mods that introduce some sort of scripting system that runs *sandboxed* arbitary code, and mods installing additional paid features as a runtime library. Do note that for the purposes of verification, the code for all of those paid features must be included, including the code used to load them. - * (`reject-vibecoded`) The mod's **codebase entirely or mostly consists of AI-generated code**. If it appears the programmer does not understand the code that has been generated and is trying to get vibecoded mods on the index, this will result in a rejection. Using AI tools to boost productivity is fine, but fully vibecoding mods will inevitably lead to instability and crashes. - * (`reject-llm`) The mod **adds an LLM to the game** that does not [adhere to our rules on generative AI](#mods-using-generative-ai). + * (`reject-vibecoded`) The mod's **codebase entirely or mostly consists of AI-generated code**. If it appears the programmer does not understand the code that has been generated and is trying to get vibecoded mods on the index, this will result in a rejection. Using AI tools to boost productivity is fine, but fully vibecoding mods will inevitably lead to instability and crashes. For more information, see the section on [using generative AI](#mods-using-generative-ai). + * (`reject-llm`) The mod **adds an LLM to the game** that does not [adhere to our rules on generative AI](#mods-with-generative-ai-features). A mod found breaking any of these rules will likely be rejected, although depending on the situation, they could also still be approved. @@ -130,9 +130,9 @@ Sometimes rather than making original ideas, modders want to for one reason or a * The new mod must have some **meaningful changes** compared to the original, for example major bugfixes or a port to a new GD version. Simply repackaging Click Between Frames as Superb Input Precision is not allowed. * The original mod and mod developer **must be credited in `about.md`**, as per the no stealing rule. -## Mods using Generative AI +## Mods with Generative AI features -> :information_source: Note that mods *coded* using Generative AI are subject to [different rules](#rejection-rules); this section is about mods that bring Generative AI into the game itself +> :information_source: Note that mods *coded* using Generative AI are subject to [different rules](#mods-using-generative-ai); this section is about mods that bring Generative AI into the game itself Due to controversy among developers regarding the subject, mods that utilize **Generative AI** have to follow these additional guidelines in relation to their AI usage. @@ -145,6 +145,20 @@ Due to controversy among developers regarding the subject, mods that utilize **G In addition, all mods utilizing AI **must be manually verified** on the index and **approved unilaterally by Geode lead developers**, regardless of whether the developer is verified on the index or not. +## Mods using Generative AI + +Mods that use generative AI for anything on a mod's repository **must disclose their usage** in a location accessible to reviewers. This may be the mod's `ABOUT.md`, the repository's `README.md`, or as a comment on the mod submission. This disclosure must be in detail, describing where in the codebase generative AI was used and how it was used. Usage of LLMs for review or planning does not have to be disclosed, as long as those conversations _do not end up in the repository_. Developers found being **intentionally dishonest** about their use of AI for development will have their mod removed, and may be banned from the index. + +Our expectation is that AI generated code **must be exceptional**. The code must be clean and well-documented, and the mod itself **must be thoroughly tested**. Compatibility issues with other mods **must be resolved** prior to submission. We expect **all testing** to be provably **done by humans**. Enforcement of this policy is left [up to individual reviewers](#everything-is-situational). Reviewers are under no obligation to explain why a mod was rejected for generative AI use. + +Please respect the time of our human reviewers. The developer must be fully accountable for their codebase, and should not need to consult a LLM when asked questions about it. If a reviewer or another developer is expected to read something, it should not be written by an LLM. This means that _all documentation_ (including the disclosure notice) must be human-written. + +Mods must not use generative AI for **any public asset**, including mod icons, sprites, and the various descriptions (about, changelog, etc.). + +This policy **does not apply** to content _outside_ of the mod submission, such as backend servers used by the mod or external companion tools. + +If you believe that your mod was erroneously rejected for generative AI use, please reach out to an index staff. + ## Hateful conduct Developers may be banned off the mods index and other Geode-related online spaces such as the Discord server and the GitHub organization, if they have committed acts in *or outside* the Geode community that are considered hateful, harmful, or otherwise detestable. **These include, but are not limited to:** From fbe88e8b6720c70d64ae1945da9d800bfb37c840 Mon Sep 17 00:00:00 2001 From: Chloe <25387744+qimiko@users.noreply.github.com> Date: Fri, 7 Aug 2026 23:25:00 -0700 Subject: [PATCH 2/5] move section closer to top --- mods/guidelines.md | 28 ++++++++++++++-------------- 1 file changed, 14 insertions(+), 14 deletions(-) diff --git a/mods/guidelines.md b/mods/guidelines.md index c44f27ae..7a4d4d14 100644 --- a/mods/guidelines.md +++ b/mods/guidelines.md @@ -90,6 +90,20 @@ if (this->querySelector("hjfod.gdshare/export-button")) { ``` Checking that another mod is loaded by looking for identifying effects of them in the game is completely fine, as long as the checks are safe and don't make assumptions about things that haven't been checked. For example, just doing `Loader::get()->isModLoaded("hjfod.gdshare")` is NOT enough to guarantee all of GDShare's buttons exist, so you should always check for the buttons themselves! +## Mods using Generative AI + +Mods that use generative AI for anything on a mod's repository **must disclose their usage** in a location accessible to reviewers. This may be the mod's `ABOUT.md`, the repository's `README.md`, or as a comment on the mod submission. This disclosure must be in detail, describing where in the codebase generative AI was used and how it was used. Usage of LLMs for review or planning does not have to be disclosed, as long as those conversations _do not end up in the repository_. Developers found being **intentionally dishonest** about their use of AI for development will have their mod removed, and may be banned from the index. + +Our expectation is that AI generated code **must be exceptional**. The code must be clean and well-documented, and the mod itself **must be thoroughly tested**. Compatibility issues with other mods **must be resolved** prior to submission. We expect **all testing** to be provably **done by humans**. Enforcement of this policy is left [up to individual reviewers](#everything-is-situational). Reviewers are under no obligation to explain why a mod was rejected for generative AI use. + +Please respect the time of our human reviewers. The developer must be fully accountable for their codebase, and should not need to consult a LLM when asked questions about it. If a reviewer or another developer is expected to read something, it should not be written by an LLM. This means that _all documentation_ (including the disclosure notice) must be human-written. + +Mods must not use generative AI for **any public asset**, including mod icons, sprites, and the various descriptions (about, changelog, etc.). + +This policy **does not apply** to content _outside_ of the mod submission, such as backend servers used by the mod or external companion tools. + +If you believe that your mod was erroneously rejected for generative AI use, please reach out to an index staff. + ## Mods modifying the Geode UI Some mods may want to **extend Geode's own UI**, for example to add custom features to their own mod's page. This is allowed, however with some caveats. See [the tutorial page](/tutorials/modify-geode) for more. @@ -145,20 +159,6 @@ Due to controversy among developers regarding the subject, mods that utilize **G In addition, all mods utilizing AI **must be manually verified** on the index and **approved unilaterally by Geode lead developers**, regardless of whether the developer is verified on the index or not. -## Mods using Generative AI - -Mods that use generative AI for anything on a mod's repository **must disclose their usage** in a location accessible to reviewers. This may be the mod's `ABOUT.md`, the repository's `README.md`, or as a comment on the mod submission. This disclosure must be in detail, describing where in the codebase generative AI was used and how it was used. Usage of LLMs for review or planning does not have to be disclosed, as long as those conversations _do not end up in the repository_. Developers found being **intentionally dishonest** about their use of AI for development will have their mod removed, and may be banned from the index. - -Our expectation is that AI generated code **must be exceptional**. The code must be clean and well-documented, and the mod itself **must be thoroughly tested**. Compatibility issues with other mods **must be resolved** prior to submission. We expect **all testing** to be provably **done by humans**. Enforcement of this policy is left [up to individual reviewers](#everything-is-situational). Reviewers are under no obligation to explain why a mod was rejected for generative AI use. - -Please respect the time of our human reviewers. The developer must be fully accountable for their codebase, and should not need to consult a LLM when asked questions about it. If a reviewer or another developer is expected to read something, it should not be written by an LLM. This means that _all documentation_ (including the disclosure notice) must be human-written. - -Mods must not use generative AI for **any public asset**, including mod icons, sprites, and the various descriptions (about, changelog, etc.). - -This policy **does not apply** to content _outside_ of the mod submission, such as backend servers used by the mod or external companion tools. - -If you believe that your mod was erroneously rejected for generative AI use, please reach out to an index staff. - ## Hateful conduct Developers may be banned off the mods index and other Geode-related online spaces such as the Discord server and the GitHub organization, if they have committed acts in *or outside* the Geode community that are considered hateful, harmful, or otherwise detestable. **These include, but are not limited to:** From eb50eaa1291b26255b42e6656c53373c8746d8dc Mon Sep 17 00:00:00 2001 From: Chloe <25387744+qimiko@users.noreply.github.com> Date: Sat, 8 Aug 2026 02:43:43 -0700 Subject: [PATCH 3/5] update guidelines after discussion --- mods/guidelines.md | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) diff --git a/mods/guidelines.md b/mods/guidelines.md index 7a4d4d14..8670a50c 100644 --- a/mods/guidelines.md +++ b/mods/guidelines.md @@ -92,17 +92,19 @@ Checking that another mod is loaded by looking for identifying effects of them i ## Mods using Generative AI +Mods programmed primarily with LLM assistance pose a unique set of challenges to the index. Developers of these mods tend to prioritize the end product over the code (and effort) required to create it, viewing the mod more as a toy than a project. This results in a mod that initially seems to function, but falls apart over time, especially once the developers lose interest in their mod. For the sake of users and other developers, we have to be confident that mod developers will remain invested in maintaining their mod. We also want to ensure that those developers have the skills necessary to update their own code when incompatibilities or bugs appear. + Mods that use generative AI for anything on a mod's repository **must disclose their usage** in a location accessible to reviewers. This may be the mod's `ABOUT.md`, the repository's `README.md`, or as a comment on the mod submission. This disclosure must be in detail, describing where in the codebase generative AI was used and how it was used. Usage of LLMs for review or planning does not have to be disclosed, as long as those conversations _do not end up in the repository_. Developers found being **intentionally dishonest** about their use of AI for development will have their mod removed, and may be banned from the index. -Our expectation is that AI generated code **must be exceptional**. The code must be clean and well-documented, and the mod itself **must be thoroughly tested**. Compatibility issues with other mods **must be resolved** prior to submission. We expect **all testing** to be provably **done by humans**. Enforcement of this policy is left [up to individual reviewers](#everything-is-situational). Reviewers are under no obligation to explain why a mod was rejected for generative AI use. +AI generated code should be _kept to a minimum_. This code **must be thoroughly tested** and kept to a reasonable standard of **maintainability**. This code should not create **incompatibilities** with other mods. We expect all testing to be provably **done by humans**. Enforcement of this policy is left [up to individual reviewers](#everything-is-situational). Index Staff are under no obligation to explain why a mod was rejected for generative AI use. -Please respect the time of our human reviewers. The developer must be fully accountable for their codebase, and should not need to consult a LLM when asked questions about it. If a reviewer or another developer is expected to read something, it should not be written by an LLM. This means that _all documentation_ (including the disclosure notice) must be human-written. +Please respect the time of our human reviewers. The developer must be fully accountable for their codebase, and should not need to consult a LLM when asked questions about it. If an Index Staff or another developer is expected to read something, it should not be written by an LLM. This means that _all documentation_ (including the disclosure notice) must be human-written. Mods must not use generative AI for **any public asset**, including mod icons, sprites, and the various descriptions (about, changelog, etc.). This policy **does not apply** to content _outside_ of the mod submission, such as backend servers used by the mod or external companion tools. -If you believe that your mod was erroneously rejected for generative AI use, please reach out to an index staff. +If you believe that your mod was erroneously rejected for generative AI use, please reach out to an Index Staff. ## Mods modifying the Geode UI From 6511de94e182791fafdfefe92ab4bd8bce9b03f6 Mon Sep 17 00:00:00 2001 From: Chloe <25387744+qimiko@users.noreply.github.com> Date: Sat, 8 Aug 2026 06:10:09 -0700 Subject: [PATCH 4/5] expand on sentence about incompatibilities --- mods/guidelines.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/mods/guidelines.md b/mods/guidelines.md index 8670a50c..a66a71a5 100644 --- a/mods/guidelines.md +++ b/mods/guidelines.md @@ -92,11 +92,11 @@ Checking that another mod is loaded by looking for identifying effects of them i ## Mods using Generative AI -Mods programmed primarily with LLM assistance pose a unique set of challenges to the index. Developers of these mods tend to prioritize the end product over the code (and effort) required to create it, viewing the mod more as a toy than a project. This results in a mod that initially seems to function, but falls apart over time, especially once the developers lose interest in their mod. For the sake of users and other developers, we have to be confident that mod developers will remain invested in maintaining their mod. We also want to ensure that those developers have the skills necessary to update their own code when incompatibilities or bugs appear. +Mods programmed primarily with LLM assistance pose a unique set of challenges to the index. Developers of these mods tend to prioritize the end product over the code (and effort) required to create it, viewing the mod more as a toy than a project. This results in a mod that initially seems to function, but falls apart over time, especially once the developers lose interest in their mod. For the sake of users and other developers, we have to be confident that mod developers will remain invested in maintaining their mod. We also want to verify that those developers have the skills necessary to update their own code when incompatibilities or bugs appear. Mods that use generative AI for anything on a mod's repository **must disclose their usage** in a location accessible to reviewers. This may be the mod's `ABOUT.md`, the repository's `README.md`, or as a comment on the mod submission. This disclosure must be in detail, describing where in the codebase generative AI was used and how it was used. Usage of LLMs for review or planning does not have to be disclosed, as long as those conversations _do not end up in the repository_. Developers found being **intentionally dishonest** about their use of AI for development will have their mod removed, and may be banned from the index. -AI generated code should be _kept to a minimum_. This code **must be thoroughly tested** and kept to a reasonable standard of **maintainability**. This code should not create **incompatibilities** with other mods. We expect all testing to be provably **done by humans**. Enforcement of this policy is left [up to individual reviewers](#everything-is-situational). Index Staff are under no obligation to explain why a mod was rejected for generative AI use. +AI generated code should be _kept to a minimum_. This code **must be thoroughly tested** and kept to a reasonable standard of **maintainability**. We expect all testing to be provably **done by humans**. We understand that _some issues cannot be resolved_, especially when it comes to compatibility issues. However, relating back to maintainability, AI generated code may be held to **higher standards** when it comes to major bugs or incompatibilities. (Ideally a mod would not contain enough AI generated code for this to be a concern.) Enforcement of this policy is left [up to individual reviewers](#everything-is-situational). Index Staff are under no obligation to explain why a mod was rejected for generative AI use. Please respect the time of our human reviewers. The developer must be fully accountable for their codebase, and should not need to consult a LLM when asked questions about it. If an Index Staff or another developer is expected to read something, it should not be written by an LLM. This means that _all documentation_ (including the disclosure notice) must be human-written. From 5baec4cb8ab049488736b93056b26bcd77cc29e0 Mon Sep 17 00:00:00 2001 From: Chloe <25387744+qimiko@users.noreply.github.com> Date: Fri, 14 Aug 2026 13:37:37 -0700 Subject: [PATCH 5/5] make disclosure policies a little looser --- mods/guidelines.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/mods/guidelines.md b/mods/guidelines.md index a66a71a5..dc565ef2 100644 --- a/mods/guidelines.md +++ b/mods/guidelines.md @@ -92,19 +92,19 @@ Checking that another mod is loaded by looking for identifying effects of them i ## Mods using Generative AI -Mods programmed primarily with LLM assistance pose a unique set of challenges to the index. Developers of these mods tend to prioritize the end product over the code (and effort) required to create it, viewing the mod more as a toy than a project. This results in a mod that initially seems to function, but falls apart over time, especially once the developers lose interest in their mod. For the sake of users and other developers, we have to be confident that mod developers will remain invested in maintaining their mod. We also want to verify that those developers have the skills necessary to update their own code when incompatibilities or bugs appear. +Mods programmed primarily with LLM assistance create unique challenges for the index. Developers of these mods tend to prioritize the end product over the code (and effort) required to create it, viewing the mod more as a toy than a project. This results in a mod that initially seems to function, but falls apart over time, especially once the developers lose interest in their mod. For the sake of users and other developers, we have to be confident that mod developers will remain invested in maintaining their mod. We also want to verify that those developers have the skills necessary to update their own code when incompatibilities or bugs appear. -Mods that use generative AI for anything on a mod's repository **must disclose their usage** in a location accessible to reviewers. This may be the mod's `ABOUT.md`, the repository's `README.md`, or as a comment on the mod submission. This disclosure must be in detail, describing where in the codebase generative AI was used and how it was used. Usage of LLMs for review or planning does not have to be disclosed, as long as those conversations _do not end up in the repository_. Developers found being **intentionally dishonest** about their use of AI for development will have their mod removed, and may be banned from the index. +Mods that use generative AI for any significant portions of a mod's repository **must disclose their usage** in a location accessible to reviewers. This may be the mod's `ABOUT.md`, the repository's `README.md`, or as a comment on the mod submission. This disclosure must be in detail, describing where in the codebase generative AI was used and how it was used. Usage of LLMs for review or planning does not have to be disclosed, as long as those conversations _do not end up in the repository_. Usage of generative AI for minor portions of code (e.g. repetitive tasks) does not have to be disclosed, but it is encouraged to avoid issues during review (disclosure in these cases can be a comment near the generated code). Developers found being **intentionally dishonest** about their use of AI for development will have their mod removed, and may be banned from the index. -AI generated code should be _kept to a minimum_. This code **must be thoroughly tested** and kept to a reasonable standard of **maintainability**. We expect all testing to be provably **done by humans**. We understand that _some issues cannot be resolved_, especially when it comes to compatibility issues. However, relating back to maintainability, AI generated code may be held to **higher standards** when it comes to major bugs or incompatibilities. (Ideally a mod would not contain enough AI generated code for this to be a concern.) Enforcement of this policy is left [up to individual reviewers](#everything-is-situational). Index Staff are under no obligation to explain why a mod was rejected for generative AI use. +AI generated code should be _kept to a minimum_. This code **must be thoroughly tested** and kept to a reasonable standard of **maintainability**. We expect all testing to be provably **done by humans**. We understand that _some issues cannot be resolved_, especially when it comes to compatibility issues. However, relating back to maintainability, AI generated code may be held to **higher standards** when it comes to major bugs or incompatibilities. (Ideally a mod would not contain enough AI generated code for this to be a concern.) Please respect the time of our human reviewers. The developer must be fully accountable for their codebase, and should not need to consult a LLM when asked questions about it. If an Index Staff or another developer is expected to read something, it should not be written by an LLM. This means that _all documentation_ (including the disclosure notice) must be human-written. -Mods must not use generative AI for **any public asset**, including mod icons, sprites, and the various descriptions (about, changelog, etc.). +Mods must not use generative AI for **any public asset**, including mod icons, sprites, and metadata (about, changelog, etc.). This policy **does not apply** to content _outside_ of the mod submission, such as backend servers used by the mod or external companion tools. -If you believe that your mod was erroneously rejected for generative AI use, please reach out to an Index Staff. +Enforcement of this policy is left [up to individual reviewers](#everything-is-situational). Index Staff are under no obligation to explain why a mod was rejected for generative AI use. If you believe that your mod was erroneously rejected for generative AI use, please reach out to an Index Staff. ## Mods modifying the Geode UI