-
Notifications
You must be signed in to change notification settings - Fork 3
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Suggestion: Get player's currently active job, current HP, average item level, main weapon level and main weapon name (would help us determine player activity status). #8
Comments
Good call, but it would allow for some really fuzzy data because people also log out on alt-classes and crafting/gather classes. This would in my opinion only work for really large datasets to get a general line. And you then need to detach the battle/craft/gather classes from each other for a job breakthrough graph. Not saying that it wouldn't work. This should definitely be tried out. |
That's right, it would definitely need careful analysis before exploitation. |
Merge pull request #50 from crakila/master
It could be a good idea to grab the player's currently active job and their average item level (and, why not, the main weapon's item level too) from the player lodestone profile along with the rest of the currently scraped data. That would allow us to get a "snapshot" of what jobs are players playing at the time of the census, and maybe infer their main job from this additional data (e.g. by comparing levels or previous censuses). And it could also help us with distinguishing SCHs from SMNs.
Could be reflected in the DB with a column containing the class/job trigram of the currently active class in the lodestone, and another containing the average ilvl.
The text was updated successfully, but these errors were encountered: