Fixing Player engagement DEV pls consider

[DPZ2]

The primary question for all of this:

Are you willing to endure the latency that would be generated in a 24-man battle in order to record and analyze how 'good' you are? That's a lot of data to analyze on-the-fly.
Remember, this is data that would need to be reported back to the servers, rather than to a file on you local computer, for. Every. Individual. In. A. Raid.

[Ath192]

The primary question for all of this:

Are you willing to endure the latency that would be generated in a 24-man battle in order to record and analyze how 'good' you are? That's a lot of data to analyze on-the-fly.
Remember, this is data that would need to be reported back to the servers, rather than to a file on you local computer, for. Every. Individual. In. A. Raid.

Hmmm... Not necessarily, the game already tells you via chat log how much damage your attacks do, who gets what effect, who dies to what, so it already does all of that correct? So at the end of the instance it can run a report and compile the information since the rewards would be given after the fact which can count as part of the server resources used for that reserved instance. Yes, the number crunching may take additional resources but the information is already available, I believe the PVP instances such as hidden gorge already produce a scoreboard saying how much damage everyone made and whether it was to structures or players. And those are large instances with many players as well.

That being said, I am not an expert, but the PVP scoreboard seems to indicate this is possible.

[Nethereal]

The primary question for all of this:

Are you willing to endure the latency that would be generated in a 24-man battle in order to record and analyze how 'good' you are? That's a lot of data to analyze on-the-fly.
Remember, this is data that would need to be reported back to the servers, rather than to a file on you local computer, for. Every. Individual. In. A. Raid.

Very much a non issue. The site that shall not be named does exactly this and also keeps a 2d recording of everything, SE wouldn't have an issue doing what a random site with less funding can do.
They won't though simply because the method is tried and true and now ffxiv is in the milking phase, no large changes will be made to the recipe anymore, especially with yoshi leaving the scene.

[linayar]

yoshi leaving the scene.

What are you talking about?

[DPZ2]

Very much a non issue. The site that shall not be named does exactly this and also keeps a 2d recording of everything, SE wouldn't have an issue doing what a random site with less funding can do.

Are you are implying that which has no name actually pulls the data from the SE servers?

I know how that which has no name works in other games that don't have one built in (WoW, for example). It reads battle data sent to the user's computer in real-time and records it. It uses your computer's CPU and memory, not the MMO company servers. It is also doing so for a single battle environment, not every battle environment occurring at the same time across all servers.

Talk about ping ...

[Penthea]

Are you are implying that which has no name actually pulls the data from the SE servers?

I know how that which has no name works in other games that don't have one built in (WoW, for example). It reads battle data sent to the user's computer in real-time and records it. It uses your computer's CPU and memory, not the MMO company servers. It is also doing so for a single battle environment, not every battle environment occurring at the same time across all servers.

Talk about ping ...

Yeap all a parser does is use the info from your combat log.

If parsers pulled data directly from the servers SE would have a super easy time tracking down who used them, which would mean it would be easy to figure out who to ban. It's because it uses client side data that SE can't tell who is using a parser from their server info. Sure the info that the combat log gets is from the server, but a piece of software does not need to be connected directly to the servers to read a body of text, which is what the combat log is.