Authors CurseForge

Good luck getting a reply, CurseForge/Wowace are becoming a joke, I'd be lying if I said I have been thinking of taking my addons elsewhere such as WoWInterface.

Most of the "staff" here are full of themselves and don't act very professional.

My project (ProcAlert) uses a Git repo at GitHub, does the packager know to check there for new commits? If so, how often?

There might be a way of finding out, if you want to create characters and keep checking their GUID, and if you find one that has one lower then another, there's your answer I guess..

I would assume every time a character is created their GUID is one digit higher than the last character created. At least thats how I would have made it.

This is similar to the code I use in my addon:

local LB = LibStub("LibBars-1.0") -- LibBars
local LSM = LibStub("LibSharedMedia-3.0") -- LibSharedMedia
local barFont = "Arial Narrow" -- Font text uses
local barFontSize = 12 -- Font Size
local barHeight = 20 -- Height of the bars
local barWidth = 150 -- Width of the bars
local barTexture = "Blizzard" -- Texture the bars use
local bars = nil

-- Create the bars
bars = LB:NewBarGroup("Bars", nil, barWidth, barHeight, "testBars")
bars:SetFont(LSM:Fetch('font', barFont), barFontSize)
bars:SetTexture(LSM:Fetch('statusbar', barTexture))
bars:SetUserPlaced(true)

-- Add a countdown bar from 10 to 0
bars:NewTimerBar("Test", "test", 10, 10, "Interface\\Icons\\Spell_Holy_WordFortitude")

This isn't the exact code I use, but it should help you understand how to use LibBars better than browsing the source of other addons.

Thanks for the help, I feel stupid. I never thought about the [[...]] quoting, Thanks again.

I'm trying to store sound locations in an AceDB then read them when my addon loads and register then with LibSharedMedia.

I've been able to do everything except the sound doesn't play.

This is how the location looks when its in the SavedVariables:

["customSounds"] = {
	["test"] = {
		["name"] = "test",
		["location"] = "[[Sound\\Spells\\SeepingGaseous_Fel_Nova.wav]]",
	},
},

This is the code I use to read and register the sound with LSM:

for name,info in pairs(self.opt.customSounds) do
	LSM:Register("sound", info.name, string.gsub(info.location,'\\\\','\\'))
end

The sound shows up in the LSM sound dropdowns, but when it comes time to play the sound, it doesn't work.

The reason I'm doing this is because I have an addon people wish to add custom sounds to without editing the addon files.

Is anyone able to help with this?

Thanks.

Thanks for the replies, I was able to get the cooldowns of the spells by using code similar to what Finghin posted, thanks for the help.

I've been searching as best I can, now either I suck at it or I just cant find anything.

I'm trying to found out how to detect the cooldown for certain spells, Does anyone know of a way?

Thanks.

Quote from OrionShock

looks like your project is messed... wait for an admin to fix it.

It's not just my project, a lot of other people have having the same issue.

So far I've notice two of my project won't push the files to Curse,
- Proculas
- ProculasFu

I'm not sure about the rest of my projects.

Quote from OrionShock

and the tag name has the word "release" at the end? :D

No, but the files in the file list are set as "Release" by the package unless it has "beta" or "alpha".

And other addons that are having their files pushed to Curse don't have "Release" in the filename.

Quote from OrionShock

are you doing tags to releases or just changing the zip file tyep from alpha to release? there is a slight of hand difference there.

I tag them with the "svn cp" command.

Quote from Torhal

Tagged another release for Revelation 10 minutes ago - it's on Curse.

Tagged another release for my addon and it hasn't shown up on Curse.

Quote from OrionShock

Are you tagging as release?

http://www.curseforge.com/projects/curseforge/tickets/1008-file-not-syncing-from-wow-ace-curse-forge-to-curse/

My Release files are not being pushed to Curse, its the same for a lot of other addons.

I reported this on the CurseForge Tickets page over a day ago and I haven't heard anything about a fix.