Riven OCR

A Chrome extension that eliminates the tedious manual work of listing Riven mods by extracting stats from screenshots and auto-filling warframe.market forms.

Background (Why)

While building Riven Tracker, I watched my roommate painstakingly list his Riven mods on warframe.market. Every single listing required manually filling out at least 13 fields—and all that information was already sitting right there on the Riven screenshot. It was the definition of repetitive, soul-crushing work.

I remembered a conversation I’d had with AI earlier: “Look for tasks that are tedious and repetitive.” This was it. The moment I saw him doing it, I knew I had to build an automation tool for this.

What I Built (What)

I built a full-stack Chrome extension to automate the entire Riven listing workflow.

• Frontend: A Chrome extension that integrates directly into the warframe.market website.
  • Repository: riven-ocr-extension
• Backend: A Python-based OCR service that extracts text from Riven screenshots and parses the game-specific data format.
  • Repository: Riven-OCR
• Two Versions: I built both Chinese and English versions to serve different communities.
  • Chinese Backend: Deployed on Tencent Cloud Lighthouse (¥79/year).
  • English Backend: Deployed on Vultr ($40/month).

The workflow was simple: paste a Riven screenshot, let the OCR backend extract the stats, and watch the form fill itself.

Outcome (Result)

The Chinese version caught a wave.

Bilibili Success: A classmate helped me promote it, and the demo video got 10,000+ views and hundreds of likes. Early Adoption Problem: The Chrome Web Store version was ready, but the Edge extension was still under review. Since most Chinese users can’t access the Chrome Web Store, I distributed the extension manually as a .zip file. In just 5 days, it was downloaded 300 times. Chrome Web Store: Once approved, the Chinese version quickly gained 50+ users.

Seeing this traction, I decided to go international.

I overhauled the UI/UX, added a Ko-fi donation link, and adapted the backend for English. On January 25, 2026, I posted to Reddit’s r/WarframeRivens community (8K members).

Cultural Insight: I discovered that the larger Warframe subreddit (900K members) is actually pretty anti-Riven. Most players see Rivens as a needless grind. In contrast, the Chinese community embraces Rivens much more enthusiastically. When I posted in the main subreddit, I got more downvotes than upvotes. But in r/WarframeRivens, the reception was warm.

Positive Feedback: As of January 28, 2026, the Reddit post had 60 upvotes and thousands of views.

Chrome Web Store (EN): Only 9 users so far, but already two 5-star reviews. That felt really good.

Key Takeaways

This project taught me a lot about iteration, localization, and cost management.

Shipping Fast: I went from idea to launch in less than three weeks. Building the Chinese version first let me validate the concept before investing in the international version.

OCR Complexity: Parsing Warframe’s unique stat format (with abbreviations, symbols, and variable layouts) was harder than I expected. I spent a lot of time fine-tuning the OCR accuracy and handling edge cases.

Distribution Challenges: Edge Web Store approval can be slow, and Chinese users face real barriers to installing extensions. Manual distribution worked, but it’s not sustainable.

Localization ≠ Translation: The Chinese and English communities have completely different attitudes toward Rivens. What works on Bilibili doesn’t work on Reddit, and vice versa.

Cost Reality Check (and Long-term Thinking): At first glance, the Vultr server at $40/month seems too expensive for a passion project with only 9 users. But I’m learning to think beyond immediate ROI. The OCR service itself is lightweight—it barely scratches the server’s capacity. This means the infrastructure is already there for future projects. If I build another tool that needs server-side processing (image manipulation, API proxying, data crunching), I won’t need to spin up a new server. In a way, I’m paying $40/month not just for Riven OCR, but for a general-purpose backend foundation. It’s less of a sunk cost and more of an investment in future optionality.

Current Status

• Status: Frozen
• The Chinese version will keep running (cheap server, stable user base). The English version’s Vultr server will stay online for now—not just for Riven OCR, but as shared infrastructure for future experiments. The OCR service uses minimal resources, so the server has plenty of headroom for whatever comes next.
• I won’t be adding new features to Riven OCR itself, but the tool works as-is and solves the problem it was built to solve.
• If you’re building automation tools for niche gaming communities, I’d recommend starting with a single language/region, validating demand, and thinking carefully about whether server costs can be amortized across multiple projects.