sanjosolutions / addons Goto Github PK

With the current approach, an add-on depending on that the library makes itself accessible via global seems brittle because it only does it when "Library" is absent. "Library" might be included by another add-on.

With the alternative approach to always also load the library in the global environment, the benefit of avoiding that a name conflict occurs seems gone. Also only one version of the add-on can be accessable via one global directly. Therefore an add-on which accesses a library via global might access another version of the library via it if another version of the library loads last.

See:

• https://support.curseforge.com/en/support/solutions/articles/9000197281-automatic-packaging
• https://support.curseforge.com/en/support/solutions/articles/9000197952-preparing-the-packagemeta-file

This might improve revenue share via declaring dependencies with https://support.curseforge.com/en/support/solutions/articles/9000197952-preparing-the-packagemeta-file#Specifying-dependencies.

Version tags like 1.0.0 (instead of v1.0.0).

• Create additional version tags with the absence of 'v' for existing versions.

See https://github.com/SanjoSolutions/LuaBoolean/tree/c80efb61858b1485f2a5ef037b1fbaa625c3ac98 for how it can be done.