census info from offline guild status
-
guest
census info from offline guild status
is there anyway to allow census updates from the guild member offline status window? That is, if I open up the guild info window and check the offline status box, census info would be gathered/updated about who's still in the guild from that? so, for example, if someone was previously recorded as being in my guild but left/transferred, Census+ would/could gather the full member roster of a guild via that window and at least remove the guild association?
It *can* do that, although this is not happening currently. The problem here is because I do not know which submitted info to take as authority. I am working on a new feature that will hopefully enable this type of functionality for certain people (like guild masters or officers).
I am working on some fixes for this that I'll hopefully be able to roll out soon.
I am working on some fixes for this that I'll hopefully be able to roll out soon.
phpbb:phpinfo()
...
can you not allow the latest submittal to be the authority. there will be a lot of info that is not gathered by restricting this information-gathering to officers, no? and this information is generally not something non-officer players are going to bother w/ counterfeiting, is it? I mean, if they are so motivated to submit unreliable/false info that someone was in a guild (which is the core of what ya are concerned w/ when ya say 'info to take as authority', no?), they can just as easily edit the file before its uploaded, no? or figure out what parameters represent being an officer or guildmaster of a guild and edit that into their upload, no?The problem here is because I do not know which submitted info to take as authority.
It just seems like a nice info-gathering feature to implement if its available. /shrug
Here's the reason I can't just do a blanket accept on the last submission.
Let's say Joe plays on Garona. Let's say Joe joins the Cable Repairmen of Azeroth guild. Joe logs in one day and takes a Census and gathers his guild information.
Now, let's assume Joe decides there are just not enough hot chicks on Garona so he decide to go try out Silverhand. Joe never returns to Garona yet unless he purges his data, he still carries the guild and census data from Garona.
Anytime from this point forward that Joe submits his data, we also get the data from Garona that is no telling how old. This data could be very out of date and incorrect.
There are a few things I do to minimize this and there are some things I may do in the future to do it better. For starters if the level of the character I am updating is lower than what I currently have, then I ignore that entry.
What I could do and what kind of sounds like a good bet to me now, is to include a Timestamp that will let me know when the guild data was collected and only use collected guild data that was gotten in say the last 7 days. I could then clear out all members of a guild and rebuild it from the latest guild dump.
I could also aknowledge if someone is an officer or GM of a guild and take their listing as authority, but in all honesty, a GM or officer is just as capable of submitting out of date guild info as well.
So I will probably end up dating the guild data. Which would mean another release, hehe.
I'll keep thinking on it and will hopefully have a good solution soon.
Let's say Joe plays on Garona. Let's say Joe joins the Cable Repairmen of Azeroth guild. Joe logs in one day and takes a Census and gathers his guild information.
Now, let's assume Joe decides there are just not enough hot chicks on Garona so he decide to go try out Silverhand. Joe never returns to Garona yet unless he purges his data, he still carries the guild and census data from Garona.
Anytime from this point forward that Joe submits his data, we also get the data from Garona that is no telling how old. This data could be very out of date and incorrect.
There are a few things I do to minimize this and there are some things I may do in the future to do it better. For starters if the level of the character I am updating is lower than what I currently have, then I ignore that entry.
What I could do and what kind of sounds like a good bet to me now, is to include a Timestamp that will let me know when the guild data was collected and only use collected guild data that was gotten in say the last 7 days. I could then clear out all members of a guild and rebuild it from the latest guild dump.
I could also aknowledge if someone is an officer or GM of a guild and take their listing as authority, but in all honesty, a GM or officer is just as capable of submitting out of date guild info as well.
So I will probably end up dating the guild data. Which would mean another release, hehe.
I'll keep thinking on it and will hopefully have a good solution soon.
phpbb:phpinfo()
date-stamped
ah. figured that the census submissions were dated. else how does it handle it if I take a census at peak-playing time... say around 8-9p, but don't submit it until I'm done w/ my session, at say 4a?
I sometimes will take 5 censuses at different times of the day before I remember to submit the data. does that have the effect of showing the accumulation of those 5 population instances in one time frame?
time-stamping sounds like a good idea.
I sometimes will take 5 censuses at different times of the day before I remember to submit the data. does that have the effect of showing the accumulation of those 5 population instances in one time frame?
time-stamping sounds like a good idea.
The Census data is timestamped and it is being handled wonderfully now. The guild dump and the census data are maintained separately. I was a little shortsighted and did not incorporate the timestamps into the guild data as well (which I should have). I am leaning toward doing this as I think it will work well.
phpbb:phpinfo()