- RPG
- Simulation
- Strategy
Game
明末：甲申年
Versions, Steam Workshops and mod compatibility for 明末：甲申年.
Set during the fall of the Ming dynasty in 1644, this historical grand-strategy narrative game lets you rule as the Chongzhen Emperor, fight for the Shun regime, lead another faction, or survive as a commoner. Govern, wage war, manage resources, and reshape history through AI-assisted court debates.
Browse everything
Sorted, filterable and paged. Every link goes to the author’s own download.
From the developers
Official announcements, newest first. Posted on Steam.
- Community AnnouncementsMing: 1644 Dev Diary #2 — New Year's Day, Before the Outcome{STEAM_CLAN_IMAGE}/46150446/c02ee20f1aecbce0488a569863f287a83572a622.png If we begin with what happened later, the Jiashen year is easy to turn into a countdown: In the third lunar month, Li Zicheng entered Beijing. The Chongzhen Emperor died on Coal Hill. The situation at Shanhai Pass then changed abruptly, Qing forces entered the pass, one dynasty fell, and another long war began. But Ming: 1...
- Community AnnouncementsDevelopment Diary #1: The Map Is Not a BackgroundTo begin with the conclusion: in the remake of Ming Mo: The Jiashen Year, the map is not an image placed behind the interface. It must answer not only “what is this land called?” but also “who claims it, who actually controls it, can an army pass through it, can supplies reach it, and how much does the player truly know about it?” After introducing our grand-strategy vision in Dev Diary #0, we...
- Community AnnouncementsMing: The Jiashen Year — Developer Diary #0: Our Grand Strategy VisionAll remake screenshots in this post were captured from the current Godot build and are marked “WORK IN PROGRESS.” The interface, values, map, and art do not represent final quality. Legacy-build footage and concept art are labeled separately. Hello, and welcome to Developer Diary #0 for Ming: The Jiashen Year. We want to begin by making one thing clear: this is not a new map and a few extra scr...
- Community Announcements0.4.3-1 Update NoticeThis update focuses on improving the "Ministerial Consultation" and "Military Execution" systems to ensure consistency with the map, while also introducing the first batch of "Transmigrator System" entertainment features. Details regarding troop counts, garrison locations, military pay, and mission progress provided by ministers will now be cross-referenced against the current game session's ac...
- Mods indexed
- 5
- Versions
- 0
- Newest tracked
- none yet
- Most disruptive update
- No breakage data for this game
of 13 on Steam Workshop
Most downloaded
Measured from the source's own counts, summed across every release.
- 崇祯中兴·天启七年时局：阉党余威未消，辽东胜后真空，陕北饥民初乱，国库虽充而积弊如山。84 downloads
- 三国 · 赤壁前夕建安十三年冬，曹操南下、孙刘结盟，天下分合决于赤壁一火。78 downloads
- 南明·弘光立国时局：崇祯十七年三月，北京陷落，崇祯自缢煤山；吴三桂引清军入关占据华北，李自成退守陕西，张献忠割据四川。五月福王朱由崧于南京登基，改元弘光，坐拥江南财赋与长江天险，朝堂东林、阉党党争不休，江北四镇拥兵自重，左良玉雄踞武昌，八旗虎视江南，大明半壁危在旦夕。38 downloads
- 沧澜仙纪 · 宗门争霸时局：沧澜灵脉千年来首次大复苏 · 正道六宗与魔门三派争夺灵脉源头 · 蛰伏万年的太古妖封印将破33 downloads
- 烽火太平年·崇祯流亡时局：北京沦陷，英葡联军踞京索降，皇帝南狩凤阳，天下震恐。 崇祯携皇后及太子南下南京拜谒孝陵，意在祈福太平。车驾刚到凤阳，八百里急报传来：英吉利与葡萄牙联合舰队突袭天津，登陆后与内应配合，已攻破北京城。洋人扬言：“大明若不降服，则焚毁紫禁城，另立新君。”18 downloads
More rpg games see all
Why 明末：甲申年 mods break
A mod is compiled against one version of a game. When the game updates, anything that reached into the parts that moved stops working, and it usually stops working silently rather than with a message that explains itself.
That is what the table above counts. It is not a guess: each row is a mod the community has reported as broken by that specific release. The number is a fair measure of how disruptive an update was, and it is the reason people delay updating a game they have modded heavily.
Common questions
Does IndexGG host 明末：甲申年 mods?
No, and it never will. Every download link points at the author's own page on Nexus, GitHub, CurseForge or wherever they published it. We index the ecosystem; the files stay with the people who made them.
Where does the compatibility data come from?
From the communities that maintain it in the open, not from guesswork. Each claim carries how it is known, so a reported breakage is never presented as though the author said it.
Why is a mod listed as broken when it works for me?
Compatibility depends on your exact game version and the rest of your load order. A mod marked as broken in one release may work fine on an older one, which is exactly why the version is recorded next to the claim rather than a bare yes or no.