upd

minjaesong
2022-09-07 21:55:24 +09:00
parent bced072d07
commit a05eac6225

@@ -15,7 +15,7 @@ A metadata must have following keys:
- **releasedate** — the release date of the module of the version. The date format must be `YYYY-MM-DD`
- **jar** — the name of the Jar file the module's codes are contained. If there is none, leave it as a blank
- **jarhash** — the Sha256sum of the Jar file. If there is no Jar file, leave it as a blank
- **dependency** — list the other modules that this module requires.
- **dependency** — list the other modules that this module requires
### Dependency Format
@@ -30,10 +30,13 @@ The version string has following syntax:
- `a.b.*` — Any version between a.b.0 and a.b.65535
- `a.b+` — Any version between a.b.0 and a.255.65535
- `a.*` — Any version between a.0.0 and a.255.65535
- `*` — Any version. Period.
- `*` — Any version (for test only!)
For example, if your module requires `basegame` 0.3 or higher, the dependency string will be `basegame 0.3+`.
- Why can't I specify the `+` sign on the major version number?
- The change on the major version number denotes incompatible API changes and therefore you're expected to investigate the changes, test if your module still works, and then manually update your module to ensure the end user that your module is still operational with the new version of the dependency.
### icon.png
A module can have an icon about themselves. The image must be sized 48x48 and in 32-bit colour PNG format.