[Note: I have figured out the problem below. Here it is - you can ignore the rest...]

You all have added two lines to the scoring input page - an extra per tackle feature and an extra fumble feature. In the past, I have always checked to make sure you hadn't changed things, then just copied in my league's scoring rules from "last year." Thus, this year when I copied in my old rules - having finally assumed that you'd never make any changes! - I went over the top of TD scoring with fumble recovery scoring, and so on.

Now I've got to figure out how to reverse the damage since I've color coded and filled in my cheatsheet with all kinds of information.



Bruce, I always sync up my VBD app output with my DD output, to make sure "everything's working properly."

As I was looking down the VBDs coming out of each app, I noticed small differences. If first checked to make sure the VBD baselines in each app were the same, which they are (they are custom baselines).

In probing for the source, I found an anomaly in the defensive scoring which may be the primary cause. However, I can't determine what is causing the scoring anomaly. I have carefully looked at my input for our league scoring "per item." And I looked at the projections (I haven't touched them) in each app - they are the same per "performance unit" (e.g., yards allowed). Yet the scoring output is different. For example, in the VBD app, New England scores 280 fantasy points, but in the VBD app, they score only 204.

The only possibilites are in the weekly scoring factors - points allowed per week and yards allowed per week (which are in hidden columns in the VBD app and invisible - and "fumbles forced" (which doesn't exist as an option in the VBD app, but does in the DD though I have set that to zero).

Last year I didn't have this syncing up problem. In looking at my final VBD app spreadsheet from last year, I see the following scoring for these ranked defenses:
1 253
2 225
12 168
32 71

This year, I am getting:
1 291
2 280
12 225
32 113

Thus, if I had to guess, I'd say there is something wrong with the VBD app's scoring for defenses (relative to last year), rather than the DD. Though whatever the case, something seems wrong between the two apps, even if projections for defensive scoring have gone up across the board (which doesn't seem likely.)

I have used the VBD app for five years, and this is the second for DD, so I am reasonably familiar with moving around in them, though I am no programmer. I can usually solve these things on my own, but I am at a loss with this.

Thanks!

So is everything ok now?

Hey, Bruce. Actually, I thought it was, but now I realize no.

I outlined above in my "oh, crap" note why my VBD sheet was screwing up defensive scoring.

However, in crawling through the code to figure out what was going on, I realized that David had changed his "distribution" per game of points allowed and yards allowed. This radically lowered the scoring of Ds, particularly the top ones.

I am reasonably comfortable that, for my league at least, his change is a good one (except for the top D, which he's underscoring, though I wish I knew for sure who that would be!).

Anyway, my output for Baltimore's D now in the VBD app is 215, vs. 241 in Draft Dominator. I don't see any difference in the performance metrics (e.g., fumbles, TDs, total yards allowed, total points allowed, etc.) I'm wondering if Draft Dominator has buried within its programming the old distribution scheme of points allowed and yards allowed.

(For reference, these distributions are in the hidden columns on the defensive projections sheet, columns K through AF.)

Only somebody with a league that places such a premium on defensive scoring would ever dig this deep on such a boring position!

Where are you looking at the DD points? Projection Tab or Player Pool? The Player Pool could be inflated if your GameByGame is set to use Weekly Weights...

Well, now, that's funny. I'm at my home computer now, and I've just downloaded DD, and then pulled in my league file that I emailed myself from work.

I was looking - previously - I thought - at the projection tab but I was DEFINITELY looking at the player pool, and I thought both showed 241 points for Baltimore.

However, now, I am looking at both, and they both show 215.

It is possible - is it? - that the fact that I tried to salvage last year's rules and keepers when I started this process, caused me also to "salvage" (though I'd want to start from scratch) any weekly weights I might have put in last year?

All I can tell you - from here at home - is that things look fine. I'll have to get back to work to see whether I have any weekly weight debris left over from last year, somehow.

Sorry for the confusion, if this was all that was creating the issue.

Thanks, Bruce.

p.s though this is probably telling me that Baltimore is more valuable than I imagined... or, rather, than whoever is ultimately the number one D is more valuable than I imagined - if I only had a crystal ball...

Bruce, it is not set to use weekly weights.

However, I re-downloaded version f on top of my existing DD, pulled in my league file again, and now it looks fine.

Don't know what happened, but it's working which is all that really matters.