In coding that mostly happens but previously sorted out issues only re-occurs if you copy paste some part or don’t know the code structure or behaviour exactly.I think BigAnt seriously has code merge issues. Why does the issues that were fixed in earlier builds keeps popping out again in new patches. This almost keeps on happening on every patch.
They take effect next match.If we edit skills of a player mid match does it take in to effect in the same match or only on new match
If its every batsman playing these same shots then it's a cause of concern, if it's just one batsman then it's the player trait right?Just quit the test match could not handle these weird upper cuts and shots from markram on a day 1 green track. Disappointing to see
I reiterated the same thing a few days back that, like in real cricket batsmen plays according to the line of the ball so if the ball is swinging away from from right hander he will have to play at that bcoz the line of the ball is on stumps but in games AI is not designed in that way at allThis games bowling is the worst of all the Big Ant games. What you bowl, how you bowl and the things you do mean nothing. If the game decides a batsman should be out they'll be out but if they decide not then the pitch, the day and the bowler will not matter. Really disappointed in the bowling experience in this game. I feel I have no control and the game decides what will happen or not. Don't feel I am earning wicket at all, set-ups don't work and the fact that the AI know exactly if something will hit the stumps or not is a big part of it I feel. The can leave deliveries you would never leave batting because if you did you'd lose your stumps. I think this is proven as well because I haven't had a bowled without the AI playing on (even if you get the replay of no touch).
Should have released the game mid 2022 but you got greedy sir. Now the pressure is making you cry like a teenage girl who lost her boyfriend.Are we all imagining things?
View attachment 261575