fix: register cooldown correctly (#304)

Co-authored-by: Jeroen Claassens <support@favware.tech>

src/lib/structures/Command.ts

@@ -231,18 +231,21 @@ export abstract class Command<T = Args, O extends CommandOptions = CommandOption
 	 * @param options The command options given from the constructor.
 	 */
 	protected parseConstructorPreConditionsCooldown(options: CommandOptions) {
-		const { cooldownLimit, cooldownDelay, cooldownScope, cooldownFilteredUsers } = options;
 		const { defaultCooldown } = this.container.client.options;
 
-		if ((defaultCooldown && !defaultCooldown.filteredCommands?.includes(this.name)) || (cooldownLimit && cooldownDelay)) {
+		// We will check for whether the command is filtered from the defaults, but we will allow overridden values to
+		// be set. If an overridden value is passed, it will have priority. Otherwise it will default to 0 if filtered
+		// (causing the precondition to not be registered) or the default value with a fallback to a single-use cooldown.
+		const filtered = defaultCooldown?.filteredCommands?.includes(this.name) ?? false;
+		const limit = options.cooldownLimit ?? (filtered ? 0 : defaultCooldown!.limit ?? 1);
+		const delay = options.cooldownDelay ?? (filtered ? 0 : defaultCooldown!.delay ?? 0);
+
+		if (limit && delay) {
+			const scope = options.cooldownScope ?? defaultCooldown?.scope ?? BucketScope.User;
+			const filteredUsers = options.cooldownFilteredUsers ?? defaultCooldown?.filteredUsers;
 			this.preconditions.append({
 				name: CommandPreConditions.Cooldown,
-				context: {
-					scope: cooldownScope ?? defaultCooldown?.scope ?? BucketScope.User,
-					limit: cooldownLimit ?? defaultCooldown?.limit ?? 1,
-					delay: cooldownDelay ?? defaultCooldown?.delay ?? 0,
-					filteredUsers: cooldownFilteredUsers ?? defaultCooldown?.filteredUsers
-				}
+				context: { scope, limit, delay, filteredUsers }
 			});
 		}
 	}