Yes, that is correct.
There's one more check above, so together it is:
modIsEnabled && ( modInfo.isMaster() || modInfo.getMaster().empty() || modInfo.getMaster() == curMaster )
That means, maxSize is updated from:
- current (enabled) master
- all (enabled) mods without a master ("*" in metadata.yml)
- all (enabled) mods of the current master
PS: I copypasted these two conditions from mapResources() method
If mod is not master but still will bump up `maxSize`.
Yes, the idea is that the "root master" must have the same size as the biggest mod (regardless if the biggest mod is a master or not).
Example:
- root master = xcom1 = size 1
- piratez master by dioxine = piratez = size 3
- someone's mod for piratez = somecode = size 7
In this example, it is necessary to set the size of the root master (xcom1) to 7.