[YabbaDabba]

BUGS?

1 - Please move all the phrases into the Phrase library

2 - Fix the custom phrase bugs
I ended up having to edit the XML file to change phrases there.

3 - Have Report threads indexed in search properly
I have reports sent to a dedicated Mod-only forum with "Index New Posts in Search Engine" set to Y. Usernames are not found when searching this dedicated forum unless I go into admincp and reindex.

4 - Have report threads update the post counts properly
The Bot that generates these threads always has a "0" post count.

5 - Some unintended interaction between PM and thread generation
Had both PM and thread generation set to Y. Everything worked fine for weeks. Changed PM option to N. Threads no longer generated. This was reported as a problem on the AED for 3.5 thread also.


RECOMMEND ADDING A USE TIP TO YOUR ADMIN POST:
1 - Set up a bot account to be the author of any AED threads and PMs.
This will save people a lot of grief as otherwise the admin IP shows up associated with all the overlapping accounts.


POSSIBLE ENHANCEMENTS

1 - Skip user overlaps that have been previously reported
I realize that detecting this on the user's machine is unreliable for cookies, especially if the perp is using different computers and what not. Perhaps AED can detect if an identical post in an existing thread already exists? Or by comparing the userID's in the cookie to a logfile of past matches on the server?

2 - Automatically change new overlapping user's group assignment based on prior account's group
E.g., move new account "B" into usergroup "3" if earlier account "A" is in usergroup "2" (e.g., if member account A is in a "banned" group).

3 - Option to flush cookies
Or possibly an option to change the cookie domain; or add a trigger date to the cookie.
If a forum resets userID's, this plugin becomes worse than useless.

4 - Option to add current IP's to PM/thread for reported overlaps.

5 - Option to force acceptance of cookie
As pointed out by another user on the AED 3.5 thread, troublemakers with 1/2 a brain can get around this utility. Forcing cookie use (an option to deny access if cookie not present/written and/or detecting matching accounts against the logfile) would not affect most members at all.

6 - Create username variables for all cases
It would be nice to have variables for each reported username in both linked and unlinked states as well as for "all" user names.