Was one of the players using wifi?
I was. I can test with a wired connection as well if someone wants to play. That said, my wireless connection offers me about 60-65 Mbps. Is the auto-forfeit a bug or a feature? To us yesterday, that was by far the most annoying - the bugs were tolerable to an extent, and often just hilarious things we brushed aside.
I suppose to track some of this down you'd need to get a few people who have recording equipment to be able to capture both ends of the same online game and compare what's happening visually on both consoles - whether for some of these strange dismissals you're actually just having one side see it as a perfectly normal dismissal, and something crazy on the other side because the game hasn't synced up.
Possibly, although some of the errors are not visual bugs (like the auto-forfeit). Also, @
kushari and I noticed most of the same things (we discussed the bugs and were
live commentating during the game). Both of us noticed the full-pitched shoulder-high no-balls. Both of us noticed the batsman being given out bowled when the ball only hit his body. I can't say if both of us noticed the same exact warping or not, but we did notice warping.
I also noticed several of those issues, including bowling too many deliveries in the over. It seems that once you are no-balled (wrongly) for apparently (not) overstepping, the game gets seriously buggy. Also spinners and medium pacers getting no-balled for bouncers is very annoying.
Getting wided for balls hitting the batsman is also something I noticed one or two times.
Also the forfeit thing is annoying as well. Bowling is a nightmare in online mode and I think the bowling meter would greatly help reduce this. Also will make batting a bit more challenging because the bowler can control the deliveries better in a tight match. Would add to the excitement.
All four things you said are true and are a concern for online - too many deliveries, the full-pitched bouncer no-ball, wides when it hits the batsman, and auto-forfeit. Auto-forfeit is the worst, and the forfeit rules themselves are too strict. Three wides is too little a trigger, considering how difficult it is to bowl and considering that playing this game should be a leisurely activity, not a test.
I'm pretty sure the issue is with wireless play, things just go badly out of sync.
Even auto-forfeit and the strict forfeit rules? I understand that you want to deter time-wasters, but three extras in an over is not too big a sin in my opinion, and it is often not done intentionally by players who have often playing online for the first time and have just realised that there is no bowling meter. At the very least, if you do decide to keep auto-forfeit, that option must be toggled off by default while setting up matches. The fact that the game isn't auto-saved means the entire time invested into the game is lost, or rather, it feels like it's stolen.
We did not test on wireless as we can't have wireless connected to the dev kits for security reasons. We will be testing the retail versions this week to try and pin it down.
Thank you. This is appreciated. No one can complain about you not supporting your customers.
I'm thinking that there really needs to be a counter for field changes - or at least have a limit on the total time in a match that can be spent on making changes, instead of just having one off 30 second timers.
I think the 30 second timer is per over and not one-off. Is there a way to save our most-used fielding positions as 'favourites'? If a batsman is smashing you towards covers and you want to search for an appropriate field, it often takes about 15 or 20 seconds. If you've done this as a bowler, a forfeit is offered.
Also, the fielding needs to be constant for every bowler and batsman (at least for every batsman) unless manually changed (field restrictions permitting, of course). Right now, it defaults to a different field each time the batsmen change ends or the bowler changes, even when you don't want that. The opponent is still trying to hit me to covers, no matter who the batsman or bowler. Considering the amount of times a bowler needs to change his field back to the same one as it was one ball before, this can easily run into the 30 seconds time limit.
A limit on appeals per match would be nice as well - so people don't just hit that on every ball.
Yes. Or just get rid of the cutscene. The umpire takes about three seconds to decide, and then the players take another three or so seconds to decide if they want to review or not.
One other issue: I noticed that the timer which counts down from 30 actually keeps going when I start my run up and I lose more seconds on my next attempt to set field. Is this timer for the entire over or only per delivery? Because I noticed it kept counting down from where I left off in the same over.
Yes this happens often. Each time you change a field, you lose an additional two or three seconds during the run up. This is crucial time if you've had to change your field two or three times an over, which itself is because the game doesn't keep the positions static (or just to confirm if this is actually your field, because without a fielding radar, there is no other way for a bowler to do so).
