Api: Clan joinDate variable is not accurate.

Created on 28 Nov 2019  ·  7Comments  ·  Source: Bungie-net/api

When looking at the members listing of /Platform/GroupV2/{ groupId }/Members/ the joinDate variable associated with each member is incorrect. This variable logs the time a member was invited and not the time a member has accepted and joined. As i understand with clans invited players count towards the 100 member limit, so i assume that the invite date from that data is carried over when i played joins. I was wondering if this could be changed as i require accurate data for a project i am working on.

I have a node js bot that scans these groups and checks for differences between 2 custom made files to determine if variables in those have changed and if so it will output a broadcast to a discord server. But i have an issue where it spams if a player joins a clan because obviously there is new data. The way i have tried to prevent this is by checking if the player has joined the clan in the last 15 minutes, but with the way the join date variable logs this causes issues for people who do not accept the invitation straight away.

image

If this is not something that can be fixed easy and requires too much work i have another way around by checking the see if their name was in the previous file and if not then don't broadcast, this may however cause more issues so having this variable changed to be accurate would be awesome if possible!

Thanks as always!

bug bug filed investigation

All 7 comments

What data from the player record are you using to determine the time stamp for “has achieved the title”?

So when i grab the players data is compares it against the players old data which at the moment is only 1 minute 40 seconds old. So when it checks the record variable for lets say wayfarer, the completion value will be false in the old file and the new file will have the completion value as true. Therefor that player has obtained the wayfarer title in the last 1 minute 40 seconds. Then the bot will send a broadcast to that players clan discord.

So there is no timestamp for the record itself but it can be pretty accurate. But as you can tell if the old file does not contain data for that player and the new file contains a true completion value for wayfarer, it will announce it. To prevent this i check against that players joinDate in the clan file to determine if they've just joined the clan or not which would have been a great way to prevent spam but it's not accurate.

To avoid this problem for now i've added a check to catch if the player has achieved more than 2 titles or 6 items in that 1 minute 40 seconds and if so prevent announcement.

image

But this is a terrible way to work around this as what if a clan finished up their enlightenment title together that would be 6 titles in that 1 minute 40 seconds and would not be announced. Also people who only have 1 title still announce when they join as it is not caught.

I'll file a bug on this, thank you!

TFS 854485

I know it's a big ask but could you let me know if this gets fixed, It's quite hard to test / check for.

I will let you know when I hear more on it - unfortunately, I've got no update so far.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

dcaslin picture dcaslin  ·  3Comments

gitFurious picture gitFurious  ·  3Comments

Bizow picture Bizow  ·  4Comments

queuebit picture queuebit  ·  3Comments

andyschott picture andyschott  ·  3Comments