They're wrong, it's not caused by high server latency.
I can put the timer up to ten minutes and I'll still get the error, something is wrong with demonbuddy's interaction with D3.
Makes me not want to use DB because it's a HUGE easy detection flag, happens every freaking game.
Enter game, sit there for a delay... Then DB tries to do something when starting the run, and BAM error message every time
[02:13:42.604 N] Waiting 52.8 seconds before next game...
[02:13:49.540 N] Loaded profile In a Rush - Dahglur Oasis
[02:13:49.766 N] [Trinity] New Game - resetting everything
[02:13:49.785 N] GameChanged. Clearing actors
[02:13:49.808 D] Joined a game!
[02:13:49.810 D] [QuestTools] LastJoinedGame is 11/28/2013 19:13:49
[02:13:49.810 N] [Trinity] New Game - resetting everything
[02:13:49.829 N] ProfileOrderManager.OnGameJoined, Reloading profile.
[02:13:50.043 N] Loaded profile In a Rush - Dahglur Oasis
[02:13:50.043 N] Game joined, Resetting profile caches.
[02:13:50.043 D] Resetting current behavior.
[02:13:50.044 N] ========== Grid segmentation resetting!!! ============
[02:14:35.415 N] Creating new game. Params: [Act:A2 Difficulty:Inferno Quest:57337 QuestStep:41 ResumeFromSave:False IsPrivate:True Handicap:5]
That's not server delay. It sat there for a fraking minute, in-game and tried to create another game which is the reason the error pops up. Why does DB do this? I don't know, but it's definitely NOT server lag and they should stop using that as a default answer
