FVN.li Documentation Help

notifications:queue-game-updates

Finds recently updated games and queues notifications for users who follow them.

Overview

This command identifies games that have been updated recently and creates notification records for users who follow those games. It's the first step in the notification pipeline, detecting update events and preparing notifications for delivery.

Key Features: Update detection, follower matching, notification queuing, duplicate prevention.

Usage

php artisan notifications:queue-game-updates [options]

Options

--days=N

Check for games updated in the last N days (default: 1).

--limit=COUNT

Maximum number of games to process per run (default: 100).

Detection Logic

The command follows this process:

  1. Identifies updated games within the specified time window

  2. Finds users following each updated game

  3. Checks notification preferences for each user

  4. Creates notification records for eligible users

  5. Prevents duplicate notifications for the same update

  6. Reports queuing statistics for monitoring

Examples

php artisan notifications:queue-game-updates

Queues notifications for games updated in the last 24 hours.

php artisan notifications:queue-game-updates --days=7

Processes games updated in the last 7 days (useful after downtime).

php artisan notifications:queue-game-updates --limit=50

Processes only the first 50 updated games.

php artisan notifications:queue-game-updates --days=0.5

Processes games updated in the last 12 hours.

When to Use

Recommended Usage Scenarios

  1. Scheduled execution every few hours for regular notifications

  2. Manual execution after system maintenance or downtime

  3. Backlog processing with extended day ranges

  4. Testing notification flow with specific games

Update Detection

The command detects various types of game updates:

Version Updates

  • New game versions released

  • Updated download files

  • Version metadata changes

Content Updates

  • Description or title changes

  • New screenshots or media

  • Tag or category updates

Status Updates

  • Publication status changes

  • Pricing or availability updates

  • Game jam participation

Follower Matching

Follow Type

Notification Trigger

User Preference

Game Follow

Any game update

Game notifications enabled

Creator Follow

Creator's games updated

Creator notifications enabled

Collection Follow

Collection games updated

Collection notifications enabled

Tag Follow

Tagged games updated

Tag notifications enabled

Notification Preferences

The command respects user notification preferences:

Global Settings

  • Notifications Enabled: Master notification toggle

  • Update Frequency: How often to receive notifications

  • Quiet Hours: Time periods to avoid notifications

Content Filters

  • Update Types: Which types of updates to notify about

  • Game Categories: Specific genres or tags to include/exclude

  • Creator Filters: Specific creators to prioritize or mute

Duplicate Prevention

The system prevents duplicate notifications through:

  • Update Tracking: Records which updates have been processed

  • User Notification History: Tracks what users have been notified about

  • Time Windows: Prevents multiple notifications for the same update

  • Deduplication Logic: Combines similar updates into single notifications

Performance Considerations

  • Database Queries: Optimized queries for update detection

  • Follower Lookups: Efficient matching of users to games

  • Batch Processing: Processes updates in manageable chunks

  • Memory Usage: Handles large follower lists efficiently

Monitoring

Track these metrics during execution:

  • Games Processed: Number of updated games found

  • Notifications Queued: Total notifications created

  • Users Affected: Unique users receiving notifications

  • Processing Time: Time taken to complete queuing

Last modified: 01 June 2025