Menu
烈山海一(BMS1)
  • Action
  • Adventure
  • Indie
  • RPG

Game

烈山海一(BMS1)

《烈山海》是一款以中国神话为背景的RPG游戏,玩家在游戏中将扮演一位身负奇异命运的穿越者,在机缘巧合之下来到山海境,与神农、夸父、精卫等经典神话人物相遇,一边改写他们的命运,一边完成自己的冒险……

《烈山海》是一款以中国神话为背景的RPG游戏,内容精彩让人欲罢不能!

烈山海一(BMS1) screenshot 1 of 61 / 6

About 烈山海一(BMS1)

Released
October 2020
Engine
Unity
Platforms
PC (Microsoft Windows)

Where to get it

Release, studio and platform data from IGDB. Store links go to the sellers, not to us. We do not sell games and we do not host files.

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.

Mods indexed
15

of 26 on Steam Workshop

Versions
0
Newest tracked
none yet
Most disruptive update
No breakage data for this game

Most downloaded

Measured from the source's own counts, summed across every release.

More rpg games see all

Why 烈山海一(BMS1) 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 烈山海一(BMS1) 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.