MA: Getting Hamstrung | War Robots Forum

nocluevok
Ao Jun

Posts: 2,186
Karma: 2,047
Pilot name: Ima Badshot
Platform: Android
Clan: Me, Myself, & I
League: Master
Server Region: North America
Favorite robot: Blitz

MA: Getting Hamstrung Jan 7, 2022 13:29:38 GMT -5 via mobile

Quote

Post by nocluevok on Jan 7, 2022 13:29:38 GMT -5

Been working on the beacon task for the Lancer (only 98 to go) but here lately I've run into what I believe is an intentional roadblock. I cap the first beacon and a few steps from the 2nd, my Lancer's forward progress glitches. As in the control flickers and I'm suddenly running backwards, forward, backwards. Only happens when an AI teammate reaches the beacon first. We aren't close enough for the AI bot to be pushing me off. The glitch stops when the beacon has been capped and my opportunity is lost. This only happens to my Lancer.

I don't mind not getting the 2nd beacon when the MM decides to beeline my AI teammates straight to beacons, but this is ridiculous.

Some folks might argue that it wasn't a fair fight. I disagree. That Racoon had the option of whoopin' all them dogs and walkin' off.
-Jerry Clower -

S1E1
Ao Jun

Mr. Footloose

Posts: 2,443
Karma: 3,112
Pilot name: S1E1
Platform: Android
League: Champion
Server Region: North America
Favorite robot: Strider

MA: Getting Hamstrung Jan 7, 2022 13:45:37 GMT -5 via mobile

Quote

Post by S1E1 on Jan 7, 2022 13:45:37 GMT -5

I have had a similar glitch but it has occurred with multiple bots and usually near a wall (though not that near). It seems like some weird invisible object glitch even though it does do the forward/backward stutter and doesn't just stop me in my tracks. Has happen in both beacon and TDM games for me though not recently. It is quite frustrating.

Redfiend
Invader

Mech Arena Trusted Contributor

Posts: 1,084
Karma: 1,454

MA: Getting Hamstrung Jan 7, 2022 19:27:45 GMT -5 via mobile

Quote

Post by Redfiend on Jan 7, 2022 19:27:45 GMT -5

The server prioritizes AI pathing, which is why they can push you, but not vice versa. A temporary desync, even for a moment, can have the server accidentally peg both mechs at the same coordinates, and that's when it gets all wierd trying to recalculate and reposition everyone so two mechs don't appear to be occupying the same space server side.

Last Edit: Jan 7, 2022 19:28:23 GMT -5 by Redfiend