Xenoblade X - Time Attack: The Wrothian Samurai - 3.5s (OUTDATED)

Channel:

Abarax

Subscribers:

223

Published on December 26, 2018 12:42:56 AM ● Video Link: https://www.youtube.com/watch?v=G5dIuo5Zi6Q

Game:

Xenoblade Chronicles X (2015)

Duration: 1:15

318 views

4

A new attempt at The Wrothian Samurai - again, not a WR but a new best in the west… there is a story behind this one too. Hellfire always seemed to be better off second, I looked at a few dozen setups involving various gatlings, headgear, True Bangle R (R-ATK Boost XX), melee weapons etc, but I couldn’t come up with anything better. However the Japanese record is supposedly 3.3 seconds, so this time can be beaten - additionally I took a little too long to target and use the art so it can possibly be beaten with the exact same setup.

I’m sure you don’t want to hear the story so here it is:

TL;DR - someone had a different build than usual, checked TA leaderboards, my score was beaten, calculated a better build, spreadsheet had errors, disconnected, broke record offline, enemies spawned in order I had never seen before which would have affected how I setup, changed calculation, broke record.

I woke up on Christmas morning and Aimi (J.U.N.I.) had a different build on - Gat/Knife (as opposed to the usual Sniper/Knife). I wondered why, and out of curiosity, checked all the TA leaderboards. To my surprise he had got 3.8s on Wrothians. Well that just wouldn’t do would it?

I calculated a build that would easily beat it and put it to the test - didn’t even get Vasara to half HP. Closer inspection revealed that my enemy stat calculator was pulling data from a dummy level 1 Vasara, and its HP was actually 377, 491, quite a step up from the story counterpart, and almost double what my calculator was saying.

Well that was annoying so I had to redo the calculation. I had the game running while I was doing this (I sort of just sit there and look at the spreadsheet and see what I could change, trying to see how I can kill the first enemy with minimal effort and then put everything else into killing the second as fast as possible). During this I disconnected from the server, but I went in and tested my new build anyway and got 3.7s - I was wondering if it would upload that but I beat that later anyway.

The problem with this though, was that something happened that I hadn’t seen before, and that would have affected the calculation I used - the Deva Caladar spawned in first and it was targeted first. Vasara and the Deva Caladar have different resistances, and also different appendage hardnesses. I was a little concerned because it happened a few times in a row, but after I returned to title screen and signed back online it seemed to go back to normal and spawn in the Vasara first, so I could use my initial setup.

Other Statistics