Group Calendar 4 

Yes, I do it because I love programming and enjoy helping people enjoy themselves more in their leisure time. I disagree of course that my "free labor pool" point-of-view is self-serving. Blizzard's product is improved considerably by the free work of others and this free labor has filled in the numerous gaps they've left in their own product. All most of us ask for in return is appreciation and respect. What some ask for is direct compensation for the extensive amount of time it takes to do this work, which is benefiting a for-profit (and highly profitable) corporation. For them to say we don't deserve to get paid and that we have to hide our requests for donations on a website (which most people will never see thanks to auto-updaters) is abusing that free labor.

I'm sad to do it, but I feel I have to stand up for what I believe is unjust corporate abuse of a free labor pool. Judging by the posts I've seen in various discussion forums, Blizzard isn't the only one who devalues the work of addon authors either. It's disheartening and depressing.

If you did download the dummy file I uploaded and thereby lost your current working copy of Group Calendar, please email me using the Contact link on wobbleworks.com. I'm very happy to send you another copy.

What really sucks is that I'm so far along on Group Calendar 5 and it was really shaping up to be a great improvement over both Group Calendar 4 and the Blizzard calendar (while working within the Blizzard calendar's database, something I've long wished for!).

WARNING: WoWInterface doesn't allow all versions of an addon to be removed from the downloads list. To get around this I uploaded a 'dummy' copy of Group Calendar which contains no code. DO NOT DOWNLOAD THIS VERSION AS IT WILL OVERWRITE YOUR EXISTING (WORKING) VERSION. If you've already downloaded it and need a new copy, use the Contact link at wobbleworks.com and send me an email asking for a copy and I will happily send one.

Group Calendar 5.0 preview 3 is now available for download on my site at wobbleworks.com. While there are still features missing, I spent a lot of time debugging this release to ensure that the features which are implemented function well. I believe this release will be a good reference for what I have in mind for the overall design and workflow of GC5, so check it out and let me know what you think (please post comments on the wobbleworks forums and not here though, I don't want to confuse people seeking support for GC4 issues).

Please remember to disable GC4 while you're playing with GC5 because they can't be run simultaneously or they fight like cats and dogs over the "GroupCalendar" name rights

GC5 will not affect your GC4 data in any way whatsoever, so don't worry about messing up GC4 by choosing to toy around with GC5 for a bit.

During development I often disable the synch code in GC to speed up my turnaround. I usually remember to turn it back on before I release a build, but I forgot in 4.4. Without the synch period, users who use more than one computer, or those who have friends/spouses who log into their account and also run GC, will have trouble with their events not following them correctly from machine to machine.

This update is a minor change over 4.4 and should not risk any new problems, so I recommend using it to avoid roaming problems.

v4.4.1 Changes

- BUGFIX: Restored synch period timing (altered for debugging, forgot to put it back)

Sorry for the delay, but I had a couple of early reports of problems with 4.4 so I waited a bit. Those problems appear to be compatibility issues affecting events using manual confirmations and will not affect most users/guilds. If it does affect you, have the event organizer and the raid members all update to solve the problem.

v4.4 Changes

- FEATURE: Various cosmetic and behavior repairs
- FEATURE: Re-implemented Pending status for manually-confirmed events (missing since sometime before 3.0!)
- BUGFIX: Viewing your own attendance will no longer bump your signup date and time

You're not missing anything - it's GC that's missing something. Before Blizzard added their calendar in 3.0, GC would scan your raid info tab and record your raid resets for you, but it had to be coded with the name of each reset. That code hasn't been updated for Wrath (and barely for TBC really), so you'll have to use the Blizzard calendar (right-click on the minimap clock) to see your raid reset calendar. Group Calendar 5 does have full support for the built-in reset calendar.

I have posted the first development build of Group Calendar 5 on my site at wobbleworks.com. This is a very early release and several features are missing, but much is done as well. Visit the GC5 forum at http://wobbleworks.com/forums for a download link and notes regarding the release if you're interested in checking it out.

Note that you can not run GC5 and GC4 at the same time, but that GC5 will not alter your GC4 data in any way. If you try to login with both enabled you'll get all sorts of goofy errors from the collision, so be sure to only enable one of them at a time.

It is a known bug but I haven't gotten around to looking into it yet. I thought it was fixed a while back, but it sounds like I broke it again somehow.

v4.3.5 Changes

- FEATURE: Compatible with patch 3.0.8
- FEATURE: Updated Simplified Chinese translation (courtesy of Neptunic)
- BUGFIX: Fixed error message generated when guild configuration specifies a max event age