Day 2 and still getting Failed to connect to the lobby error with Warhaven's playtest. Oh well. Probably giving up after today. Note: the most recent feedback is it wasn't antivirus/firewall/security but DNS and that changing your DNS servers to Google (8.8.8.8) would be the panacea. Narrator: It was not.
This is my experience with Warhaven's playtest; or really not-play testing anything at all because I can't get past this error: Failed to connect to the lobby. Please try logging in again later. I've tried everything from ensuring its allowed in the firewall, to disabling things like Malware Bytes and other antivirus software. Nothing works to fix this that I've found.
A couple quick items to meet my "post a day" quota for today.
New World lessons learned
First, Scot Lane has a guest article posted on Venture Beat: New World: What we’ve learned during our first year. I will have some more thoughts on this article to post later this coming week, but for now I am really glad to see this quote up front:
There is a saying that live games are owned by the development team until launch, and then at launch they become the players’ game. I couldn’t agree more.
I couldn't agree more myself and feel this is how the New World team has and continues to handle this game.
Warhaven
Second, I caught wind of a game called Warhaven that is in a free beta period. Ironically it caught my attention because of New World and the below video posted by Atlas Fishmo on Youtube. What I like about what I've seen so far, and I hope to play it later today after it downloads, is that the combat has weight to it. This isn't the rollie pollies combat of New World; this is medieval combat with some heft and weight to it. Fights are up close and personal and attacks and abilities are highlighted so the player can understand what is going on without having to rely just on catching an animation or sound clue. I will share thoughts this week on my experience.
