XF-Addon FraudClient - Report Spam 1.0.4

New Features:*
Automatic Registration Check:
The addon will now automatically check new users against the FraudClient database during registration. If a report is found for the user's email or username, their account will be placed into the "Awaiting approval" queue, preventing them from accessing the forum until a staff member reviews them. This is a powerful tool to proactively stop known spammers and fraudsters.*

Manual User Check:
A "Check FraudClient" button has been added to user profiles. Staff members with the appropriate permission can now manually check any user against the FraudClient database at any time.

Bug Fixes & Improvements:*
Fixed:
Resolved an issue where the report date and time were displaying incorrectly (showing "Dec 31, 1969"). The date and time are now correctly handled and displayed in your forum's local timezone.*

Fixed:
Corrected a "Call to undefined method" error that could occur during registration.

We're excited to announce a significant update to the FraudClient - ReportSpam addon, bringing powerful new features to help you combat spam and fraud more effectively.

The headline feature of this release is automatic checking of new users during registration. When a user signs up, the addon will instantly check their username and email against the FraudClient database. If any existing reports are found, the user's account will automatically be placed into the moderation queue for your review. This is a game-changer for proactively stopping known bad actors before they can cause any trouble on your forum.

We've also added a new "Check FraudClient" button directly on user profiles. If you're ever suspicious of a user, staff members with the correct permission can now perform a manual check with a single click to see if any reports exist for that user in the FraudClient database.

This release also includes a few important fixes, most notably a fix for an issue that caused incorrect report dates (the dreaded "1969" bug). All dates and times are now handled correctly.