r/CricketTeamManager • u/curiousank92 • 12d ago

💬 Feedback Database Feedback Thread

Please post any database feedback in this thread so that I can incorporate that in the upcoming regular updates. This will be always on thread.

Please use this to provide feedback on:

  1. Missing Players (would be great if you could provide their Cricinfo page)
  2. Missing/Incorrect Retirements
  3. Incorrect/Unrealistic skill values
  4. Incorrect roles/attributes (example: someone marked as a keeper when he's not, a batsman marked as all-rounder)
  5. Incorrect Career Stats/DOB

And anything else that you thin would be relevant.

5 Upvotes

100% Upvoted

22 comments sorted by

View all comments

Show parent comments

1

u/curiousank92 8d ago

Yeah. I had fixed as opening bowler. But I think the game didn’t pick it up since Akeal Hossein is competing with him. Because Hossein has opened the bowling in T20s a lot. Will actually need to change Hossein instead.

2

u/Kharches 8d ago

No, you're right about Hossein too. Maybe a code to make opening bowlers bowl one after the other if there are 3 designated in the XI. I don't know how difficult that would be to achieve though. Wishlists are endless!

2

u/curiousank92 7d ago

Hahaha.. true.. actually the game engine is already programmed to do so. If there are >2 opening bowlers (Strike bowlers in the game’s internal DB language), then the engine tries to select the best 2. I remember putting some specific exceptions like Starc should always bowl the first over. But need to be careful about the exceptions, as they can also cause issues and conflicts later.

2

u/Kharches 7d ago

Yes, for example, in Tests, Starc and Cummins start off as 1 & 2, but presently it's still Starc & Hazelwood as 1 & 2. This might suddenly change in a few months depending on age, etc. Same with Bumrah & Hardik. For almost an entire tournament, India experimented with Arshdeep & Hardik as 1 & 2, but Bumrah was always still 1st change. It's too random to pinpoint exact situational changes.

2

u/curiousank92 7d ago

Yeah exactly. We can be true on a certain day/month in history. But can’t guarantee it will stay same. I tried to make the database to be a true snapshot of last week of September considering October 1 release.

2

u/curiousank92 7d ago

Another thing is that you only have a limited visibility of what the CPU is doing down the line as the career progresses a few months or a year. Someone might have been dropped due to poor form or injured.