After completing the above post, I realized that I hadn't addressed an obvious question from Dwayne's last post. Why haven't we yet implemented some of the missing mechanics from the APG or UM?
Everything here gets prioritized, and the single biggest factor in prioritizing anything is how many users will be impacted - negatively by omitting something or positively by adding something. If a particular mechanic of a book is asked about by only a few users over a lengthy span time, it's clearly not nearly as important as a mechanic of a different book that is asked for by numerous users.
In addition, there's the question of how long something will take to add. If one mechanic will take us two weeks to implement and another three days, and they are both asked for by about the same number of users, we'll do the one that takes three days first. If a mechanic from a old book takes weeks to implement, it also competes against all the new books that are being released for time in the schedule.
It's a juggling act on our end, and we're constantly re-evaluating the schedule and re-prioritizing all these competing tasks. We'll never be able to please everyone perfectly, so the biggest driving force behind our prioritization efforts is user demand. The more people that want something, the higher it gets prioritized.
I guess the bottom line with some of the long-unimplemented mechanics from the APG and UM is that there just haven't been many people asking for them. The net result is that other mechanics (and the onslaught of new books) keep getting prioritized above them. If some of these missing mechanics are important to a lot of you, let us know. That's how to boost their priority in our development schedule.
As I stated in my previous post, this is definitely not an ideal solution. But we don't have the staff to get everything done in the time available. This solution ensures that the most users get the most benefit, which is the best we're going to achieve.
Hope this (further) explanation helps...