
I personally would choose against giving players any info on it at all, as people cannot be trusted with that info ingame, and we already have fflogs for finding out precisely how we are doing.The thing is that that SE could calculate DPS in a run, true healing done (not overhealing), overhealing, damage taken, damage mitigated themselves, and time completed. They could take all of that information, compare it other players internally, give you ranking WITHOUT assigning a percentile rank or showing the player the actual number of DPS/True HPS/Overhealing/Damage Mit/Damage Taken which is fundamentally what logs are giving you when you look at somebody's parse in a fight. You just rank players in those categories as Poor, Good, Great and show the player but not the party that information except the ranking for completion time. Make an explicit rule in the ToS against asking players about their ranking unless they share that information with harassment rules in effect. People who get a great ranking get 1k extra gil added to their reward per category, or something that is conceivable small but adds up overtime.
Guess what happens next. Mr. Tank who gets a poor for damage mitigation goes "why do I keep getting poor rankings for mit?". He then goes looks up about damage mit techs and begins to understand that not only it will improve his rankings but it makes him a more enjoyable person to play with, which makes him more comfortable playing tank. The healer that gets a poor ranking in overhealing despite the party living goes "why do i keep getting this?" looks stuff up means to heal a bit more efficiently which gives them time to play around with using their "dps kit" (lmao). The DPS who gets poor damage ranks might check something to learn the importance of positionals, when to use their AoE rotation.
A casual player is not going to upload logs to fflogs and data from fflogs is only going to be relevant within the patch itself and only relevant to the current raid tier and ultimates within the patch. Parses for UcoB during 5.1 do not hold any relevance to parses from 6.1 outside of speed comparisons. Further, parses from sub max level dungeons are going to widely swing and typically do not have a sample size large enough to accurately make determinations that are free of kurtosis. So FFlogs is useless to a person leveling in SB or ShB content in order to determine if they are doing right. A ranking system I'm proposing is presented playerside rather than public and is instance specific rather than something overall standing such as a Raider.IO score from WoW. It just a check for the person to see if they are doing a passable job, a better than passable job, or doing poor across metrics without assigning a numerical value.
Even if another player asks what dps ranking you got for the dungeon and they provide their ranking, a "great" rating could mean fundamentally that you were at the 66th percentile to the 99th percentile. And again, you just put in the TOS "Do not ask other players for end of duty rankings" and enforce it with the same harassment rules should the player freely disclose that info.
What you suggest then is that you hope player just decided to get better but alot of player have no idea that they are playing suboptimally to the point where they are grossy extending the time in which it takes to complete the dungeon or that their play is negatively impacting other party members. Unless they are real gamers, most players need external motivation to improve and there are ways to do this via metrics that could be provided by SE in a means that is constructive.
|
|
![]() |
![]() |
![]() |
|
|
Cookie Policy
This website uses cookies. If you do not wish us to set cookies on your device, please do not use the website. Please read the Square Enix cookies policy for more information. Your use of the website is also subject to the terms in the Square Enix website terms of use and privacy policy and by using the website you are accepting those terms. The Square Enix terms of use, privacy policy and cookies policy can also be found through links at the bottom of the page.

Reply With Quote


