If this is in the wrong place, please move and inform me where to.
Regarding Rift addons, I have discovered that the packager's use of
## X-Curse-*
is not compatible with the toc. RiftAddon.toc is a simple Lua file, and comments are made with the usual "--" entry.
This currently makes the repository system useless, as you have to create zips yourself and await approval from the moderators. This also impacts things like keyword substitutions, and you cannot use pkgmeta or docmeta files.
My question about the Curse Client is simply is there an ETA on getting support for Rift? If not, no worries, but then it becomes when is curse.com getting Rift support? We are letting the ZAM network get a huge leg up here.
Speaking of ZAM, here is the Wiki link to RiftAddon.toc. You may notice that all Rift addons use RiftAddon.toc and not MyAddonName.toc.
-
View User Profile
-
View Posts
-
Send Message
Forum ModeratorRegarding Rift addons, I have discovered that the packager's use of
is not compatible with the toc. RiftAddon.toc is a simple Lua file, and comments are made with the usual "--" entry.
This currently makes the repository system useless, as you have to create zips yourself and await approval from the moderators. This also impacts things like keyword substitutions, and you cannot use pkgmeta or docmeta files.
My question about the Curse Client is simply is there an ETA on getting support for Rift? If not, no worries, but then it becomes when is curse.com getting Rift support? We are letting the ZAM network get a huge leg up here.
Speaking of ZAM, here is the Wiki link to RiftAddon.toc. You may notice that all Rift addons use RiftAddon.toc and not MyAddonName.toc.
-
View User Profile
-
View Posts
-
Send Message
Curse PremiumHeh.
o.O