Profile Mounts/Minions moved to their own subpath and README unclear on inability fetch Names without an `event` on `userAgentDesktop`

[XxInvictus]

I am mainly logging this to track it, I may see if I can raise a PR at a later time unless someone gets to it first.
Unfortunately due to the structure where the name does not exist outside of the lazy-loaded on-click tooltip I can not see an easy way to get the Mount/Minion names in CSS Selectors alone for userAgentDesktop. For the time being it looks like the clearest path is to update the README for clarity.

meta.json Paths

profile/mount.json Before: https://%s.finalfantasyxiv.com/lodestone/character/%d/
profile/mount.json After: https://%s.finalfantasyxiv.com/lodestone/character/%d/mount/

profile/minion.json Before: https://%s.finalfantasyxiv.com/lodestone/character/%d/
profile/minion.json After: https://%s.finalfantasyxiv.com/lodestone/character/%d/minion/

HTML Structure / Behaviour

Minion

On Page-Load:

On-Click (of thumbnail):

Mount

On Page-Load:

On-Click (of thumbnail):

CSS Selectors

TBD

[XxInvictus]

Additional information, inspected the URL for the image which is essentially the only thing available without the click event and there does not appear to be anything in the image path or filename that can be used to identify the mount when compared against ffxiv-datamining

[emberquill]

The readme mentions that you need to use a mobile user agent header to scrape mounts and minions. The mobile version of the page has the names directly on the page instead of injecting them into tooltips.

[XxInvictus]

@emberquill That makes sense and I can confirm that it works with the mobile UA but from my testing, not with the desktop UA of curl/7.73.0. That is the UA I was testing with as I expected similar behaviour. So I guess the scope should be changed to just update the README to clearly indicate that the Mobile UA is more reliable over the Desktop UA 😄

[XxInvictus]

It does also look like even with the mobile UA the mount and minion details have still moved to a sub-path so that update to the Uri's is still required.

[XxInvictus]

Updated the issue to be more accurate to the final issue/purpose and raised a PR for the subpath/README clarity fixes.