Badge System-Feature

[janareddyc7]

1. Milestone Badges and Achievements:
   Answer 50 Questions Badge: A badge that users receive after answering 50 questions, showcasing their commitment and engagement. You can create different badges for different milestones (e.g., 100, 500, 1000 questions answered).
   Streak Badges: Users earn badges for consistent activity, such as answering questions for 7 days straight, completing challenges daily for a week, etc.
   Speciality Badges: Based on the type of questions answered, such as “Algorithms Pro,” “Frontend Specialist,” or “Python Enthusiast.” These would be unlocked by answering a certain number of questions in a specific category.
   Challenge Completion Badges: For completing specific coding challenges, users could earn badges that recognize their success, e.g., “Algorithm Master” or “Full Stack Guru” for completing a particular challenge type.
2. Tiered Reward System:
   Bronze, Silver, Gold Tiers: Reward users with tier-based achievements. For example:
   Bronze: Answer 50 questions, complete 5 challenges.
   Silver: Answer 200 questions, achieve a 10-day streak.
   Gold: Answer 500 questions, win a monthly competition, or complete 50 challenges.

I can implement this

[Logannford]

@janareddyc7 these are great ideas! We have thought about implementing this here: #260

Is this something you'd like to see in the near future? I can start developing this very soon if that's the case? I would need to scope out schema changes, different levels etc so I am happy to have some conversations with you on what you feel would be the best way to do this 😄

[janareddyc7]

i wanted to add it in the schema then create a model badge and then pass it out and then creating a seed.js for it and then creating a api endpoint followed by frontend logic

[janareddyc7]

model Badge {
id Int @id @default(autoincrement())
name String
description String
type String // e.g., "Milestone", "Streak",
iconUrl String
}
this could be possible

[janareddyc7]

do you want to add schema changes

[Logannford]

@janareddyc7 that's a good shout - maybe we could use server actions over API endpoints?

also that schema looks great - maybe we could change it slightly to match the current style guide:

model Badge {
    uid             String   @id @default(uuid())
    createdAt       DateTime @default(now())
    updatedAt       DateTime @updatedAt
    name String
    description String
    type String // e.g., "Milestone", "Streak",
    iconUrl String
}

I suppose we should also be adding relations to the user? this way if we ever need to filter the leaderboard page by badge in the future it would be really simple? 🤔

[Logannford]

do you want to add schema changes

yeah sure thing, let me change those and I will let you know once they've been done!

[janareddyc7]

sure

[janareddyc7]

model Achievement {
id Int @id @default(autoincrement())
userId Int
badgeId Int
unlockedAt DateTime @default(now())

user User @relation(fields: [userId], references: [id])
badge Badge @relation(fields: [badgeId], references: [id])
} so this could be backbone for achivement and for the bade

const badges = [
{ name: 'Answer 50 Questions', description: 'Milestone badge for answering 50 questions', type: 'Milestone', iconUrl: '/icons/50-questions.png' },
{ name: '7-Day Streak', description: 'Answer questions 7 days in a row', type: 'Streak', iconUrl: '/icons/7-day-streak.png' },
{ name: 'Algorithms Pro', description: 'Answer 50 algorithm-related questions', type: 'Specialty', iconUrl: '/icons/algorithms-pro.png' },
// Add more badges here
]; i think this good be good in a seed.js

[Logannford]

what do you think of this?

enum BadgeType {
    STREAK
    QUESTION_ANSWERED
    QUESTION_CORRECT
    TIME_TAKEN
    LEADERBOARD_POSITION
}

model Badge {
    uid String @id @default(uuid())
    createdAt DateTime @default(now())
    updatedAt DateTime @updatedAt

    name String
    description String

    imageUrl String

    type BadgeType

    // what the user needs to do to earn the badge
    requirements String

    // the achievements that have been earned for this badge
    achievements Achievement[]
}

model Achievement {
    uid String @id @default(uuid())
    createdAt DateTime @default(now())
    updatedAt DateTime @updatedAt

    badgeUid String
    badge Badge @relation(fields: [badgeUid], references: [uid], onDelete: Cascade, onUpdate: Cascade)

    // the user who earned the badge
    userUid String
    user Users @relation(fields: [userUid], references: [uid], onDelete: Cascade, onUpdate: Cascade)

   unlockedAt DateTime
}

model Users {
  // existing fields 

  // the user's achievements
  achievements Achievement[]
}

[janareddyc7]

umm LEADERBOARD_POSITION could be tied to specific times or dynamic data. probably

enum BadgeType {
STREAK
QUESTION_ANSWERED
QUESTION_CORRECT
TIME_TAKEN
LEADERBOARD_POSITION
}

model Badge {
uid String @id @default(uuid())
createdAt DateTime @default(now())
updatedAt DateTime @updatedat

name String
description String
imageUrl String
type BadgeType

requirements Json // store as json

achievements Achievement[]
}

model Achievement {
uid String @id @default(uuid())
createdAt DateTime @default(now())
updatedAt DateTime @updatedat

badgeUid String
badge Badge @relation(fields: [badgeUid], references: [uid], onDelete: Cascade, onUpdate: Cascade)

userUid String
user Users @relation(fields: [userUid], references: [uid], onDelete: Cascade, onUpdate: Cascade)

unlockedAt DateTime
status String // Example: 'active', 'completed'
progress Int // Track progress towards completion
}

model Users {
uid String @id @default(uuid())
name String
email String @unique
password String

achievements Achievement[] // User's earned achievements
}
this

[Logannford]

that looks perfect @janareddyc7 . Let me get that in, run a migration on it and get it merged!