User Pass
Home Sign Up Contact Log In
Forum > Suggestions > Fix the rounding issue differences between the text output and the AI inputs
spindoctor02
offline
Link
 
Problem: In the AI inputs, we only have control over 5 yard increments in which to set our plays. In the text output from the plays, all results of plays are listed to their 0.5 yard increments. As it has been shown over time, the sim deals in smaller increments than 0.5 yards (you can check any game to see this). None of these are consistent with one another.

Suggestion: Obviously there is some rounding in the reporting of the plays. I suggest that if the rounding occurs in the text of the play, the rounding also occurs in regards to the AI that is being called to use.

Example: In a recent game, the team I own had 2 different results in similar situations. Three different times we had the ball on the 35 yard line (according to the text), and according to our AI (verified by a bugs mod), the only output is to kick a FG. However, twice we punted, and the third time, we attempted a FG. The only logical (non-bug) answer for this is rounding issues.

First Occurrence: Q1 12:39 4th & 9.5 on OPP 35 - Punt
http://goallineblitz.com/game/replay.pl?game_id=1703669&pbp_id=8892577

Second Occurrence: Q4 11:42 4th & 7 on OPP 35 - Punt
http://goallineblitz.com/game/replay.pl?game_id=1703669&pbp_id=8895736

Third Occurrence: Q4 2:26 4th & 18.5 on OPP 35 - FG
http://goallineblitz.com/game/replay.pl?game_id=1703669&pbp_id=8896223

If the sim rounds the text to say we are on the 35 yard line, this should be reflected in the play being accessed via the AI.

Note: I'm not suggesting to round every instance of each play within the sim code, just to make what the text reports be consistent in its rounding procedure with what we can call using the AI.
 
Novus
offline
Link
 
As long as the rounding only affects how the AI interprets things (and that is in fact what you're suggesting), I'm all for this!

+1
 
TrevJo
offline
Link
 
+1, but only for the AI yard line selector, not for the yards to go text boxes.
Reason being that there isn't a big difference between the 34.51 yard line and the 35.49 yard line, or even a huge difference between the 2.51 yard line and the 3.49 yard line.
But there is a very big difference between 0.51 yards to go and 1.49 yards to go. That could easily warrant a different play call.
 
spindoctor02
offline
Link
 
Originally posted by TrevJo
+1, but only for the AI yard line selector, not for the yards to go text boxes.
Reason being that there isn't a big difference between the 34.51 yard line and the 35.49 yard line, or even a huge difference between the 2.51 yard line and the 3.49 yard line.
But there is a very big difference between 0.51 yards to go and 1.49 yards to go. That could easily warrant a different play call.


This is exactly what I'm suggesting. Only for the yard line selector. If the text says you are on the 40, your AI should react as if you are on the 40, despite you actually being somewhere between the 39.76 and 40.24.
 
Pwned
offline
Link
 
+1
 
thunderdoozer
offline
Link
 
fix your build?
 
spindoctor02
offline
Link
 
Originally posted by thunderdoozer
fix your build?


Thanks for the bump, I guess?
 
tragula
title
offline
Link
 
-1

Why waste developer time over half a yard ?

This is a minor issue which only reflect on OCs and DCs (likely only OCs). The time wasted on this, can be used to do something that coordinators actually care about.
 
merenoise
offline
Link
 
+1
 


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