ios-personmd-notifications md-help-circle

Profile

  • Guest
    medal 0
  • Posts: 21
  • Post Likes: 3765

Notifications

  • No Unread Notifications

Approved
Driver reductions

angle-double-left ios-arrow-back 1 2 ios-arrow-forward angle-double-right
medal 5033
4 days ago

Jack
Training can easily be given a small boost as well, as a final balancing factor. It sounds like everyone feels the pit crew is reasonably balanced with 5%?



Yes. What you could do is reduce the amount of atrophy lost based on how many races and sprints you do in a season. So keep it at say ten then set the % of loss reduced so if a driver does all races in a season they only have five percent and then in that time frame say for every 5 sprints that driver competes in its another 1% or atrophy loss taken capped at 5% off so to have 0% atrophy your driver needs to take part in every race in the season and in that time frame also do 25 sprints.
md-quotelink
medal 5342
4 days ago Translate

Jack
Training can easily be given a small boost as well, as a final balancing factor. It sounds like everyone feels the pit crew is reasonably balanced with 5%?



You know, right? There are some recently acquired drivers on the market who don't lose atrophy. They're always 100%.
md-quotelink
medal 5374
4 days ago (Last edited by David Parker 4 days ago)
Just going to put this here now:

1025x312

This accommodates leagues with less than 7 day weeks and custom season lengths, as well as managers joining a league mid-season and giving them a slight atrophy to prevent league hopping.

It's based on three things: 
- number of race days remaining in the season (calculated from total races in the season, set to 15 above, and races per week, set to 7 above)
- number of non-race days remaining (calculated from total races and races per week if not 7)
- number of completed races (set at 0 in the image above)


The numbers can be played with, I made a Google Sheets version here:
https://docs.google.com/spreadsheets/d/11DSeQXdoG1SQXxdbrVlDtTYGC-McHUlVGwXR4LatQrs/edit?usp=sharing


The idea is that this would be applied when you join a league, or switch mid-season. In my separate post I made atrophy independent so that it would only need to be applied on specific occasions: joining a league, end of season, or the driver being hired.

Second example, mid-season with a custom schedule:

1025x312
md-quotelink
medal 5598
4 days ago
5% is still too much.
I am not going to be able to train fast enough before they get nerfed a second time.
Why nerf so many stats on pilots?
I could understand why moral might take a hit but everything else decreasing makes no sense to me.
md-quotelink
medal 5389
2 days ago Translate
David
Just going to put this here now:

1025x312

This accommodates leagues with less than 7 day weeks and custom season lengths, as well as managers joining a league mid-season and giving them a slight atrophy to prevent league hopping.

It's based on three things: 
- number of race days remaining in the season (calculated from total races in the season, set to 15 above, and races per week, set to 7 above)
- number of non-race days remaining (calculated from total races and races per week if not 7)
- number of completed races (set at 0 in the image above)


The numbers can be played with, I made a Google Sheets version here:
https://docs.google.com/spreadsheets/d/11DSeQXdoG1SQXxdbrVlDtTYGC-McHUlVGwXR4LatQrs/edit?usp=sharing


The idea is that this would be applied when you join a league, or switch mid-season. In my separate post I made atrophy independent so that it would only need to be applied on specific occasions: joining a league, end of season, or the driver being hired.

Second example, mid-season with a custom schedule:

1025x312



I think this should be the aim. Getting a system like this. 

I still have the feeling that with 5% you won’t be able to improve the drivers, you’ll just be able to keep them on the same level. 

For now we can accomodate with 5% until Jack has time to improve it. In 3 weeks when the season is reset and we have the chance to train the drivers we might be able to give even better feedback to improve the new system.

But like I said, we can accomodate until Jack has time to address it. He should focus on the other bugs right now, nevertheless this should remain a priority for the near future.
md-quotelink
angle-double-left ios-arrow-back 1 2 ios-arrow-forward angle-double-right

You must be logged in to post a reply.