Please move CurrentPlayerData.txt to \AppData\ and include Character Name and Current Map Name.

@Chris @Attenwood

9/21/2016 8:08 PM
Title: Please move CurrentPlayerData.txt to \AppData\Roaming\Portalarium\Shroud of the Avatar\ and include Character Name and Map Name.
Reproduction Rate: 100%
Blocker? no
Details: So CurrentPlayerData.txt is currently in the root folder of the game and it only includes the location data. It should instead be in "\AppData\Roaming\Portalarium\Shroud of the Avatar\" and include Character Name and Current Map Name. The area name as well as the template name would also be appreciated. This would make things very useful for third party tools such at SotAMapper and the SotA HUD.

EDIT: I've added Orientation to the example output.
Edit 2: changed to xml.

Example Output:

 

Good ideas! I submitted a request to support asking that the CurrentPlayerData.txt file have the same output as the /loc command and Berek indicated they were looking into that. A couple thoughts...

• Moving it to APPDATA make sense
• I think it should at least include everything in the /loc command which would be area name, map name, and location. Also including player name would be nice, but we don't want to lose out on area name. Some have pointed out the POTs may use the same map but have a different area name so including area name (like the /loc command has) would be important to know which POT of a certain template you're in

 

Agreed. This should be done.

 

Would be nice to have /stats info added to it also. That's pretty useful CurrentPlayerData.

 

I thought about this but the problem with that is it's outputting a lot of data every 2 seconds which most of the data won't change and could cause unneeded drops in performance. So it would probably be best to keep that where it's at or in a separate file that outputs at a slower rate. I don't think outputting the data I listed would be a large performance increase.

 

I was thinking to add it when shutting down the client, not 'live'.

 

I thought of one additional piece of info that would be fantastic to have. Template rotation. Either as the number of degrees of clockwise rotation (0-360), or if they are ONLY ever in multiples of 90, a 0-3 multiplier.

 

This has been added to JIRA along with the request for the orientation/rotation.

 

@Attenwood can you put a note on the jira to format in xml like the above? If not that's OK. I know the map guess wanted all the output from the /loc command but Lord Viator thought xml would be a good way to format and I agree if it's not too hard to do that.

 

Thought of another piece of info that would be useful to know. The bounds of the map, i.e. the top left and the bottom right coordinates. Together they tell you the size of the map for apps like SotAMapper to be able to calculate size of map.

 

That will be nice if we can relocate the file (parameter or in a config file) or to store on temporary location (%TEMP% or ${TEMP}).
Reason: I install on SSD to have good performance and I like that SSD doesn't have too much write (SSD life).

 

Was able to steal some time from other tasks to make some changes for this today:

 

could the friendly name someday be in the /bug data too? i've often seen qa people asking players which town the bug they're reporting is in because the /bug info only gives the template name.
@Attenwood

 

Done!

 

@BurningToad, one change please. can we have:
<location>
<x>206.6</x>
<y>37.997</y>
<z>251.5</z>
</location>
? Instead of the loc_x loc_y loc_z elements.

 

Any particular reason? Do others want this change as well?

 

Personally as a developer, i'd have just put it out as the CSV it was and leave out the bulky XML, especially how often it's read/written/parsed.
But since we're already going to go bulky which does facilitate future changes, i prefer the overly-descriptive variant, so I vote to leave it as loc_x.

Thank you for doing work on this @BurningToad, it's much appreciated. Now if you can poke whoever was in charge of putting an identifier on each type of chat (npc/whisper/combat/etc) and on the translated strings (i.e. a dodge in english and a dodge in italian would both be the ID of a dodge, even though they say different things) in the chatlog we'd be set.

 

Just seemed semantically more appropriate. I'm not particularly bothered if it stays as it is, as I've already written the code to read and parse the xml as it is.

[EDIT] Consider the request withdrawn ;-)

 

No, me, I don't want that change. I prefer the loc_x loc_y loc_z elements.

 

It was never CSV. This file was always plain text with a single line of content.
My personal choice would have been for plain text, single key: value pair per line. However that's not what we have, and I'm content to stick with what we now have.