About: (6)Ness vs (3)Auron 2004   Sponge Permalink

An Entity of Type : owl:Thing, within Data Space : dbkwik.webdatacommons.org associated with source dataset(s)

Another day, another horribly predictable match in the Midgar division. Ness was fresh off of a heated victory against Jak, while Auron was coming off of a killing against Scorpion. So what do they turn around and do? Ness winds up doing far better than his 26.87% projection. But like the Squall/Kirby match, this meant nothing. We had no way of verifying the strength or weakness of either character, simply because of how the Midgar division was set up. Auron winning this match was a virtual guarantee, but thanks to Auron/Sephiroth being set up from the start, we had no clue what to make of this match.

AttributesValues
rdfs:label
  • (6)Ness vs (3)Auron 2004
rdfs:comment
  • Another day, another horribly predictable match in the Midgar division. Ness was fresh off of a heated victory against Jak, while Auron was coming off of a killing against Scorpion. So what do they turn around and do? Ness winds up doing far better than his 26.87% projection. But like the Squall/Kirby match, this meant nothing. We had no way of verifying the strength or weakness of either character, simply because of how the Midgar division was set up. Auron winning this match was a virtual guarantee, but thanks to Auron/Sephiroth being set up from the start, we had no clue what to make of this match.
dcterms:subject
dbkwik:board8/prop...iPageUsesTemplate
abstract
  • Another day, another horribly predictable match in the Midgar division. Ness was fresh off of a heated victory against Jak, while Auron was coming off of a killing against Scorpion. So what do they turn around and do? Ness winds up doing far better than his 26.87% projection. But like the Squall/Kirby match, this meant nothing. We had no way of verifying the strength or weakness of either character, simply because of how the Midgar division was set up. Auron winning this match was a virtual guarantee, but thanks to Auron/Sephiroth being set up from the start, we had no clue what to make of this match. The logical explanation, of course, is that Ness went up due to unaccounted Bowser/Ness SFF in the 2003 Xsts. Maybe he truly was stronger than many of us thought, but how do you explain Auron overperforming so much against Scorpion? It really sucks that the bracket was set up the way it was, because there was no way to verify the strength of many of these characters after such odd matches. This match was another example.
Alternative Linked Data Views: ODE     Raw Data in: CXML | CSV | RDF ( N-Triples N3/Turtle JSON XML ) | OData ( Atom JSON ) | Microdata ( JSON HTML) | JSON-LD    About   
This material is Open Knowledge   W3C Semantic Web Technology [RDF Data] Valid XHTML + RDFa
OpenLink Virtuoso version 07.20.3217, on Linux (x86_64-pc-linux-gnu), Standard Edition
Data on this page belongs to its respective rights holders.
Virtuoso Faceted Browser Copyright © 2009-2012 OpenLink Software