Made an announcement thread for this update. Try to keep it on page 1.
https://bitcointalk.org/index.php?topic=386035.new#newChill, artos, it's not about you, it's about the coin. Had you communicated this information, you would not have had the sort of reaction you see here. You say the fix has been ready for days, but you didn't inform us.
We need timely information, especially when things aren't going as expected. We all want this coin to succeed. We all have a vested interest in it succeeding, but when we don't here anything for a couple of days, it leads to folks asking serious questions.
AS I said before. By choosing to create this coin and push it's development, you have taken on the additional burden of communicating with you base. Perhaps cobrabyte is correct, and you need some assistance in running the coin (preferably someone with plenty of knowledge and expertise. It appears there are some in this community with the knowledge to help.
Please give it some thought.
And thanks for the update.
There's been a lot of unnecessary personal attacks, even though I am just as concerned with the success of this coin as any of you are. This thread feels like a witch hunt in recent days. I've posted both in this thread and on the official forums that a fix was forthcoming.
For the curious, the issue was related to integer rounding. Shifting around the parenthesis is all that needs to be done.
nActualTimespanMax = nTargetTimespan * (112/100) <- This rounds to 1
nActualTimespanMin = nTargetTimespan * (100/111) <- This rounds to 0
Fixed:
nActualTimespanMax = (nTargetTimespan * 112) / 100
nActualTimespanMin = (nTargetTimespan * 100) / 111