Skip to content

Commit 2ce2948

Browse files
authored
add a note about how to track if your mod got accepted
1 parent edebb22 commit 2ce2948

1 file changed

Lines changed: 4 additions & 1 deletion

File tree

mods/publishing.md

Lines changed: 4 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -28,6 +28,9 @@ Submitting a mod to the official mod index is as follows:
2828
3. Navigate to [your user page](https://geode-sdk.org/me) by clicking your username in the top left corner
2929
4. Provide a **direct download link** to the .geode file (for example `https://github.com/HJfod/BetterEdit/releases/download/v6.3.3/hjfod.betteredit.geode`) in the **Submit a new mod** section.
3030

31+
## Did my mod get accepted?
32+
You can track the status of your mod on [your user page](https://geode-sdk.org/me) on the Geode website. Tracking pending mods is also available in CLI with `geode index mods pending` but rejection reasons are not available there.
33+
3134
## Releasing updates
3235

3336
To release an update using Geode CLI, use `geode index mods update`. You will have to be already logged in with the index to use this command.
@@ -38,7 +41,7 @@ If you are using GitHub releases (or any other system), **do not update an exist
3841

3942
Make sure to **increase your mod version** when updating it! You should be following [Semantic Versioning](https://semver.org), especially if you're developing a mod with a **public API**.
4043

41-
If you are a **verified** developer, then the update will automatically be accepted onto the index, without the need of approval from an **index admin**.
44+
If you are a **verified** developer, then the update will automatically be accepted onto the index, without the need of approval from an **index admin**. For non-verified developers they go through the standard approval process, which can be tracked in the same way as new mod submissions.
4245

4346
## What are **verified** developers?
4447

0 commit comments

Comments
 (0)