I don't think you can edit that. It's programmed I think.
On flat stages, the game counts a gap when there's 20 seconds between 2 riders.(Not groups, but between riders)
On hilly rated & mountain stages, that's 7 seconds.
Also, it makes sensem because on a mountain summit finish, it takes the rider a lot longer to ride 50 meters, so you shouldn't look at the meters.
I totally agree. I often try the short breaks or sneak attacks too.
I've had stages where there was a considerable gap between me and some important opponents, but due to some scattered riders in between (and not exactly together) that gap ends up being exactly nothing.
I know that a group or pack should have the same time, but sometimes it's a bit too much. Funny thing happens when one of your riders get behind the peloton. You will enter the peloton at about 1 minute gap or even more
when it comes to finishes, there should be some sort of minimum distance or those 20 or 7 seconds should be reduced quite a bit. 5 seconds for flat and 2 for mountains or thereabouts.
Edited by itisix on 30-08-2013 17:18
There is a thing called "game balance". You cannot change every bit (training and gaps was brought up lately) and believe that the game would still be fun to play.
Instead you should adapt your playing style to the game. Taking the time gap for example, it is almost pointless to make a late attack. (unless you time it right)
BTW: Trying to win time on on the finish line with a GT rider is somewhat unrealistic. Furthermore the AI is not programmed to react on late attacks or do late attacks too. The same goes for bonus time in the intermediate sprints.
itisix wrote:
when it comes to finishes, there should be some sort of minimum distance or those 20 or 7 seconds should be reduced quite a bit. 5 seconds for flat and 2 for mountains or thereabouts.
5 seconds is really low and probably would make it a non-race occurrence to have the peloton reaching at different groups/times. But 10~15 seconds would be better indeed. This used to be possible to be edited in the .cdb (so f.e. a DB could put all flat stages in 15 time gap), but now it can only be edited in the stage file (by the stagemaker). Mountain I don't think should be changed though, with 2 seconds there'd be like no groups in the results in mountain stages 7 seconds is good enough there imo.
I've never seen that, can you post an image? But this goes the opposite way of your previous post: if the stages have a lower gene_i_time_gap, there's more chance that the gap of a late attack will be counted, but there'll be a much bigger chance that sprinters will get their own gaps. While if it is raised, the "totally not right" thing of top sprinters getting a time gap would be fixed, but late attacks wouldn't.
I don't have a screenshot but if that happens again I'll post it.
The sprint gaps are, off course, a different issue, but this looked like the place to post it to put things into balance.
7 seconds is good enough there imo.
