smogon/pokemon-showdown

Pokémon battle simulator.

View on GitHub ↗Jump to charts ↓

Summary Information

Updated 6 minutes ago
Added to GitGenius on September 11th, 2026
Created on December 23rd, 2011
Open Issues & Pull Requests: 328 (+0)
GitHub issues: Enabled
Number of forks: 3,519
Total Stargazers: 5,888 (+0)
Total Subscribers: 169 (+0)

Repository Insights (GitGenius)

Most active contributors

Sign in to see contributor activity.

Related repositories by overlapping contributors

No overlapping-contributor repos identified yet.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 52
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,087 days
Stale 30+ days: 48
Stale 90+ days: 48

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • bug (29)
  • enhancement (16)
  • client (15)
  • mechanics: approved (11)
  • pastgens (4)
  • invalid (3)
  • application (2)
  • good first issue (2)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Pokémon Showdown is a battle simulator that provides a website for Pokémon battling, a JavaScript library for simulating battles and accessing Pokédex data, command-line tools, a web API, and a game server for hosting custom communities.

The tool simulates singles, doubles, and triples battles across all nine generations of Pokémon games. It solves the problem of needing an accessible, programmable way to run Pokémon battles without requiring the official games. The simulator handles the complex mechanics of each generation and exposes this functionality through multiple interfaces: a playable website, a JavaScript library for developers, command-line utilities for non-JavaScript programs, and a server that communities can self-host with custom game modes.

Pokémon Showdown suits developers building bots, battle analysis tools, or custom Pokémon communities. The project provides substantial documentation including protocol specifications, architecture overviews, and a bot FAQ to help new developers understand how to integrate with or extend the simulator. Self-hosting the server is straightforward for those wanting to run their own instance rather than using the public website.

The project maintains active engagement with its user base, with nearly all open issues coming from outside users rather than the core team, demonstrating substantial real-world adoption. Maintainers typically respond to new issues and pull requests within a day. Work in the issue tracker centers on bug fixes, enhancements, and client-related improvements.