You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment when comparing battle scars you have to know exact name of player otherwise some random name (at least that what appears to me without close code investigation) with same set of starting characters is used.
Example: I wanted to look up KnoxBE and forgotten that "BE" is at the end, so I typed Knox, returned user was Knox101.
We should investigate if there is way pre-check for 100% match in name, or how to retrieve list of options.
Second: There should be check if player has more then one persona and offer option to select which should be used for comparison.
Thirdly: As from what I seen in application, first are loaded data for "my" profile, then "compare to character". I believe it should be easy to then run simple compare function that could put in bold formatting on better performance data. Example:
12.9% Accuracy 13.8%402.96 m Longest headshot 326.88 m
The text was updated successfully, but these errors were encountered:
At the moment when comparing battle scars you have to know exact name of player otherwise some random name (at least that what appears to me without close code investigation) with same set of starting characters is used.
Example: I wanted to look up KnoxBE and forgotten that "BE" is at the end, so I typed Knox, returned user was Knox101.
We should investigate if there is way pre-check for 100% match in name, or how to retrieve list of options.
Second: There should be check if player has more then one persona and offer option to select which should be used for comparison.
Thirdly: As from what I seen in application, first are loaded data for "my" profile, then "compare to character". I believe it should be easy to then run simple compare function that could put in bold formatting on better performance data. Example:
The text was updated successfully, but these errors were encountered: