Core projects
Each tool handles one job well: streamlining gameplay, customizing the look, or running sessions at scale.
Auto-Answer Script
Automates question responses in Blooket games. Useful for testing game logic, building automation workflows, or running unattended sessions.
Gold & XP Booster Tool
Accelerates in-game progress by adjusting earned resources. Lets players test higher-level features or compress learning arcs in sandbox play.
Custom Theme & Skin Packs
Swaps colors, fonts, and visual elements. Players and streamers rebrand their Blooket sessions to match their own branding or aesthetic.
Classroom Automation Helper
Streamlines running Blooket sessions for groups. Teachers automate roster setup, question order, and session pacing—cuts manual overhead.
Behind the build: The Auto-Answer Script
Walk through how we approached one of our core tools.
When a teacher or streamer runs a Blooket session, they often need to test the game state, validate logic, or run multiple rounds without manual input. The Auto-Answer Script solves that by intercepting game events and filling in player responses programmatically.
The problem: Running a live Blooket session by hand takes time. Testing new questions or session configs meant sitting through each round. Automating it meant writing custom code for each variant.
Our approach: We built a lightweight script that hooks into Blooket's event system and watches for question prompts. When a question fires, the script selects an answer based on rules you define—hardcoded, random, or following a pattern. The session runs at normal speed; the script just removes the wait.
Testing and refinement: We tested it across different question types (multiple choice, true/false, typing) and session sizes (small group, full classroom). We found that async event handling broke in some edge cases, so we rewrote the queue system. Users reported timing issues when Blooket's server was slow, so we added fallback delays and a manual trigger mode.
The result: A tool that runs unattended sessions reliably, lets teachers validate their questions before students see them, and saves streamers from repetitive clicking during test broadcasts.
From idea to delivery
Every commissioned hack follows the same process.
Brief
We listen. What's the problem? What does success look like? Do you have existing code we need to integrate? We nail down the scope here.
Build
We write the code. We choose tools that match the job: vanilla JavaScript for browser injection, Node if you need a backend runner, or a browser extension for persistent tweaks.
Test
We run it. Does it work on your setup? Edge cases? Blooket updates? We test live and iterate based on what we find.
Deliver
You get working code: a script file, an extension package, or a runner app. Instructions on how to use it. Support if bugs surface after launch.
Want something like this built for you?
Tell us what you need. We'll scope it, quote it, and build it.