From 2a3d340b20a32f92c3d57184aea3e5a40c39b894 Mon Sep 17 00:00:00 2001 From: Timo Ley Date: Fri, 10 Jun 2022 23:57:15 +0200 Subject: [PATCH] Improve included flag specification --- docs/concepts/flags.md | 6 +++++- 1 file changed, 5 insertions(+), 1 deletion(-) diff --git a/docs/concepts/flags.md b/docs/concepts/flags.md index 20e63e2..b926fca 100644 --- a/docs/concepts/flags.md +++ b/docs/concepts/flags.md @@ -31,7 +31,11 @@ or [files](../schema/file.md). These are relational flags, which can only be used for [relations](../schema/relation.md). - `included` This flag specifies, that the related addon is included in this one. This also means, that if some - addon requires the related addon, it can also be installed with this addon instead. + addon requires the related addon, it can also be installed with this addon instead. Relations with this flag must + have an exact version specified, a version range, which includes multiple versions is not allowed. If this flag + is used together with `required` or `optional`, the files of the related addon will be installed like if the + relation wouldn't have this flag, relations of the related addon will however be ignored since AddonScript assumes, + that they are already covered by this addon. - `incompatible` This flag specifies, that the related addon is incompatible to this one. This means, that they can't be installed together in the same instance. - `launch` This flag specifies, that the related addon should take care of the Minecraft launch process. It can only