You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: mods/guidelines.md
+14-14Lines changed: 14 additions & 14 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -90,6 +90,20 @@ if (this->querySelector("hjfod.gdshare/export-button")) {
90
90
```
91
91
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!
92
92
93
+
## Mods using Generative AI
94
+
95
+
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.
96
+
97
+
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.
98
+
99
+
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.
100
+
101
+
Mods must not use generative AI for **any public asset**, including mod icons, sprites, and the various descriptions (about, changelog, etc.).
102
+
103
+
This policy **does not apply** to content _outside_ of the mod submission, such as backend servers used by the mod or external companion tools.
104
+
105
+
If you believe that your mod was erroneously rejected for generative AI use, please reach out to an index staff.
106
+
93
107
## Mods modifying the Geode UI
94
108
95
109
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
145
159
146
160
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.
147
161
148
-
## Mods using Generative AI
149
-
150
-
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.
151
-
152
-
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.
153
-
154
-
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.
155
-
156
-
Mods must not use generative AI for **any public asset**, including mod icons, sprites, and the various descriptions (about, changelog, etc.).
157
-
158
-
This policy **does not apply** to content _outside_ of the mod submission, such as backend servers used by the mod or external companion tools.
159
-
160
-
If you believe that your mod was erroneously rejected for generative AI use, please reach out to an index staff.
161
-
162
162
## Hateful conduct
163
163
164
164
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:**
0 commit comments