[Reviewed] feat: Add cooldown tracking with Collection (Item 5) - NEEDS REVISION

[messiawrq-spec]

Claims and resolves Item #5 from Issue #40.

Added a comprehensive cooldown manager directly inside interactionCreate.js. It utilizes standard Discord.js Collection objects to track users per-command, honoring custom command.cooldown parameters and protecting against spam.

[TrivCodez]

Summary

Adds in-memory cooldown tracking with Discord.js Collection for per-command rate limiting.

🔴 Critical Issues

File	Line	Severity	Issue	Fix
src/events/interactionCreate.js	4-26	CRITICAL	Duplicate cooldown logic - This PR implements cooldown directly but the file already imports and uses checkCooldown/setCooldown from ../utils/cooldown	Remove lines 14-33 entirely - the existing checkCooldown call at line 35 already handles this

🟡 Warnings

File	Line	Severity	Issue	Fix
src/events/interactionCreate.js	4-5	High	Imports Collection and creates cooldowns but duplicates existing utility	Delete import and use existing cooldown module
src/events/interactionCreate.js	20	Medium	Hardcoded defaultCooldownDuration = 3 - magic number	Move to config or command-level setting
src/events/interactionCreate.js	37	Low	Cooldown check happens AFTER this implementation runs (line 35) causing redundant logic	Remove duplicate implementation

Analysis

This PR creates conflicting cooldown implementations:

1. Lines 14-33: New in-memory cooldown with Collection
2. Line 35: Calls existing checkCooldown() from utility module

Problem: Both will run, potentially causing:

• Double cooldown enforcement
• Memory leak (Collection grows unbounded)
• Confusing behavior for command authors

🟢 Suggestions

Option 1 (Recommended): Remove this PR entirely - existing cooldown.js handles it
Option 2: Replace cooldown.js with this implementation if Collection-based approach is preferred
Option 3: Merge both approaches - use Collection for storage but keep utility functions for logic

✅ Good

• Clean Discord timestamp format for remaining time
• Proper cleanup with setTimeout
• Per-command customization support

Needs revision - Must resolve duplicate cooldown logic before merging. Recommend removing lines 14-33 and keeping existing checkCooldown/setCooldown calls.