Heh I played daboob today. He was with one very good player Mister_E and another who was decent named KOOOBEEE. I found him to be an average player. Fortunately his teammates weren't - KOBE did manage to get a good snipe on me early in the game after I was in a 2v2 with Mister and boob. We had a new rook who didn't really know how to use towers or which items to get, so he fed them quite a bit, 6 or 7 deaths I think, then left. The erebus on my team was actually good, despite having played so
grimunk
If you die due to a snipe you have overextended yourself. Reg on map is an automatic -500 hp, so act as though you are always down this many. Best way to deal with him is using teleport/batswarm and stuns to gank, as well as a friend.
bump again. Just gave 3 free kills to the other team thanks to this bug. It seems to happen when you try to cast it from just outside it's range. However, I did't ever regain control of my DG until after he was killed and respawned. It sux, coz I actually like the sludge slinger, but can't afford to actually use it since it ends up killing me.
IMO it's a bad idea. The game stacks fast enough as is. You will see concedes or quits earlier and more often.
This looks an awful lot like a blocking call to connect() with a 3 minute timeout. Now, it's one thing when you have a blocking connect() call that hangs the game, is it quite another when your game blocks alt-tab, ctrl-alt-del, and prevents other windows from being displayed over it (such as taskman.exe). You are hijacking the system and effectively hanging it thanks to bad code. Running in Windowed mode is the workaround, but in all honesty, a complete system hijack is not the correct way t