Version 1.2.0 is out with some feature changes, but most importantly some important background work to make VCC easier to evolve. The end of 2009 and beginning of 2010 brought important challenges to the core developers of the project. With much of the demand behind us we are now focusing on new things for VCC.

The main goal for the 1.3.0 release is to work on the core logic of the tracker to allow it to do some of the long requested functions. These include: roll initiative in the middle of the battle, remind DM of sustains and save, ongoing damage, and other. The core logic is quite old and need some major work.

We still need help on all kinds of small tasks:

• Testing is a must! Most development and testing are done on Windows, having people to test on Mac and Linux would be great;
• We could use some web-designer help to look at the stat blocks and general artwork;
• Scala programmers can help tackle several issues. Bjarte Stien Karlsen has helped us a lot with the Character builder import logic;
• Java programmers are welcome too, we have a small part that is in Java, but there are several ideas that need skilled Java codes;
• Aside from this, having people willing to help think on how VCC should look and behave could be helpful.
  E.g. How should a user request the re-roll for initiative? A popup menu on the sequence table? A menu option? Should he open the Start Combat dialog?

If you feel you can give us some of your time, join the VCC Developer group.

A lot of effort of version 1.2.0 was placed in making VCC build and testing easier. This will bear fruits on the next releases. If you looked at the code base in the past we urge you to check the new Maven based project (check build instruction here).