ModOrganizer2/modorganizer

Mod manager for various PC games. Discord Server: https://discord.gg/ewUVAqyrQX if you would like to be more involved

View on GitHub ↗Jump to charts ↓Open shareable report →

ModOrganizer2/modorganizer has 3k+ stars and 200+ forks on GitHub, is written in C++, and was last pushed on Oct 5, 2026. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 22nd, 2026
Created on November 13th, 2016
Open Issues & Pull Requests: 676 (+0)
GitHub issues: Enabled
Number of forks: 229
Total Stargazers: 3,126 (+0)
Total Subscribers: 91 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 19.1 hours
Mean response time: 101.6 days
90th percentile: 262.2 days
Tracked items: 220

Maintainer activity

2 people did triage or write work on this repository in the last 12 months.

Counts unlabeled, assigned, unassigned, milestoned, demilestoned, locked, unlocked over the last 12 months. These are issue and pull request events that require triage or write permission. Commits and code review are not counted. labeled and renamed are excluded because GitHub issue forms record the issue author as the actor. Figures from October 18, 2026. This count is not comparable across projects: each project's automation decides which of these events a person emits. How this is counted.

How this project is maintained

Roughly one issue in three opened in the past year never receives a reply. 99% of open issues come from outside the core team, so the backlog reflects real-world use rather than internal planning. Work labelled "issue report" is answered fastest, typically in about 19 hours, while "area: mo2 game plugins" waits about 4 weeks. 73% of tracked open issues have had no activity in three months, so the open count overstates what is actively being worked. Only 20% of issues opened in the past year have been closed.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 209
New in 7 days: 1
Closed in 7 days: 0
Avg open age: 587 days
Stale 30+ days: 199
Stale 90+ days: 182

Recent activity

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

Top labels

  • issue report (184)
  • Feature Request (71)
  • area: mo2 game plugins (11)
  • Dev Ticket (7)
  • additional games support (7)
  • area: modlist (5)
  • bug (5)
  • fixed in next release (5)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Mod Organizer 2 is a mod manager for PC games that handles installation, organization, and conflict resolution for game modifications across multiple titles.

The tool addresses the complexity of managing large numbers of mods by providing a virtual file system approach that keeps the original game directory untouched while allowing mods to be installed, enabled, disabled, and reordered without physical file manipulation. This architecture prevents mod conflicts from corrupting the base game and makes it straightforward to test different mod combinations or revert changes. The manager tracks mod dependencies, load orders, and file conflicts, presenting this information to users so they can make informed decisions about which mods to activate.

Mod Organizer 2 suits players who maintain extensive mod collections and need fine-grained control over load order and conflict resolution. It is particularly valuable for games with complex modding ecosystems where dozens or hundreds of mods might interact. The virtual file system design distinguishes it from simpler mod managers by eliminating the need to manually restore game files when testing different configurations or uninstalling mods.

Development on the project shows consistent activity with regular commits addressing bug fixes and feature improvements. The codebase receives ongoing maintenance focused on stability and compatibility with game updates. Community engagement is active through the project's Discord server, where users and contributors collaborate on issues and discuss development direction. The project accepts contributions from the community and maintains responsiveness to reported problems.