User Pass
Home Sign Up Contact Log In
Forum > Goal Line Blitz > If I hear someone say "They're getting rid of the DPC!" one more time...
Page:
 
jdbolick
offline
Link
 
Originally posted by bug03
Catch said in a PM (i think i copied it in our PF) that blocking code would be figured out after they limit the dpc

Originally posted by jdbolick

I know the excuse given, but it makes no rational sense. If the code worked against base alignments but not custom ones, then that would be a plausible reaction. Since it doesn't work against either, how can anyone pretend that custom alignments are the problem?


 
Deathblade
offline
Link
 
Originally posted by jdbolick
Originally posted by bug03

Catch said in a PM (i think i copied it in our PF) that blocking code would be figured out after they limit the dpc

Originally posted by jdbolick


I know the excuse given, but it makes no rational sense. If the code worked against base alignments but not custom ones, then that would be a plausible reaction. Since it doesn't work against either, how can anyone pretend that custom alignments are the problem?




I always enjoy how people cannot fathom infinite possibilities vs finite possibilities.
 
jdbolick
offline
Link
 
Originally posted by Deathblade
I always enjoy how people cannot fathom infinite possibilities vs finite possibilities.

If your engine knocks when the air conditioner is on, but also knocks when it isn't, then pulling out the air conditioner doesn't actually change anything. Again, if the blocking code worked properly against base alignments but not custom ones, then the admin excuses would have some validity. The fact that they don't work properly against base alignments either proves that custom alignments are not the problem.

Edit:
It's also worth noting that we're going to have an entire season of shitty results where no one is happy, because DCs will have their hands tied while OCs will be bitching about the fact that the blocking still doesn't work properly. "Oh, we're going to make blocking changes, but not until we've limited the DPC" makes no god damned sense. Be working on it now, and have the solution ready by the end of this season.
Edited by jdbolick on Dec 9, 2010 13:19:59
 
Deathblade
offline
Link
 
Originally posted by jdbolick
If your engine knocks when the air conditioner is on, but also knocks when it isn't, then pulling out the air conditioner doesn't actually change anything. Again, if the blocking code worked properly against base alignments but not custom ones, then the admin excuses would have some validity. The fact that they don't work properly against base alignments either proves that custom alignments are not the problem.


Originally posted by Deathblade
I always enjoy how people cannot fathom infinite possibilities vs finite possibilities.


 
Deathblade
offline
Link
 
I mean, I'm not sure if you are purposely being ignorant, or what.

If I had to memorize every political leader ever I would likely miss a handful of them. If I only had to remember 3 (2 of them being ones I would have missed earlier), then I'm much more likely to get them right.
 
Warhawk
Moderator
offline
Link
 
Originally posted by jdbolick
Originally posted by Warhawk

I think the idea was that they'd fix the blocking code once they limited the DPC.

I know the excuse given, but it makes no rational sense. If the code worked against base alignments but not custom ones, then that would be a plausible reaction. Since it doesn't work against either, how can anyone pretend that custom alignments are the problem?


It's not that custom alignments are the problem with the blocking code as it is now. They're not. Custom alignments are the problem with overhauling the blocking code.

Basically, the blocking code is borked, and they could fix it right now with regards to the default alignments, but they only way they're going to fix it entirely is by limiting custom alignments. Thus, the problem isn't that custom alignments are screwing up the current blocking code - the problem is that custom alignments make it impossible to produce a better blocking code.
Edited by Warhawk on Dec 9, 2010 13:28:23
 
Deathblade
offline
Link
 
Or maybe I should have compared it to catching a million raindrops in a bucket vs catching 5.
 
Warhawk
Moderator
offline
Link
 
Originally posted by Deathblade
Or maybe I should have compared it to catching a million raindrops in a bucket vs catching 5.


/me imagines Deathblade running around in the rain with a bucket.
 
Deathblade
offline
Link
 
Originally posted by Warhawk
/me imagines Deathblade running around in the rain with a bucket.


I'm trying to think of a good analogy to explain why it is easier to stop finite possibilities than relatively infinite.
Edited by Deathblade on Dec 9, 2010 13:29:58
 
Deathblade
offline
Link
 
Also, I'm fully aware that there's a jdbullock post incoming that has somewhere between 2000 and 3000 words, 90% of which call me an idiot with way more words than are really needed.
 
jdbolick
offline
Link
 
Originally posted by Warhawk
It's not that custom alignments are the problem with the blocking code as it is now. They're not. Custom alignments are the problem with overhauling the blocking code.

Except that they're clearly not, because this shit has always happened. The blocking code sucked before the DPC even existed, and Hcreek has already proven that it will continue to suck after these latest changes are made. Fixing the code has nothing to do with the DPC. Again, if you could "fix" the code such that it worked against base alignments, then we could see whether or not it still had trouble with custom alignments. If it did, then you would make these changes. But it makes no sense to make the changes first when there is absolutely no evidence that custom alignments are either responsible for poor blocking or that there will somehow be a correct blocking code without them. The code sucks because the code sucks. It's not that complicated.
 
jdbolick
offline
Link
 
Originally posted by Deathblade
Also, I'm fully aware that there's a jdbullock post incoming that has somewhere between 2000 and 3000 words, 90% of which call me an idiot with way more words than are really needed.

no u
 
Deathblade
offline
Link
 
Really amazed that someone who is "so intelligent that I get frustrated because I see problems way ahead of other people" can't understand that it is easier to account for a handful of possibilities rather than so many possibilities you would have to use google to look up the name of the number.
 
Deathblade
offline
Link
 
Are you under the impression that the DPC is going to be limited and they are never ever going to touch blocking again, keeping this season's code?
 
Warhawk
Moderator
offline
Link
 
Originally posted by jdbolick
Originally posted by Warhawk

It's not that custom alignments are the problem with the blocking code as it is now. They're not. Custom alignments are the problem with overhauling the blocking code.

Except that they're clearly not, because this shit has always happened. The blocking code sucked before the DPC even existed, and Hcreek has already proven that it will continue to suck after these latest changes are made. Fixing the code has nothing to do with the DPC. Again, if you could "fix" the code such that it worked against base alignments, then we could see whether or not it still had trouble with custom alignments. If it did, then you would make these changes. But it makes no sense to make the changes first when there is absolutely no evidence that custom alignments are either responsible for poor blocking or that there will somehow be a correct blocking code without them. The code sucks because the code sucks. It's not that complicated.


The code does suck, but if they can't produce a blocking code that would work against custom alignments, then it makes no sense to implement a completely different blocking code just for the default alignment. I'm sure they've done a fair bit of testing on this, it would be pointless for them to implement a new blocking code designed to work against default alignments if they already know it won't work against custom alignments.

And really you have no basis to say that there won't be a correct blocking code without custom alignments. The whole point of getting rid of custom alignments is to make the creation of a correct blocking code feasible. It's not to fix the current blocking code problems.

They've been trying to fix it for a while now. Clearly they've come to the conclusion that the only way to produce a blocking code that works across the board is to limit the LB and D-line alignments.
Edited by Warhawk on Dec 9, 2010 13:47:03
 
Page:
 


You are not logged in. Please log in if you want to post a reply.