HackerReposA FIELD GUIDE TO OPEN SOURCE
ProSponsor the shelf♧ 0
← Back to top all-time
vjeux
pokemon-showdown-rs
Rust2026–2026
vjeux / pokemon-showdown-rs

pokemon-showdown-rs

Pokemon Showdown Battle System ported to Rust

2Distinct people
3Mentions
0Explicit recommenders
39GitHub stars
REPOSITORY AT A GLANCE

What to know before exploring

What it is

Pokemon Showdown Battle System ported to Rust

GitHub

Where it is used

No documented product use has been verified yet.

What people are saying

No recommendation phrase was found in the indexed comments.

No classified warning is attached to this page. Read the discussions before treating silence as approval.

Also in these discussions

No other repository is repeatedly linked in the same discussions.

This week on Hacker News

Nov 7–Nov 14 UTC · Direct repository links and separately labeled related project stories. Indexed through 11/14/2026, 5:04:57 PM UTC.

No direct repository links were found in the indexed HN discussions over the past seven days. Older discussions are available below.

Mentions over time

HN mentions by hour3 dated mentions

Observed mentions: 2026-01-27 06:53:38 UTC to 2026-01-27 15:18:21 UTC.

012026-01-27 06:00:00 UTC to 2026-01-27 07:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 27, 06:002026-01-27 07:00:00 UTC to 2026-01-27 08:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-27 08:00:00 UTC to 2026-01-27 09:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-27 09:00:00 UTC to 2026-01-27 10:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-27 10:00:00 UTC to 2026-01-27 11:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 commentsJan 27, 10:002026-01-27 11:00:00 UTC to 2026-01-27 12:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-27 12:00:00 UTC to 2026-01-27 13:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-27 13:00:00 UTC to 2026-01-27 14:00:00 UTC (exclusive): 0 mentions; 0 submissions, 0 comments2026-01-27 14:00:00 UTC to 2026-01-27 15:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 comments2026-01-27 15:00:00 UTC to 2026-01-27 16:00:00 UTC (exclusive): 1 mentions; 0 submissions, 1 commentsJan 27, 15:00

Counts come from the repository’s dated source evidence. Index cutoff: 2026-11-02 08:16:59 UTC.

View mention counts and date ranges
UTC ranges include their start and exclude their end. Select a period to filter the source evidence.
PeriodStart (UTC)End (exclusive, UTC)MentionsSubmissionsComments
Jan 27, 06:002026-01-27 06:00:00 UTC2026-01-27 07:00:00 UTC101
Jan 27, 07:002026-01-27 07:00:00 UTC2026-01-27 08:00:00 UTC000
Jan 27, 08:002026-01-27 08:00:00 UTC2026-01-27 09:00:00 UTC000
Jan 27, 09:002026-01-27 09:00:00 UTC2026-01-27 10:00:00 UTC000
Jan 27, 10:002026-01-27 10:00:00 UTC2026-01-27 11:00:00 UTC000
Jan 27, 11:002026-01-27 11:00:00 UTC2026-01-27 12:00:00 UTC000
Jan 27, 12:002026-01-27 12:00:00 UTC2026-01-27 13:00:00 UTC000
Jan 27, 13:002026-01-27 13:00:00 UTC2026-01-27 14:00:00 UTC000
Jan 27, 14:002026-01-27 14:00:00 UTC2026-01-27 15:00:00 UTC101
Jan 27, 15:002026-01-27 15:00:00 UTC2026-01-27 16:00:00 UTC101

What Hacker News says

3 sources
Like a couple of others here I tried checking out this project [1] and running these 2.3 million random battles. The README says everything needs to be run in docker, and indeed the test script uses docker and fails without it, but there are no docker/compose files in the repo. It's great that the repo is provided, but people are clamouring for proof of the extraordinary powers of AI. If the claim is that it allowed 100 kloc to be ported in one month by one dev and the result passes a gazillion tests that prove it actually replicates the desired functionality, that's really interesting! How hard would it be, then, to actually have the repo in a state where people can run those tests? Unless the repo is updated so the tests can be run, my default assumption has to be that the whole thing is broken to the point of uselessness. [1] Link bur
Read the rest
In Porting 100k lines from TypeScript to Rust using Claude Code in a month
Not really. Due to combinatorial explosion some path is hard to hit randomly in this kind of source code. I would have preferred if after 2M random battles the reference implementation had 99% code coverage, than 99% pass rate. I don't know anything about Pokemon, but I briefly looked at the code. "weather" seemed like a self contained thing I could potentially understand. Looking at https://github.com/vjeux/pokemon-showdown-rs/blob/master/src... > NOTE: ignoringAbility() and abilityState.ending not fully implemented So it is almost certain even after 99.96% pass rate, it didn't hit battle with weather suppressing Pokemon but with ability ignored. Code coverage driven testing loop would have found and fixed this one easily.
In Porting 100k lines from TypeScript to Rust using Claude Code in a month

MAKE YOURSELF AT HOME

A few shortcuts

/
Search the collection
?
Open this guide
Esc
Close dialogs and navigation

Your saved repositories and interests stay in this browser.