Posted by wronoj on 6/24/2010 1:10:00 PM (view original):
not good enough. As far as I can tell, the PBP contains every event which would cause a whistle/stoppage in play. It contains all turnovers, fouls, shots (made or missed). Why would you assume the ball was kicked and the shot clock reset? What makes that more likely than there being an error in the SIM? And, if you are correct, why are you willing to forgive a missing key element of a play in your PBP? What other missing elements of PBPs actually affect game results in a visible manner? Are you willing to forgive those? 

either:

you are correct and the shot clock was somehow reset, but we just don't see it

or: 

there's an error in the engine which allowed this team 39 seconds to take a shot.

There is no way to tell, so if I lost that game I would surmise that it's an error until a developer tells me otherwise. No reason to just assume that they got it right, but not all the way right...

I have always been willing to overlook the details of whether my PG had a 10-second violation vs a double dribble vs a pass out of bounds-- all turnovers, i don't care how the PBP describes it. But if there's an element that affects timing, I want to see it.
Thanks wronoj for at least understanding that this was wrong. The current PBP has been enhanced to include whether a player threw a pass out of bounds because it was covered with sweat, so I can't just assume that they didn't bother to mention that there was a clock reset that allowed the extra 4 seconds. I did send a ticket and will share the response when I get it.

As for the player time issue, the Freshman PG was listed as 3rd string PG and nowhere else. The Jr PG was second string PG and 3rd string SG. That may explain that the 3rd stringer could come in when 2nd stringer was at SG, but how can the 3rd stringer have more minutes? As for the excuse that I gave more time when the game is out of reach, if that was the case and I lost, that part of the logic is broken. That should only kick in with a 20 point lead as I understand it. Again, I will let you know what CS says.
6/24/2010 1:49 PM
Well, Customer Service was just as helpful as they were with the old engine. Here is their response, "Please place your comments in the new 'Suggestions' box that is located the game's new site forum. This is monitored by the game's creator who will look further into this if he feels that this could be an issue."
6/24/2010 1:56 PM
And what is wrong with that?  They are just sayign to put the technical glitches in one place.

6/24/2010 2:08 PM
This happened in the old engine frequently, especially with an opponent playing slow down. I was told that if the ball went through the basket with 39 seconds left, it could take up to 5 seconds to inbound, thus the max is 35+5=40 seconds. I didn't like the explanation, because it made the slowdown even more dominant, but that's what I was told.
6/24/2010 2:12 PM
Posted by acn24 on 6/24/2010 11:38:00 AM (view original):
Also - please remember that the play-by-play is generated after the result/box score.  You had already lost by the time that was created. 
I stand corrected on this - it seems that this is something that is enhanced with the new engine.  They do generate play by plays for sim v. sim games now, and the play by play is generated after each individual play is simulated. 
6/24/2010 2:14 PM
The volatility inside games, as well as the fouling issue, make me the most nervous.

http://www.whatifsports.com/hd/GameResults/BoxScore.aspx?gid=5871082

In the linked game above, I fell behind by 29 with 6 1/2 mins left in the first half. Then, trailing by 23 with 17 1/2 mins left, I go on a 39-9 run over the next 12 mins, only to be outscored 23-9 in the last 5 minutes. I also committed 41 fouls (only the last 2 were intentional) - on the same night, I saw a box score with a zone team that committed only 3 total fous.

I intentionally did not redshirt any of my 4 freshmen this year, because I believe that to run FCP and FB you'll need a strong 10-12 man rotation between fatigue and fouls.

I don't necessarily think this is a flaw - just something that will take time for adjustment in the mindset of the fast pace coaches.
6/24/2010 2:25 PM
This post has a rating of , which is below the default threshold.
Posted by treyomo on 6/24/2010 2:12:00 PM (view original):
This happened in the old engine frequently, especially with an opponent playing slow down. I was told that if the ball went through the basket with 39 seconds left, it could take up to 5 seconds to inbound, thus the max is 35+5=40 seconds. I didn't like the explanation, because it made the slowdown even more dominant, but that's what I was told.
The clock doesn't start until the ball is inbounded, but maybe that is the way they have the game programmed. If that is what they told you, then the programmers and CS don't know the rules of college basketball.
6/24/2010 2:36 PM
This post has a rating of , which is below the default threshold.
as before, jetsons, i agree with you here.

but i would still suggest you link this box score and PBP in seble's thread at the top of the page with your questions. No way he has time to get through all of these threads and weed out real issues from the junk.

on the PT issue, i think you should submit it, but i'd also play around with your depth chart settings in the meantime to get it straight on your own. I don't think it was a "glitch", but rather an anomalous but repeatable result.
6/24/2010 8:23 PM
I hope you are right about the depth chart, wronoj, but I have NEVER had a 3rd stringer get more minutes than a second stringer with no fouls and good stamina. It is not a big deal, just a frustrating consequence of inadvertent changes to the engine that require us to "play around with our depth charts" . I would love for someone to point out positive changes in the new engine. Are there any discernible positive changes? 
6/24/2010 9:44 PM
Jetsons, definitely submit that. I had the same complaint about the depth chart and had a conversation with seble, it's pretty clear to me that's one area he doesn't have the best grasp on just yet.
6/24/2010 9:59 PM
Posted by jetsons on 6/24/2010 10:33:00 AM (view original):
Game 1 in Wooden, and already the new engine is horrible. my 3rd string, Freshman player, played more minutes than the second stringer who had 81 stamina and no fouls. then I lose at the buzzer after my opponent inbounded with 39 seconds to go. It isn't fun paying to be a beta test site.
I had an even worse example, where my 3rd string pf (in fairness, the #2 guy is #2 at both big spots, but he's set to getting tired), played more mins than my starting pf (who had higher sta), who was not in foul trouble and it was a close game the whole time. I was not happy.
6/24/2010 10:01 PM
  I found a Solution to Playing Time.  All my guys suck, so I don't care who plays how many minutes.  Therefore, I never have a Playing Time Concern.  If my Manager (fancy name for 'Guy who does Laundry for Team') sneaks on the Court, I could get Improved Play... so I'm all for crazy guys getting on the court.
6/24/2010 10:39 PM
Posted by acn24 on 6/24/2010 11:38:00 AM (view original):
Also - please remember that the play-by-play is generated after the result/box score.  You had already lost by the time that was created. 
pretty sure this is wrong.
6/25/2010 1:02 AM
◂ Prev 123 Next ▸

Search Criteria

Terms of Use Customer Support Privacy Statement

© 1999-2026 WhatIfSports.com, Inc. All rights reserved. WhatIfSports is a trademark of WhatIfSports.com, Inc. SimLeague, SimMatchup and iSimNow are trademarks or registered trademarks of Electronic Arts, Inc. Used under license. The names of actual companies and products mentioned herein may be the trademarks of their respective owners.