I get the stock answers I think?  And I dont send in very many tickets

Posted by stinenavy on 11/4/2010 10:48:00 AM (view original):

11/4/2010 10:10 AM	stinenavy
The problem is that the other team is perfect from the line! In fact on my Crum team the opponent just went 8-8 from the line when being intentionally fouled. So in my games the other team has hit 32 consecutive free throws! This isn't just some random variance, this is a fatal flaw in the game engine that needs to be addressed immediately.
11/4/2010 10:37 AM	Customer Support
On closer inspection, you're right, there is a bug that pops up in intentional foul situations. We'll get that corrected before the next games run. Thanks for pointing it out.

Nice job stinenavy. 

I sent in a development chat question about the early forced miss on early free throws.  Thank you, stinenavy, for getting some action on the end of game free throw bonanza.

Nice work by both Drsnell and Stinenavy!

Posted by drsnell on 11/4/2010 1:13:00 PM (view original):
I sent in a development chat question about the early forced miss on early free throws.  Thank you, stinenavy, for getting some action on the end of game free throw bonanza.

One of the adjustments on 8/28 was “reduced single-game variance on free throw shooting.” But now it appears it is impossible for a player to start a game 4 for 4 from the line. Each player is forced to miss at least once in their first four attempts. Why was this done? I would much rather have a 72% free throw shooter simply have a 72% chance to make a free throw. (drsnell - Hall of Famer - 1:32 PM)

Actually, starting this afternoon, it will begin to work that way. There was a bug found and fixed related to FT shooting in intentional foul situations. As part of that fix, the variance reduction was removed from FT shooting completely. It's one area I debated about for the 8/28 release anyway.

_____________________________________________________
From the Dev Chat.

I hadn't noticed the problem but, going back and checking,  players hit 87 of 91 (95.6%) in my just completed Wooden season. Maybe that's why I was 11-18. LOL

Wow, you'd almost think seble knew what he was doing and cared about the game, or something.

Holy Moly!  I just looked, I had my best D3 team ever in Wooden, ending up with a 553 rating and starting out as the #8 ranked team in the country, but ended up with a 13-15 record.  I did a comparison of some of the teams in my league and I shot 75 more free throws than the second most team (which shot a lot).  I then went back an compared pbp of some close games.  For instance, in a game agains Hamline, he shot 4/8 initially, but when I started intentionally fouling, he finished 8 in a row.  In the next game at St. Scholastica, he started out 14/21 and then made his last 12 in a row, St Mary's, he made his last 11 in a row in an overtime loss.  There was a definite coralation to intentional fouling dramatically raising the free throw percentage, usually to a 100%.   At some point, I sensed this and removed the intentional fouling, but was not smart enough to see the pattern.  Again, I was also hurt on the flip side as I've never seen one of my players hit 4 in a row, which definitely hurt in the 1 and 1 situation as mentioned. 

Anyway, drsnell, thanks for bringing this up.  I just couldn't figure out why my team was so horrible, and this seems like a valid reason, I lost a ton of games on free throws..

I hate the new fix. LOL My very young, outmanned team was leading the #3 team 50-48. With 20 seconds left, they intentionally fouled me.  We missed the FT. At the buzzer, they dunked the ball and was fouled. They made the FT and won 51-50.

Posted by brip87 on 11/4/2010 10:56:00 AM (view original):
Why do they treat everyythign like its ok until you bug the crap out of them it sucks

The guy went in a checked the code the and found the bug.  What he said the first time is also correct ... there should have been no reason for it to be different.

But, instead of complaining, how about thanking them for finding the problem and taking care of it so quickly.

For people who write and debug code, you should be able to understand that it is very easy to look at a section of code and have it look fine, but have some other place pass in a variable under certain conditions that causes issues.

In any event, the fact of the matter is, seble did NOT blow off the issue, he did very quickly find and fix it.

Posted by jpeterson84 on 11/4/2010 8:10:00 PM (view original):
Holy Moly!  I just looked, I had my best D3 team ever in Wooden, ending up with a 553 rating and starting out as the #8 ranked team in the country, but ended up with a 13-15 record.  I did a comparison of some of the teams in my league and I shot 75 more free throws than the second most team (which shot a lot).  I then went back an compared pbp of some close games.  For instance, in a game agains Hamline, he shot 4/8 initially, but when I started intentionally fouling, he finished 8 in a row.  In the next game at St. Scholastica, he started out 14/21 and then made his last 12 in a row, St Mary's, he made his last 11 in a row in an overtime loss.  There was a definite coralation to intentional fouling dramatically raising the free throw percentage, usually to a 100%.   At some point, I sensed this and removed the intentional fouling, but was not smart enough to see the pattern.  Again, I was also hurt on the flip side as I've never seen one of my players hit 4 in a row, which definitely hurt in the 1 and 1 situation as mentioned. 

Anyway, drsnell, thanks for bringing this up.  I just couldn't figure out why my team was so horrible, and this seems like a valid reason, I lost a ton of games on free throws..

If your team was really that good you wouldnt have been behind in the closing minutes in so many games.

Posted by hughesjr on 11/5/2010 7:48:00 AM (view original):

Posted by brip87 on 11/4/2010 10:56:00 AM (view original):
Why do they treat everyythign like its ok until you bug the crap out of them it sucks

The guy went in a checked the code the and found the bug.  What he said the first time is also correct ... there should have been no reason for it to be different.

But, instead of complaining, how about thanking them for finding the problem and taking care of it so quickly.

For people who write and debug code, you should be able to understand that it is very easy to look at a section of code and have it look fine, but have some other place pass in a variable under certain conditions that causes issues.

In any event, the fact of the matter is, seble did NOT blow off the issue, he did very quickly find and fix it.

If the person who wrote the ticket would of just said ok no bug.  Then we wouldnt even be having this converation.  They (cs) almost always just blow it off and say its all ok or there is nothing that can be done about it and thats the reality.  Did they fix it?  Probally but only after the coach who sent the ticket kept after them.  I never said seble "blew it".  But in most cases including this they just ignore the tickets and give crappy answers.

seble is light-years easier to work with than his predecessor, who  considered it a sign of weakness to say, "I'm sorry", or "I made  a mistake."

Example:
 1) I pointed out that my  team was on the 'lock' list but didn't make the NT. His response was that analysts often predict the at-large teams incorrectly and  that he had no control over what the 'Collegiate Insider' reporter writes!! A few days later, he discovered the glitch and corrected it, after I'd endured some rather nasty postings from other coaches on the Forum.  I asked him to post an explanation in the Forum, exonerating me. I even  sent him a humerous, tongue-in-cheek apology to the 'great Transylvania nation' and asked him to copy it into the Forum. I never heard a word.....even in fun, he was incapable to saying "I'm sorry".

  2) I noticed that low prestige teams were pulling down great recruits very easily.  I questioned it 5 different times over a period of weeks, in specific detail, only to be told it was functioning properly. Finally, another coach explained the glitch to me and I started using it.  After another coach questioned it (once),  WIS found the glitch and corrected it.....A) during recruiting; B) without telling anyone EXCEPT that second coach!  By then, I had spent most of my budget on a formula that no longer worked.

  So, every time I read about a customer service issue with seble, I think , "oh, if you only knew......"

Oh I agree Al, Seble is much better than TK ever was, but the CS runaround still exists, just not as bad as before.