FSOC-OSS/Fsoc-level-hard

🔥 Feature Request: Implement Streak System with Bonus Rewards and Animations

Open

#10 opened on Sep 30, 2025

View on GitHubContributor guide
 (1 comment) (0 reactions) (0 assignees)JavaScript (21 forks)auto 404
MediumPriority lowenhancementgood first issuehacktoberfest

Repository metrics

Stars
 (1 star)
PR merge metrics
 (PR metrics pending)

Description

Design Reference

Reference design showing streak counter, fire animations, and bonus point displays

Problem Statement

The current quiz lacks motivation for consistent performance. Users need visual feedback and rewards for maintaining consecutive correct answers to encourage focused play and create engaging momentum.

Proposed Solution

Implement a comprehensive streak system that:

  • Tracks consecutive correct answers in real-time
  • Displays streak counter with visual effects
  • Awards bonus points for streak milestones
  • Shows celebratory animations for streak achievements
  • Provides streak preservation incentives

Acceptance Criteria

✅ Streak Tracking & Display

  • Streak preservation across questions in same quiz
  • Visual streak indicator (fire icons, progress bars)
  • Streak multiplier display for bonus points
  • Streak history in results page

✅ Bonus Rewards System

  • Bonus points for streak milestones (5, 10, 15, 20+ correct answers)
  • Increasing multipliers (1.5x at 5, 2x at 10, etc.)
  • Special rewards for extended streaks (25, 50, 100)
  • Streak bonus calculation in final score
  • Bonus point animations and notifications

Contributor guide

Research direction
Examine the existing quiz codebase to understand how answers are evaluated and scores calculated. Implement a streak counter that increments on consecutive correct answers and resets on wrong answers. Add a visual streak indicator with fire icons and animations. Implement bonus points for milestone streaks and display them. Use state management to persist streak across questions.
Tech stack
javascript
Domain
frontend
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
JavaScript
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75