Critical & Enhancement Issues — Bounty Board

[TrivCodez]

🔧 Issues for Community Bounty

Found multiple bugs & improvements from codebase review. This bounty board is designed to help new contributors gain experience for their interviews and portfolios — there are no monetary payments.

Feel free to claim one and submit a PR!

---

✅ Items Already Complete

• Add !time prefix command to display current time #1 → Fixed deploy-commands.js path (multiple PRs submitted)
• Add /avatar slash command to fetch user avatar #3 → Added folder existence checks (PRs [Reviewed] fix: add folder existence checks (Item 3) #27, [Reviewed] fix: add folder existence checks (Item 3) #33)
• Add error handling for unknown prefix commands #4 → Added client.login() error handler (PRs [Reviewed] fix: add error handler for client.login() rejection (Fixes #4) #26, [Reviewed] fix: handle client login rejection (Item 4) #34)
• Add /userinfo slash command to display user information #6 → Added permission checks to interactionCreate (PR [Reviewed] fix: add robust permission checks to interactionCreate #35)
• Add !coinflip prefix command for random coin toss #7 → Added user-facing error feedback (PR [Reviewed] fix: add robust user-facing error feedback for slash commands #28, merged)
• implemented /userinfo command and fix deployment script (fixes #6) #8 → Added guild vs global command scoping (PR [Reviewed] feat: support guild scoped command deploys #37)
• add time prefix command to display current time #9 → Added dev deploy script (PR feat: add guild deploy script #36)
• Add !8ball prefix command for random fortune-telling #10 → Improved event loader error handling (PR fix: enhance event and command loader error handling #29)

---

🔴 Critical (Still Available)

2. Missing CLIENT_ID in .env.example
File: .env.example
Issue: deploy-commands.js uses CLIENT_ID, but .env.example only includes DISCORD_TOKEN
Fix: add CLIENT_ID= to .env.example

---

🟡 Warnings (Still Available)

5. messageCreate doesn't exclude bot messages
File: src/events/messageCreate.js:7
Issue: bot may reply to itself, causing infinite loops
Fix: early return if message.author.bot

---

Bounty Rules:

• Comment to claim a specific issue number
• One PR per issue
• Follow CONTRIBUTING.md code style
• Test locally before PR

Perfect for building your GitHub profile and interview portfolio! 🎯

[KunalTiwari-git]

Hey! I'd like to claim fixes #1, #2 and #7. Could you assign those them to me?

[TrivCodez]

Hey @KunalTiwari-git! Thanks so much for your interest in contributing!

I appreciate you wanting to claim those issues, but unfortunately #1, #2, and #7 are currently closed and are planned to be reopened in the future when we're ready to address them.

Could you please take a look at the currently open issues instead? We'd love to have you work on something that's actively being tracked.

Thanks again for your enthusiasm to help out!

[TrivCodez]

FYI @KunalTiwari-git - issues #1, #2, and #7 from your earlier comment have already been completed by either myself or another contributor. You can check the closed issues to see the implementations.

Feel free to claim any open issues from this bounty board instead!

[dromero14521]

Claiming issue #1 and submitted PR #25

[dromero14521]

Claiming issue #4 and submitted PR #26

[dromero14521]

Claiming issue #3 and submitted PR #27

[jshaofa-ui]

I'd like to claim this bounty board and fix all the critical + warning issues.

Planned fixes:

1. 🔴 Fix deploy-commands.js path reference (src/commands → src/slashcommands)
2. 🔴 Add CLIENT_ID to .env.example
3. 🟡 Add folder-existence checks with auto-create
4. 🟡 Add .catch() for client.login()
5. 🟡 Add bot message exclusion in messageCreate
6. 🟡 Add permission checks in interactionCreate
7. 🟡 Add user-facing error feedback
8. 🟡 Add guild vs global command scoping support
9. 🟢 Add dev deploy guild script
10. 🟢 Improve event loader error handling

Timeline: 2-3 hours
Approach: Single comprehensive PR with conventional commits

Looking forward to contributing! 🎯