kalilistic / PlayerTrack

Keep track of players you meet.
MIT License
16 stars 9 forks source link

Only players from dungeons/raids/etc #148

Open JinxLuckless opened 6 months ago

JinxLuckless commented 6 months ago

This could turn out to be me not understanding the settings, but I can't seem to get it to only track players that I did a dungeon or other instanced content with.

For 'Overworld' I have both settings unchecked. For 'Content' I even tried unchecking 'Add Players'. And then for 'High End Content' I left both checked. Despite this, when I go to Limsa, it starts tracking anyone in Limsa, not just people I did an instance with. For social lists, I only clicked those on my Friends List and Free Company, and didn't click 'Sync with Dynamic Category' in either case, if that matters.

I purged the entire list while idling in Limsa, and already have 46 new names on the list. Is this intended, (and if so, my feature request is to have an option to only track players I did instanced content with), or could it be a bug?

kalilistic commented 6 months ago

The intended functionality is it still shows these players in Limsa, etc - it just doesn't add new ones. You mention 46 new names though so maybe that's not what you're seeing. I'll try to replicate this next time I'm working on the plugin - I haven't seen this myself.

JinxLuckless commented 6 months ago

Mainly I'm just not wanting new names to be added from non-instanced content. I purged all names on my list while standing in Limsa to be sure, and then got 46 new entries while I idled there for awhile.

So the intended functionality is more like, if I did an instance earlier with someone who's now in Limsa, when I head to Limsa it might notify me that they're nearby if I have that checked, right? That definitely makes sense and is what I was hoping for.

Currently instead, it's adding the names of anyone nearby in Limsa/wherever, whether I have met them before or done any instances with them. I think I have my settings set correctly.

Thanks for the help. Hopefully we'll figure this out-- whether it's a bug or me just misunderstanding a setting.