|
|
Post by iamgoot on Dec 9, 2017 6:07:41 GMT -5
Just went on the latest test server and it's horrible. The only new addition is a new game mode called King of the Hill which I'm not even sure what it is after playing a couple of games. Secondly they are allowing shocktrains and embers in this so that is all anyone is running and it's unplayable.
|
|
|
|
Post by Pulse Hadron on Dec 9, 2017 6:24:21 GMT -5
Yeah, they didn’t explain how it works and I can’t tell if it’s bugged. I looked around for a white beacon and there was only one, but getting to it found it was a faint white and it wouldn’t turn. Looked again, there’s no other white beacon. I start visiting every beacon site and then see it’s turned red on the other side of the map where I already saw it wasn’t.
Also, you have to stay near the beacon for it to drain. I’ve seen many players turn it then walk away to fight.
Battles are haphazard, confusing and deadly. Redeemer, Shocktrain and Ember make short work of most bots. And most players don’t get the mode or don’t care. I saw very few trying to go for the beacon.
Edit: maybe the faint white beacon is a cue to its next location. But they need to indicate where it’s current location is. Like it’s letter designation in the beacon pool icon.
Edit 2: peeked at the questionnaire and they ask a question from which I can infer the faint white beacon is the next one. How are we supposed to test something if we don’t know how it works. They should let use easily see the questionnaire contents so we have an idea of what to look for. Seems obvious.
|
|
|
|
Post by iamgoot on Dec 9, 2017 6:41:44 GMT -5
Yeah, they didnât explain how it works and I canât tell if itâs bugged. I looked around for a white beacon and there was only one, but getting to it found it was a faint white and it wouldnât turn. Looked again, thereâs no other white beacon. I start visiting every beacon site and then see itâs turned red on the other side of the map where I already saw it wasnât. Also, you have to stay near the beacon for it to drain. Iâve seen many players turn it then walk away to fight. Battles are haphazard, confusing and deadly. Redeemer, Shocktrain and Ember make short work of most bots. And most players donât get the mode or donât care. I saw very few trying to go for the beacon. Edit: maybe the faint white beacon is a cue to its next location. But they need to indicate where itâs current location is. Like itâs letter designation in the beacon pool icon. Exactly...i was confused by the beacon. I think it jumps about and you have to catch it where it is. It's just going to be a cluster 「fluffernutter」 |
|
|
|
Post by ѻﻭɼﻉ on Dec 9, 2017 18:17:08 GMT -5
Ok, first, if you want to take full advantage of test server, I suggest keeping an eye on the following: - In-app envelope for updated videos - This forum for relevant threads - The War Robots Facebook page - The War Robots Test Server FB page - Warrobots.net Regarding King of the Hill mode, it is explained here: warrobots.net/en/posts/173Basically, it is simply another form of beacon control. Most people in TS at the moment engage it as TDM and don’t pay attention to capture and control. First, there is a fight over Center. After a bit, the beacon vanishes and reappears elsewhere. What I like about this is it requires you to keep an eye on the beacon location and color, which appears to be a quality sorely lacking in some War Robots pilots, so maybe it will help them, although if they haven’t figured out by now that most modes are about beacon control and how to do that, not sure there’s hope for them. So, as usual, you will have to take matters into your own hands. |
|
|
|
Post by ѻﻭɼﻉ on Dec 9, 2017 18:51:41 GMT -5
And second, Embers and Shocktrains are not the only weapons being used, and even with quite a few out there, it is very playable.
I’m seeing and running Gust Stalkers, Redeemer Taran Boa, Gust Orkan Rhino, DB, Ancilot, Aphex Griffin, Redeemers on all sorts, Trident Fury etc.
Maybe you just had a few tough ones where everyone was using Ember and Shocktrain. Give it another whirl
|
|
|
|
Post by Nexsan on Dec 9, 2017 18:55:41 GMT -5
It's not like you can blame any of those players. Mail.ru created this mess.
|
|
|
|
Post by ѻﻭɼﻉ on Dec 9, 2017 20:04:28 GMT -5
Also, since Shenzhen is the only map atm, if you know there is going to be Embers, put more range in. Tempest Fury, Gunships, RDB, Trident rigs. Counter the excess Ember and Shocktrain with similar or longer range. If you just put more Ember and ST in, there will be more and more of that. I’ve just run several with Gunship Rhino and Tempest Fury. Lots of Ember ST mech murders happening there!
|
|
|
|
Post by Pulse Hadron on Dec 9, 2017 20:31:05 GMT -5
That explanation is vague. It doesn’t mention when the beacon is visible/available, how to spot it, if there’s a time gap between one closing and the next opening, that you have to stay near it to deplete, that there’s a faux white beacon indicating the next location. There’s so much basic detail left out and everyone has to figure it out for themselves instead of Pix just explaining it. |
|
|
|
Post by Pulse Hadron on Dec 9, 2017 20:41:38 GMT -5
Also, is this the only thread about the test server? Are a lot of people not bothering because of the event?
|
|
|
|
Post by ѻﻭɼﻉ on Dec 9, 2017 21:42:51 GMT -5
That explanation is vague. It doesn’t mention when the beacon is visible/available, how to spot it, if there’s a time gap between one closing and the next opening, that you have to stay near it to deplete, that there’s a faux white beacon indicating the next location. There’s so much basic detail left out and everyone has to figure it out for themselves instead of Pix just explaining it. I agree the explanation could be more detailed, but I got the gist from the general description: capture beacon, guard beacon, watch for it changing location. Easy enough. |
|
|
|
Post by ezekielcrow on Dec 9, 2017 21:51:14 GMT -5
Near as I can figure. You cant just run to any beacon. Only one is active at a time. You have to fight your way to it and defend it til the progress circle in your hud goes all the way down. Then active beacon transfers elsewhere for the cycle to repeat. Progress also seems faster when more meachs of a team are close to a beacon. Its pretty cool once you get the hang of it. But it doesnt really allow in depth testing of the new weaps. One is forced to come in with a competitive set up.
That said I tried a full plasma golem and it was awesome. I wish they had storm available to assemble a trench sweeper golem though. Gust jesse, gep, patton were pretty powerful. Perhaps a bit too much. Shocktrains flooded the map, making it confusing. I ran them on a rog and doc though and did similar set ups for the vortex.
|
|
|
|
Post by Pulse Hadron on Dec 10, 2017 0:06:04 GMT -5
The part I don’t get is when there’s no beacon available for capture. Is there a wait time for it to become active or am I just not finding it. Most times it does change quickly but I swear there’s been moments I check all locations and none are present. Bug or no? Can’t tell because I don’t know what’s supposed to be happening.
|
|
|
|
Post by Pulse Hadron on Dec 10, 2017 5:53:31 GMT -5
Here’s my test server video and it shows why I’m confused. My battles must have been bugged.
The first 1m40s shows me looking for a beacon that isn’t there, ending with a guess that you have to be near the beacon for it to appear and that the center would be that place, but I die quickly.
Then after 1m40s is another battle and again there’s no beacon. I go to the same faint beacon because that’s the only ‘thing’. There’s clearly no center beacon but at one point I look away and then back and center is blue. The beacon capturing ring was growing (which I didn’t notice) while I was looking at an empty center.
Then a battle after that the beacons seem to be working correctly and we capture and drain a couple, but both times the capper walks away.
|
|
