silksong-coop-mod 0.4.0

package/INSTALL.bat

@@ -0,0 +1,16 @@
+@echo off
+chcp 65001 >nul 2>&1
+title Silksong co-op (SSMP) installer
+
+rem Runs the real installer next to this file. -ExecutionPolicy Bypass applies to this one run only and changes
+rem nothing on the machine. pwsh is preferred when present, because it handles text encoding better.
+
+where pwsh >nul 2>&1
+if %errorlevel%==0 (
+    pwsh -NoProfile -ExecutionPolicy Bypass -File "%~dp0install.ps1"
+) else (
+    powershell -NoProfile -ExecutionPolicy Bypass -File "%~dp0install.ps1"
+)
+
+echo.
+pause

package/INSTALL.txt

@@ -0,0 +1,258 @@
+丝之歌联机模组（SSMP 自制版）——一键安装
+==========================================
+
+这是 SSMP 联机模组的一个自制版本，比公开版多了「双人存档」：
+两个人共用一条流程，任务、世界变化、剧情道具会互相同步。
+
+重要：两个人必须装【同一份】这个压缩包，不能一个人用公开版。
+
+     【从这一版开始，版本不一致会被直接拦住。】
+     加入房间时会比对双方的版本，不一样就不让连，并且明确告诉你
+     「你们装的版本不同」，而不是连上之后表现出一堆对不上的怪事。
+
+     ※ 代价是：这一版【不认识任何旧版本】。
+       所以【两个人必须一起换成这一版】，只有一个人装的话，
+       你们会连不上——这是正常的，不是坏了。
+       这笔账只付一次，以后就不会再有「一个人更了一个人没更」还不知情的情况。
+
+     （顺带更正我之前在这里写错的话：我原先说「版本不一致配对时会提示」，
+       那时候是【不对的】，当时根本没有任何东西在比对版本。现在才是真的。）
+
+【这个包是完全离线的】模组加载器已经放在包里，
+安装过程不需要联网，不用梯子，也不受任何网站能不能打开的影响。
+
+
+一、怎么装（双击一下就行）
+--------------------------
+
+1. 把这个压缩包【完整解压】到任意位置（比如桌面）。
+   不要只解压出单个文件，INSTALL.bat、SSMP 文件夹和
+   BepInEx_win_x64_5.4.23.4.zip 必须在一起。
+
+2. 双击 INSTALL.bat。
+
+3. 等它跑完，看到绿色的 Done 就好了。
+
+它会自己做这几件事：
+   - 找到你的 Silksong 安装位置（找不到会让你把路径粘进去）
+   - 先把你的存档备份成 zip，放在这个文件夹里的 save-backups\ 下
+     （只留最近 3 份，更旧的会自动删掉；它不会碰别的文件）
+   - 用包里自带的加载器装好（不联网）
+   - 把联机插件放进去
+   - 最后检查一遍有没有装成功
+
+窗口里的提示是英文的，因为 Windows 自带的 PowerShell 显示中文
+经常是乱码，英文反而不会出错。
+
+
+二、这个脚本安全吗
+------------------
+
+- 它只往【游戏目录】写东西，外加一个存档备份。
+  不改注册表、不改系统设置、不装任何后台程序、不联网。
+- 不需要管理员权限（除非你的游戏装在 C:\Program Files 里）。
+- 想卸载：把游戏目录里的 BepInEx 文件夹、winhttp.dll、
+  doorstop_config.ini、.doorstop_version、changelog.txt
+  删掉就完全干净了。
+
+包里那个 BepInEx_win_x64_5.4.23.4.zip 是 BepInEx 官方在 GitHub
+上发布的原版文件，没有改动过，大小 638,940 字节。
+
+有一点要提前说：BepInEx 这类模组加载器的工作方式，是在游戏
+exe 旁边放一个 dll，让游戏启动时连带加载它。这是所有同类
+加载器的通用做法，但这个手法和某些恶意软件相同，所以
+【杀毒软件有时会报毒】。看到告警是这个原因，不是脚本在干别的。
+
+真正的风险不在系统，在存档：模组有可能弄坏存档，
+所以脚本会先备份。
+
+
+三、怎么一起玩
+--------------
+
+1. 【从 Steam 启动游戏】，不要直接双击 exe。
+
+2. 一个人开房：选 "Steam" 那一页，点 Create Lobby。
+   开完房不会直接进游戏，而是停在一个【等待室】里。
+
+3. 房主在等待室里点 INVITE FRIEND，会直接弹出 Steam 的邀请框，
+   不用自己去找 Steam 覆盖层。对方接受邀请就会进到同一个等待室。
+
+4. 两个人各自点一次 I'M READY。
+   名单上能看到对方是 READY 还是 NOT READY。
+   【两个人都 READY 之后】，两边才会同时打开各自的选存档界面。
+   反悔就再点一次取消。
+
+5. 进游戏后，屏幕上方会出现一行字，
+   写着「按 L 和 XXX 组成双人存档」。
+   两个人都按一下 L 就配对好了。
+   不想配对就别理它，它会自己消失。
+
+   【用手柄的话按下左摇杆（L3）】，和 L 是同一件事。
+   屏幕上那行字会自己判断你在用键盘还是手柄，显示你真正该按的那个。
+
+   （配对键原来是 J，这一版改成了 L。因为 J 是游戏自己
+     「打开背包并翻到笔记页」的默认键，按一下会同时干两件事。
+     L 在游戏的默认键位里没人用。）
+
+6. 之后这两个存档必须两个人都在线才能打开。
+   如果对方不来、或者两边一直停在「Waiting for XXX」不动，
+   你会被定住不能移动，屏幕上会写着在等谁。
+   【这时按 K】就能退出双人存档、自己单独玩。
+   注意：这只解开你这边，对方要自己也按一次 K。
+
+   ※ 不要去聊天框打 /coopsave off。被定住的时候聊天框打不开；
+     而且只要对方还在线，那条指令也只是【请求对方同意】，
+     并不会放你走。K 才是真正的出路。
+
+
+四、第一次玩的建议
+------------------
+
+* 两个人都【开新档】。
+  配对会检查双方已击败的 Boss 是否一致，老档大概率对不上。
+
+* 连接和等待室都已经实测跑通过（中国 ↔ 马来西亚，走 Steam 中继）。
+
+* 【之前卡在「Waiting for XXX」的原因已经找到并修掉了】
+  服务器把所有玩家的网络数据放在同一个拼包缓冲区里，而且是先拼字节、
+  后判断这包是谁发的。双人存档要同步的世界进度是全游戏唯一一个
+  大到需要拆包发送的数据，一拆包，两个人的数据就会被粘在一起，
+  连接的分帧从此错乱、五秒后超时重连，于是校验永远走不完。
+
+  这也解释了为什么配对、聊天、看到对方走路一直都正常——
+  那些包都很小，从来不需要拆。
+
+  现在每条连接各用各的缓冲区。
+  【这个修复已经实机验证通过】，两个人已经正常连上并一起玩过了。
+  万一还卡：按 K 脱身，然后把两边的日志都发回来。
+
+  备份脚本会自动做，位置见上面第一节。
+
+* 【从这一版开始，敌人和 Boss 才是真正同步的】
+  在这之前，控制这件事的开关默认是关的，而且没有任何界面能打开它，
+  所以你们其实是各打各的：同一只怪在你这边死了、在她那边还站着，
+  打完的记录也只记在动手的那个人身上。
+  现在这个开关被固定为常开，配置文件里存着的旧设置不再起作用。
+  【两个人都必须重装这一版】，只有一个人装是没用的。
+
+  顺带说一句：Boss 的击败记录本来就是各记各的，不会互相抄，
+  这是当初定好的规则（剧情进度共享，战绩和拾取各归各的）。
+  所以如果一个人已经打过、另一个人没打过，
+  那只怪在没打过的那个人的世界里还在，两个人可以一起再打一遍，
+  这次两边都会拿到记录。
+
+* 【茧：平时各看各的；但你死了之后，队友可以把你拉起来】
+  平时的规则没变：你只看得见【自己】的茧，对方也碰不到你的。
+
+  新加的是救人。你死掉之后【不会立刻回长椅】，会先在原地等一会儿，
+  最多 45 秒。这段时间里，你的茧会出现在【队友】那边，
+  她打【5 下】就能把你拉起来：
+  在你倒下的地方站起来，血量是你上限的【一半】（向下取整），
+  茧里的钱和丝也一起还给你，等于这一次没白死。
+
+  等的时候屏幕上有一行字，写着在等谁、对方已经打了几下。
+  不想等了就【按 K】，立刻回长椅、按原来的规则结算，
+  你的茧同时从队友那边消失。等满 45 秒没人来，也一样自动回长椅。
+  （注意：这里的 K 只是「不等了」，不会解除你们的双人存档。）
+
+  【两个人都死了，就都直接回长椅】，不会互相干等，
+  也不会出现谁站在那儿等一个同样躺着的人。
+
+  这一条是刚写的，【还没有实机验证过】。
+  真卡住不动了（按理说等满 45 秒一定会自己回长椅），
+  Alt+F4 强退就行，存档还停在上一次保存的地方。
+
+  这里原本藏着一个很隐蔽的问题，已经修掉：
+  两个人的茧在各自游戏里【名字完全一样】，而模组会把「打碎世界物件」
+  这类命中按名字转发给对方重放。于是她打她自己的茧，
+  你这边被打碎的是【你的】茧——而且和你们死在哪儿没关系，
+  隔着半个房间照样会中。茧里的钱是记在存档里的，
+  被这样打掉会直接结算掉、还会抹掉你那个茧的记录。
+  现在茧被排除在转发之外，对方攻击的副本也碰不到它。
+  你自己打自己的茧，一切照旧。
+
+* 【修掉了「后进房间的人，满屋子怪全定住」】
+  只要你走进一个对方已经清过的房间，那些怪在你这边会全部卡死不动。
+  原因是服务器只记得「这怪没血了」，却不记得「它死过」，
+  于是你这边的怪变成了一具零血的活尸：它每一帧都想死，
+  每一帧都被模组挡回去，一个房间能刷出七千多次，整屋子就此卡住。
+  现在补状态时会把这类怪真正结算掉一次，进门看到的是尸体而不是活尸。
+
+* 【昵称会记住了】
+  以前只有「直连 IP」和「直连开房」两条路会保存昵称，而你们用的是 Steam
+  开房 / 加入 / 房间列表，这几条一条都不保存 —— 所以不是你忘了填，
+  是它在你的用法下从来没存过。现在填一次就记住，下次自动带出来。
+
+* 【进游戏之后不用再碰键盘了】
+  配对（L）和放弃等待（K）这两个动作，手柄都可以【按下左摇杆】来完成。
+  选左摇杆是因为它是游戏唯一没占用的按钮 —— 扳机、肩键、四个面键、
+  右摇杆按下、旁边那两个键，游戏全都用掉了。
+  这两个动作不会同时出现（没配对时才问你要不要配对，配对了才谈得上放弃），
+  所以共用一个键不会冲突。
+  聊天键故意没给手柄绑：手柄本来就打不了字，绑了也只是开一个填不进去的框。
+
+  ※ 联机大厅（连接、房间列表、等待室）目前仍然要用鼠标键盘，这是你定的。
+
+* 【手柄在选存档界面按不进去，这一版尝试修了】
+  原因是模组会自己建一套界面输入系统，而负责「在菜单里把它关掉」的代码
+  是挂在场景切换上的 —— 但模组本身就是在主菜单里启动的，此后到进游戏
+  之前根本不会再切场景，所以它整个菜单流程都开着。现在它一建出来
+  就先判断一次当前场景。
+
+  顺便解释那个最奇怪的地方：为什么手柄能上下切换存档却按不进去，
+  键盘却可以。游戏判定「确认」时分成两支——
+  键盘那支除了确认键还认【跳跃键】，手柄那支【只认确认键】，没有替补。
+  所以确认信号一旦出不来，键盘还有后路，手柄直接没辙。
+
+  ※ 这一条【没有实机验证过】。如果还是按不进去，
+    把游戏目录下 BepInEx\LogOutput.log 发我：这一版特意在进选存档界面时
+    写了一行「Save selection is driven by ...」，那行字会直接说明
+    是谁在管这个界面，不用再猜。
+
+* 聊天框默认按 Y 打开，打 /help 可以看到所有指令。
+
+* 【修掉了「在聊天框打字会误触发快捷键」】
+  以前模组只屏蔽了游戏自己的操作，没屏蔽它自己的快捷键。
+  所以在聊天框里打一句带 k 的话（比如「ok」）就等于按了一次 K ——
+  配上新的救人机制，那就是当场放弃等救援、直接回长椅；
+  打带配对键的字则会发一次配对请求。
+  现在聊天框一打开，模组自己的快捷键就整个关掉，关掉聊天再恢复。
+  另外 Enter 以前在聊天关着的时候也会白触发一次，现在不会了。
+
+* 【模组界面跟着游戏语言走】
+  以前模组自己的字全是英文，游戏明明是中文的，
+  一到模组这儿就换语言。
+  现在游戏设成中文，联机界面、聊天里的提示、
+  等人和救人的提示都是中文；设成别的语言还是英文。
+  在游戏选项里中途换语言也会立刻跟着变，不用重开游戏。
+
+
+五、出问题的话
+--------------
+
+游戏目录下 BepInEx\LogOutput.log 是日志，
+出问题把它发回来就能定位。
+
+如果是卡在「Waiting for XXX」，日志里这两句最有用：
+  Starting a check     —— 会列出三个存档 key，一眼能看出哪个对不上
+  Turned down a hello  —— 说明有一条握手消息被丢掉了，以及丢的原因
+
+
+六、这东西是谁写的
+------------------
+
+联机功能本身、以及这里几乎全部的代码，都是 Extremelyd1 写的
+（原项目：github.com/Extremelyd1/SSMP）。
+这一份只是在它上面加了「两个人共用一条流程」的双人存档，
+沿用和原作相同的 LGPL-2.1 许可证。
+
+※ 有任何问题请找我，【不要去原作者的 Discord 或 issues 页面】。
+  这些改动不是人家写的，人家既复现不了也没义务解释。
+
+包里还有两个别人的东西：
+  BouncyCastle.Cryptography.dll —— 第三方加密库，MIT 许可证，
+    版权归 The Legion of the Bouncy Castle Inc.，
+    完整条款见同目录下的 LICENSE-BouncyCastle.md。
+  BepInEx_win_x64_5.4.23.4.zip —— BepInEx 官方发布的原包，
+    一个字节都没有改过。

package/LICENSE

@@ -0,0 +1,458 @@
+                  GNU LESSER GENERAL PUBLIC LICENSE
+                       Version 2.1, February 1999
+
+ Copyright (C) 1991, 1999 Free Software Foundation, Inc.
+ 51 Franklin Street, Fifth Floor, Boston, MA  02110-1301  USA
+ Everyone is permitted to copy and distribute verbatim copies
+ of this license document, but changing it is not allowed.
+
+[This is the first released version of the Lesser GPL.  It also counts
+ as the successor of the GNU Library Public License, version 2, hence
+ the version number 2.1.]
+
+                            Preamble
+
+  The licenses for most software are designed to take away your
+freedom to share and change it.  By contrast, the GNU General Public
+Licenses are intended to guarantee your freedom to share and change
+free software--to make sure the software is free for all its users.
+
+  This license, the Lesser General Public License, applies to some
+specially designated software packages--typically libraries--of the
+Free Software Foundation and other authors who decide to use it.  You
+can use it too, but we suggest you first think carefully about whether
+this license or the ordinary General Public License is the better
+strategy to use in any particular case, based on the explanations below.
+
+  When we speak of free software, we are referring to freedom of use,
+not price.  Our General Public Licenses are designed to make sure that
+you have the freedom to distribute copies of free software (and charge
+for this service if you wish); that you receive source code or can get
+it if you want it; that you can change the software and use pieces of
+it in new free programs; and that you are informed that you can do
+these things.
+
+  To protect your rights, we need to make restrictions that forbid
+distributors to deny you these rights or to ask you to surrender these
+rights.  These restrictions translate to certain responsibilities for
+you if you distribute copies of the library or if you modify it.
+
+  For example, if you distribute copies of the library, whether gratis
+or for a fee, you must give the recipients all the rights that we gave
+you.  You must make sure that they, too, receive or can get the source
+code.  If you link other code with the library, you must provide
+complete object files to the recipients, so that they can relink them
+with the library after making changes to the library and recompiling
+it.  And you must show them these terms so they know their rights.
+
+  We protect your rights with a two-step method: (1) we copyright the
+library, and (2) we offer you this license, which gives you legal
+permission to copy, distribute and/or modify the library.
+
+  To protect each distributor, we want to make it very clear that
+there is no warranty for the free library.  Also, if the library is
+modified by someone else and passed on, the recipients should know
+that what they have is not the original version, so that the original
+author's reputation will not be affected by problems that might be
+introduced by others.
+
+  Finally, software patents pose a constant threat to the existence of
+any free program.  We wish to make sure that a company cannot
+effectively restrict the users of a free program by obtaining a
+restrictive license from a patent holder.  Therefore, we insist that
+any patent license obtained for a version of the library must be
+consistent with the full freedom of use specified in this license.
+
+  Most GNU software, including some libraries, is covered by the
+ordinary GNU General Public License.  This license, the GNU Lesser
+General Public License, applies to certain designated libraries, and
+is quite different from the ordinary General Public License.  We use
+this license for certain libraries in order to permit linking those
+libraries into non-free programs.
+
+  When a program is linked with a library, whether statically or using
+a shared library, the combination of the two is legally speaking a
+combined work, a derivative of the original library.  The ordinary
+General Public License therefore permits such linking only if the
+entire combination fits its criteria of freedom.  The Lesser General
+Public License permits more lax criteria for linking other code with
+the library.
+
+  We call this license the "Lesser" General Public License because it
+does Less to protect the user's freedom than the ordinary General
+Public License.  It also provides other free software developers Less
+of an advantage over competing non-free programs.  These disadvantages
+are the reason we use the ordinary General Public License for many
+libraries.  However, the Lesser license provides advantages in certain
+special circumstances.
+
+  For example, on rare occasions, there may be a special need to
+encourage the widest possible use of a certain library, so that it becomes
+a de-facto standard.  To achieve this, non-free programs must be
+allowed to use the library.  A more frequent case is that a free
+library does the same job as widely used non-free libraries.  In this
+case, there is little to gain by limiting the free library to free
+software only, so we use the Lesser General Public License.
+
+  In other cases, permission to use a particular library in non-free
+programs enables a greater number of people to use a large body of
+free software.  For example, permission to use the GNU C Library in
+non-free programs enables many more people to use the whole GNU
+operating system, as well as its variant, the GNU/Linux operating
+system.
+
+  Although the Lesser General Public License is Less protective of the
+users' freedom, it does ensure that the user of a program that is
+linked with the Library has the freedom and the wherewithal to run
+that program using a modified version of the Library.
+
+  The precise terms and conditions for copying, distribution and
+modification follow.  Pay close attention to the difference between a
+"work based on the library" and a "work that uses the library".  The
+former contains code derived from the library, whereas the latter must
+be combined with the library in order to run.
+
+                  GNU LESSER GENERAL PUBLIC LICENSE
+   TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION
+
+  0. This License Agreement applies to any software library or other
+program which contains a notice placed by the copyright holder or
+other authorized party saying it may be distributed under the terms of
+this Lesser General Public License (also called "this License").
+Each licensee is addressed as "you".
+
+  A "library" means a collection of software functions and/or data
+prepared so as to be conveniently linked with application programs
+(which use some of those functions and data) to form executables.
+
+  The "Library", below, refers to any such software library or work
+which has been distributed under these terms.  A "work based on the
+Library" means either the Library or any derivative work under
+copyright law: that is to say, a work containing the Library or a
+portion of it, either verbatim or with modifications and/or translated
+straightforwardly into another language.  (Hereinafter, translation is
+included without limitation in the term "modification".)
+
+  "Source code" for a work means the preferred form of the work for
+making modifications to it.  For a library, complete source code means
+all the source code for all modules it contains, plus any associated
+interface definition files, plus the scripts used to control compilation
+and installation of the library.
+
+  Activities other than copying, distribution and modification are not
+covered by this License; they are outside its scope.  The act of
+running a program using the Library is not restricted, and output from
+such a program is covered only if its contents constitute a work based
+on the Library (independent of the use of the Library in a tool for
+writing it).  Whether that is true depends on what the Library does
+and what the program that uses the Library does.
+
+  1. You may copy and distribute verbatim copies of the Library's
+complete source code as you receive it, in any medium, provided that
+you conspicuously and appropriately publish on each copy an
+appropriate copyright notice and disclaimer of warranty; keep intact
+all the notices that refer to this License and to the absence of any
+warranty; and distribute a copy of this License along with the
+Library.
+
+  You may charge a fee for the physical act of transferring a copy,
+and you may at your option offer warranty protection in exchange for a
+fee.
+
+  2. You may modify your copy or copies of the Library or any portion
+of it, thus forming a work based on the Library, and copy and
+distribute such modifications or work under the terms of Section 1
+above, provided that you also meet all of these conditions:
+
+    a) The modified work must itself be a software library.
+
+    b) You must cause the files modified to carry prominent notices
+    stating that you changed the files and the date of any change.
+
+    c) You must cause the whole of the work to be licensed at no
+    charge to all third parties under the terms of this License.
+
+    d) If a facility in the modified Library refers to a function or a
+    table of data to be supplied by an application program that uses
+    the facility, other than as an argument passed when the facility
+    is invoked, then you must make a good faith effort to ensure that,
+    in the event an application does not supply such function or
+    table, the facility still operates, and performs whatever part of
+    its purpose remains meaningful.
+
+    (For example, a function in a library to compute square roots has
+    a purpose that is entirely well-defined independent of the
+    application.  Therefore, Subsection 2d requires that any
+    application-supplied function or table used by this function must
+    be optional: if the application does not supply it, the square
+    root function must still compute square roots.)
+
+These requirements apply to the modified work as a whole.  If
+identifiable sections of that work are not derived from the Library,
+and can be reasonably considered independent and separate works in
+themselves, then this License, and its terms, do not apply to those
+sections when you distribute them as separate works.  But when you
+distribute the same sections as part of a whole which is a work based
+on the Library, the distribution of the whole must be on the terms of
+this License, whose permissions for other licensees extend to the
+entire whole, and thus to each and every part regardless of who wrote
+it.
+
+Thus, it is not the intent of this section to claim rights or contest
+your rights to work written entirely by you; rather, the intent is to
+exercise the right to control the distribution of derivative or
+collective works based on the Library.
+
+In addition, mere aggregation of another work not based on the Library
+with the Library (or with a work based on the Library) on a volume of
+a storage or distribution medium does not bring the other work under
+the scope of this License.
+
+  3. You may opt to apply the terms of the ordinary GNU General Public
+License instead of this License to a given copy of the Library.  To do
+this, you must alter all the notices that refer to this License, so
+that they refer to the ordinary GNU General Public License, version 2,
+instead of to this License.  (If a newer version than version 2 of the
+ordinary GNU General Public License has appeared, then you can specify
+that version instead if you wish.)  Do not make any other change in
+these notices.
+
+  Once this change is made in a given copy, it is irreversible for
+that copy, so the ordinary GNU General Public License applies to all
+subsequent copies and derivative works made from that copy.
+
+  This option is useful when you wish to copy part of the code of
+the Library into a program that is not a library.
+
+  4. You may copy and distribute the Library (or a portion or
+derivative of it, under Section 2) in object code or executable form
+under the terms of Sections 1 and 2 above provided that you accompany
+it with the complete corresponding machine-readable source code, which
+must be distributed under the terms of Sections 1 and 2 above on a
+medium customarily used for software interchange.
+
+  If distribution of object code is made by offering access to copy
+from a designated place, then offering equivalent access to copy the
+source code from the same place satisfies the requirement to
+distribute the source code, even though third parties are not
+compelled to copy the source along with the object code.
+
+  5. A program that contains no derivative of any portion of the
+Library, but is designed to work with the Library by being compiled or
+linked with it, is called a "work that uses the Library".  Such a
+work, in isolation, is not a derivative work of the Library, and
+therefore falls outside the scope of this License.
+
+  However, linking a "work that uses the Library" with the Library
+creates an executable that is a derivative of the Library (because it
+contains portions of the Library), rather than a "work that uses the
+library".  The executable is therefore covered by this License.
+Section 6 states terms for distribution of such executables.
+
+  When a "work that uses the Library" uses material from a header file
+that is part of the Library, the object code for the work may be a
+derivative work of the Library even though the source code is not.
+Whether this is true is especially significant if the work can be
+linked without the Library, or if the work is itself a library.  The
+threshold for this to be true is not precisely defined by law.
+
+  If such an object file uses only numerical parameters, data
+structure layouts and accessors, and small macros and small inline
+functions (ten lines or less in length), then the use of the object
+file is unrestricted, regardless of whether it is legally a derivative
+work.  (Executables containing this object code plus portions of the
+Library will still fall under Section 6.)
+
+  Otherwise, if the work is a derivative of the Library, you may
+distribute the object code for the work under the terms of Section 6.
+Any executables containing that work also fall under Section 6,
+whether or not they are linked directly with the Library itself.
+
+  6. As an exception to the Sections above, you may also combine or
+link a "work that uses the Library" with the Library to produce a
+work containing portions of the Library, and distribute that work
+under terms of your choice, provided that the terms permit
+modification of the work for the customer's own use and reverse
+engineering for debugging such modifications.
+
+  You must give prominent notice with each copy of the work that the
+Library is used in it and that the Library and its use are covered by
+this License.  You must supply a copy of this License.  If the work
+during execution displays copyright notices, you must include the
+copyright notice for the Library among them, as well as a reference
+directing the user to the copy of this License.  Also, you must do one
+of these things:
+
+    a) Accompany the work with the complete corresponding
+    machine-readable source code for the Library including whatever
+    changes were used in the work (which must be distributed under
+    Sections 1 and 2 above); and, if the work is an executable linked
+    with the Library, with the complete machine-readable "work that
+    uses the Library", as object code and/or source code, so that the
+    user can modify the Library and then relink to produce a modified
+    executable containing the modified Library.  (It is understood
+    that the user who changes the contents of definitions files in the
+    Library will not necessarily be able to recompile the application
+    to use the modified definitions.)
+
+    b) Use a suitable shared library mechanism for linking with the
+    Library.  A suitable mechanism is one that (1) uses at run time a
+    copy of the library already present on the user's computer system,
+    rather than copying library functions into the executable, and (2)
+    will operate properly with a modified version of the library, if
+    the user installs one, as long as the modified version is
+    interface-compatible with the version that the work was made with.
+
+    c) Accompany the work with a written offer, valid for at
+    least three years, to give the same user the materials
+    specified in Subsection 6a, above, for a charge no more
+    than the cost of performing this distribution.
+
+    d) If distribution of the work is made by offering access to copy
+    from a designated place, offer equivalent access to copy the above
+    specified materials from the same place.
+
+    e) Verify that the user has already received a copy of these
+    materials or that you have already sent this user a copy.
+
+  For an executable, the required form of the "work that uses the
+Library" must include any data and utility programs needed for
+reproducing the executable from it.  However, as a special exception,
+the materials to be distributed need not include anything that is
+normally distributed (in either source or binary form) with the major
+components (compiler, kernel, and so on) of the operating system on
+which the executable runs, unless that component itself accompanies
+the executable.
+
+  It may happen that this requirement contradicts the license
+restrictions of other proprietary libraries that do not normally
+accompany the operating system.  Such a contradiction means you cannot
+use both them and the Library together in an executable that you
+distribute.
+
+  7. You may place library facilities that are a work based on the
+Library side-by-side in a single library together with other library
+facilities not covered by this License, and distribute such a combined
+library, provided that the separate distribution of the work based on
+the Library and of the other library facilities is otherwise
+permitted, and provided that you do these two things:
+
+    a) Accompany the combined library with a copy of the same work
+    based on the Library, uncombined with any other library
+    facilities.  This must be distributed under the terms of the
+    Sections above.
+
+    b) Give prominent notice with the combined library of the fact
+    that part of it is a work based on the Library, and explaining
+    where to find the accompanying uncombined form of the same work.
+
+  8. You may not copy, modify, sublicense, link with, or distribute
+the Library except as expressly provided under this License.  Any
+attempt otherwise to copy, modify, sublicense, link with, or
+distribute the Library is void, and will automatically terminate your
+rights under this License.  However, parties who have received copies,
+or rights, from you under this License will not have their licenses
+terminated so long as such parties remain in full compliance.
+
+  9. You are not required to accept this License, since you have not
+signed it.  However, nothing else grants you permission to modify or
+distribute the Library or its derivative works.  These actions are
+prohibited by law if you do not accept this License.  Therefore, by
+modifying or distributing the Library (or any work based on the
+Library), you indicate your acceptance of this License to do so, and
+all its terms and conditions for copying, distributing or modifying
+the Library or works based on it.
+
+  10. Each time you redistribute the Library (or any work based on the
+Library), the recipient automatically receives a license from the
+original licensor to copy, distribute, link with or modify the Library
+subject to these terms and conditions.  You may not impose any further
+restrictions on the recipients' exercise of the rights granted herein.
+You are not responsible for enforcing compliance by third parties with
+this License.
+
+  11. If, as a consequence of a court judgment or allegation of patent
+infringement or for any other reason (not limited to patent issues),
+conditions are imposed on you (whether by court order, agreement or
+otherwise) that contradict the conditions of this License, they do not
+excuse you from the conditions of this License.  If you cannot
+distribute so as to satisfy simultaneously your obligations under this
+License and any other pertinent obligations, then as a consequence you
+may not distribute the Library at all.  For example, if a patent
+license would not permit royalty-free redistribution of the Library by
+all those who receive copies directly or indirectly through you, then
+the only way you could satisfy both it and this License would be to
+refrain entirely from distribution of the Library.
+
+If any portion of this section is held invalid or unenforceable under any
+particular circumstance, the balance of the section is intended to apply,
+and the section as a whole is intended to apply in other circumstances.
+
+It is not the purpose of this section to induce you to infringe any
+patents or other property right claims or to contest validity of any
+such claims; this section has the sole purpose of protecting the
+integrity of the free software distribution system which is
+implemented by public license practices.  Many people have made
+generous contributions to the wide range of software distributed
+through that system in reliance on consistent application of that
+system; it is up to the author/donor to decide if he or she is willing
+to distribute software through any other system and a licensee cannot
+impose that choice.
+
+This section is intended to make thoroughly clear what is believed to
+be a consequence of the rest of this License.
+
+  12. If the distribution and/or use of the Library is restricted in
+certain countries either by patents or by copyrighted interfaces, the
+original copyright holder who places the Library under this License may add
+an explicit geographical distribution limitation excluding those countries,
+so that distribution is permitted only in or among countries not thus
+excluded.  In such case, this License incorporates the limitation as if
+written in the body of this License.
+
+  13. The Free Software Foundation may publish revised and/or new
+versions of the Lesser General Public License from time to time.
+Such new versions will be similar in spirit to the present version,
+but may differ in detail to address new problems or concerns.
+
+Each version is given a distinguishing version number.  If the Library
+specifies a version number of this License which applies to it and
+"any later version", you have the option of following the terms and
+conditions either of that version or of any later version published by
+the Free Software Foundation.  If the Library does not specify a
+license version number, you may choose any version ever published by
+the Free Software Foundation.
+
+  14. If you wish to incorporate parts of the Library into other free
+programs whose distribution conditions are incompatible with these,
+write to the author to ask for permission.  For software which is
+copyrighted by the Free Software Foundation, write to the Free
+Software Foundation; we sometimes make exceptions for this.  Our
+decision will be guided by the two goals of preserving the free status
+of all derivatives of our free software and of promoting the sharing
+and reuse of software generally.
+
+                            NO WARRANTY
+
+  15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO
+WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW.
+EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR
+OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY
+KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE
+IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR
+PURPOSE.  THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE
+LIBRARY IS WITH YOU.  SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME
+THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.
+
+  16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN
+WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY
+AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU
+FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR
+CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE
+LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING
+RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A
+FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF
+SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH
+DAMAGES.
+
+                     END OF TERMS AND CONDITIONS

package/LICENSE-BouncyCastle.md

@@ -0,0 +1,15 @@
+MIT License (https://opensource.org/licenses/MIT)
+
+Copyright (c) 2000-2026 The Legion of the Bouncy Castle Inc. (https://www.bouncycastle.org).
+Permission is hereby granted, free of charge, to any person obtaining a copy of this software and
+associated documentation files (the "Software"), to deal in the Software without restriction,
+including without limitation the rights to use, copy, modify, merge, publish, distribute,
+sub license, and/or sell copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions: The above copyright notice and this
+permission notice shall be included in all copies or substantial portions of the Software.
+
+**THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT
+NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND
+NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM,
+DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT
+OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.**

package/README.md

@@ -0,0 +1,17 @@
+# silksong-coop-mod 0.4.0
+
+The files a player needs to install a two-player co-op build of **SSMP**, packaged so they can be fetched from
+a mirror that is reachable inside mainland China. This is not a Node library: nothing here is imported or run
+by `npm install`.
+
+## Install
+
+Download and unpack the tarball, then double-click `INSTALL.bat`. `INSTALL.txt` explains the rest, in Chinese.
+
+The BepInEx loader is included, so the install needs no network access at all.
+
+## Credit and licence
+
+The multiplayer mod is the work of [Extremelyd1](https://github.com/Extremelyd1/SSMP). This is a modified copy
+that adds a shared two-player save; please do not take questions about it to the original author. Distributed
+under the GNU LGPL 2.1 - see `LICENSE`. Built from https://github.com/Candy-649/SSMP at `deba6cf`.

package/install.ps1

@@ -0,0 +1,250 @@
+# Installs the BepInEx mod loader and the SSMP co-op plugin into Hollow Knight: Silksong.
+#
+# The loader ships inside this archive, so a normal install needs no network at all. Downloading is only a fallback
+# for when the bundled copy is missing, and the host that serves it is blocked on some networks.
+#
+# Console output is English on purpose: Windows PowerShell 5.1 reads a UTF-8 file without a BOM as ANSI, which turns
+# any other language into mojibake on a machine that has not been set up for it. The readable explanation lives in
+# INSTALL.txt next to this script.
+#
+# Everything this script writes goes into the game folder, plus one backup of the save folder. It changes no system
+# setting and needs no administrator rights unless the game itself sits in a protected folder.
+
+$ErrorActionPreference = 'Stop'
+
+$GameExe = 'Hollow Knight Silksong.exe'
+$GameDirName = 'Hollow Knight Silksong'
+
+# How many save backups to keep. Older ones are removed after a new one is made, so reinstalling a few times does not
+# leave a pile behind. Only backups this script made, in the folder this script made, are ever touched.
+$KeepBackups = 3
+$ApiUrl = 'https://thunderstore.io/api/experimental/package/silksong_modding/BepInExPack_Silksong/'
+
+# Used only when the version cannot be looked up. The package that is merely a redirect stub, BepInEx/
+# BepInExPack_Silksong, must never be used here: it downloads successfully and contains nothing.
+$FallbackUrl = 'https://thunderstore.io/package/download/silksong_modding/BepInExPack_Silksong/1.0.3/'
+$FallbackVersion = '1.0.3'
+
+function Write-Step($text) { Write-Host ""; Write-Host "==> $text" -ForegroundColor Cyan }
+function Write-Ok($text) { Write-Host "    $text" -ForegroundColor Green }
+function Write-Warn2($text) { Write-Host "    $text" -ForegroundColor Yellow }
+
+function Find-Game {
+    $candidates = New-Object System.Collections.Generic.List[string]
+
+    # Steam records where it is installed, and where its other libraries are
+    try {
+        $steamPath = (Get-ItemProperty 'HKCU:\Software\Valve\Steam' -ErrorAction Stop).SteamPath
+        if ($steamPath) {
+            $steamPath = $steamPath -replace '/', '\'
+            $candidates.Add((Join-Path $steamPath "steamapps\common\$GameDirName"))
+
+            $vdf = Join-Path $steamPath 'steamapps\libraryfolders.vdf'
+            if (Test-Path $vdf) {
+                foreach ($line in (Get-Content $vdf)) {
+                    if ($line -match '"path"\s+"(.+?)"') {
+                        $libPath = $matches[1] -replace '\\\\', '\'
+                        $candidates.Add((Join-Path $libPath "steamapps\common\$GameDirName"))
+                    }
+                }
+            }
+        }
+    } catch {
+        # No Steam in the registry is not fatal; the guesses below and the prompt still apply
+    }
+
+    # Common places people put a second Steam library
+    foreach ($drive in (Get-PSDrive -PSProvider FileSystem).Name) {
+        $candidates.Add("${drive}:\STEAM\steamapps\common\$GameDirName")
+        $candidates.Add("${drive}:\SteamLibrary\steamapps\common\$GameDirName")
+        $candidates.Add("${drive}:\Steam\steamapps\common\$GameDirName")
+    }
+
+    foreach ($candidate in ($candidates | Select-Object -Unique)) {
+        if (Test-Path (Join-Path $candidate $GameExe)) { return $candidate }
+    }
+
+    return $null
+}
+
+function Backup-Saves {
+    $lowLow = Join-Path $env:USERPROFILE 'AppData\LocalLow'
+    if (-not (Test-Path $lowLow)) { Write-Warn2 'No LocalLow folder found, skipping the save backup.'; return }
+
+    # Found rather than assumed, so that a different folder name does not silently skip the backup
+    $saveDirs = Get-ChildItem $lowLow -Directory -Recurse -Depth 1 -ErrorAction SilentlyContinue |
+        Where-Object { $_.Name -like '*Silksong*' }
+
+    if (-not $saveDirs) { Write-Warn2 'No Silksong save folder found, skipping the save backup.'; return }
+
+    # Kept in a folder beside this script rather than on the desktop. These are only ever wanted if an install goes
+    # wrong, and piling them onto someone's desktop is a poor price for that. The trade is that deleting the unpacked
+    # installer takes them with it, which is why the script says where they are.
+    $backupDir = Join-Path $PSScriptRoot 'save-backups'
+
+    foreach ($dir in $saveDirs) {
+        $stamp = Get-Date -Format 'yyyyMMdd-HHmmss'
+        # The folder name is part of it: two save folders backed up within the same second would otherwise write the
+        # same file name, and the -Force below would quietly overwrite the first backup with the second
+        $target = Join-Path $backupDir "silksong-saves-backup-$($dir.Name)-$stamp.zip"
+        try {
+            New-Item -ItemType Directory -Path $backupDir -Force | Out-Null
+            Compress-Archive -Path $dir.FullName -DestinationPath $target -Force
+            Write-Ok "Saves backed up to: $target"
+
+            # Deliberately narrow: only this folder, only names this script writes, and only after the new backup
+            # exists, so a failed backup never costs you the older ones
+            Get-ChildItem -Path $backupDir -Filter 'silksong-saves-backup-*.zip' -File -ErrorAction SilentlyContinue |
+                Sort-Object LastWriteTime -Descending |
+                Select-Object -Skip $KeepBackups |
+                ForEach-Object {
+                    Remove-Item -LiteralPath $_.FullName -Force -ErrorAction SilentlyContinue
+                    Write-Ok "Removed an older backup: $($_.Name)"
+                }
+        } catch {
+            Write-Warn2 "Could not back up $($dir.FullName): $($_.Exception.Message)"
+        }
+    }
+}
+
+function Get-LoaderArchive($work) {
+    # The bundled copy first: it is the whole point of shipping one, and it works on networks where the download host
+    # is blocked. Any BepInEx archive placed next to this script is accepted, so a manually downloaded one works too.
+    $bundled = Get-ChildItem $PSScriptRoot -Filter 'BepInEx*.zip' -File -ErrorAction SilentlyContinue |
+        Select-Object -First 1
+    if ($bundled) {
+        Write-Ok "Using the copy that came with this installer: $($bundled.Name)"
+        return $bundled.FullName
+    }
+
+    Write-Warn2 'No BepInEx archive next to this script, downloading one instead.'
+
+    $url = $FallbackUrl
+    $version = "$FallbackVersion (fallback)"
+    try {
+        $info = Invoke-RestMethod -Uri $ApiUrl -UseBasicParsing -TimeoutSec 30
+        if ($info.latest.download_url) {
+            $url = $info.latest.download_url
+            $version = $info.latest.version_number
+        }
+    } catch {
+        Write-Warn2 "Could not ask for the newest version ($($_.Exception.Message))."
+    }
+
+    Write-Ok "Version: $version"
+
+    $zipPath = Join-Path $work 'bepinex.zip'
+    $oldProgress = $ProgressPreference
+    $ProgressPreference = 'SilentlyContinue'
+    try {
+        Invoke-WebRequest -Uri $url -OutFile $zipPath -UseBasicParsing -TimeoutSec 300
+    } catch {
+        throw ("Could not download the mod loader: $($_.Exception.Message)`n" +
+               "      Your network may be blocking it. Ask for an installer with the loader included, or put a`n" +
+               "      BepInEx zip next to this script and run it again.")
+    } finally {
+        $ProgressPreference = $oldProgress
+    }
+
+    # A download that succeeds but is far too small is the empty redirect package, which would install nothing at all
+    if ((Get-Item $zipPath).Length -lt 500KB) {
+        throw 'That download is too small to be the mod loader. It is probably the empty redirect package.'
+    }
+
+    return $zipPath
+}
+
+function Find-PayloadRoot($extractedDir) {
+    # The layer to copy is the one holding the loader itself, whatever the archive wraps it in. Matching on the
+    # contents rather than on a folder name means a repackaged archive still installs correctly.
+    $all = @(Get-Item $extractedDir) + @(Get-ChildItem $extractedDir -Recurse -Directory)
+    foreach ($dir in $all) {
+        $hasBepInEx = Test-Path (Join-Path $dir.FullName 'BepInEx')
+        $hasProxy = (Test-Path (Join-Path $dir.FullName 'winhttp.dll')) -or
+                    (Test-Path (Join-Path $dir.FullName 'version.dll'))
+        if ($hasBepInEx -and $hasProxy) { return $dir.FullName }
+    }
+
+    return $null
+}
+
+try {
+    Write-Host ""
+    Write-Host "  Silksong co-op (SSMP) installer" -ForegroundColor White
+    Write-Host "  --------------------------------"
+
+    Write-Step 'Looking for the game'
+    $game = Find-Game
+    if (-not $game) {
+        Write-Warn2 "Could not find $GameDirName automatically."
+        Write-Host "    Paste the folder that contains $GameExe and press Enter:"
+        $game = (Read-Host '    Game folder').Trim('"', ' ')
+        if (-not (Test-Path (Join-Path $game $GameExe))) {
+            throw "No $GameExe in: $game"
+        }
+    }
+    Write-Ok "Game folder: $game"
+
+    Write-Step 'Backing up saves first'
+    Backup-Saves
+
+    $work = Join-Path ([System.IO.Path]::GetTempPath()) ("ssmp-install-" + [Guid]::NewGuid().ToString('N'))
+    New-Item -ItemType Directory -Path $work -Force | Out-Null
+
+    Write-Step 'Getting the BepInEx mod loader'
+    $archive = Get-LoaderArchive $work
+
+    Write-Step 'Installing the mod loader into the game folder'
+    $extracted = Join-Path $work 'extracted'
+    Expand-Archive -Path $archive -DestinationPath $extracted -Force
+
+    $payload = Find-PayloadRoot $extracted
+    if (-not $payload) {
+        throw 'Could not find the loader inside the archive (no folder with both BepInEx and winhttp.dll).'
+    }
+
+    foreach ($item in (Get-ChildItem $payload -Force)) {
+        Copy-Item -Path $item.FullName -Destination $game -Recurse -Force
+    }
+    Write-Ok 'Mod loader copied'
+
+    Write-Step 'Installing the co-op plugin'
+    $pluginSource = Join-Path $PSScriptRoot 'SSMP'
+    if (-not (Test-Path $pluginSource)) {
+        throw 'No SSMP folder next to this script. Unzip the whole archive first, then run the installer from inside it.'
+    }
+
+    $pluginTarget = Join-Path $game 'BepInEx\plugins\SSMP'
+    New-Item -ItemType Directory -Path $pluginTarget -Force | Out-Null
+    foreach ($dll in (Get-ChildItem $pluginSource -Filter '*.dll')) {
+        Copy-Item -Path $dll.FullName -Destination $pluginTarget -Force
+        Write-Ok "Installed $($dll.Name)"
+    }
+
+    Write-Step 'Checking the result'
+    $checks = @(
+        (Join-Path $game 'winhttp.dll'),
+        (Join-Path $game 'BepInEx'),
+        (Join-Path $pluginTarget 'SSMP.dll')
+    )
+    $missing = $checks | Where-Object { -not (Test-Path $_) }
+    if ($missing) {
+        throw "These are missing after the install:`n      " + ($missing -join "`n      ")
+    }
+
+    if (Test-Path $work) { Remove-Item $work -Recurse -Force -ErrorAction SilentlyContinue }
+
+    Write-Host ""
+    Write-Host "  Done. Start the game from Steam: the main menu now has 'Start Multiplayer'." -ForegroundColor Green
+    # Deliberately not a summary of how to play: that changed twice already, and a second copy of it here is a
+    # second copy to keep correct. INSTALL.txt is the one place that describes it.
+    Write-Host "  Both players need this same installer. INSTALL.txt says how to play together." -ForegroundColor Green
+    Write-Host ""
+} catch {
+    Write-Host ""
+    Write-Host "  FAILED: $($_.Exception.Message)" -ForegroundColor Red
+    Write-Host ""
+    Write-Host "  Nothing was started. You can run this installer again." -ForegroundColor Yellow
+    Write-Host ""
+    exit 1
+}

package/package.json

@@ -0,0 +1,28 @@
+{
+  "name": "silksong-coop-mod",
+  "version": "0.4.0",
+  "description": "Offline installer payload for a two-player co-op build of the SSMP Silksong multiplayer mod. Not a Node library.",
+  "license": "LGPL-2.1-or-later",
+  "author": "Candy-649 (https://github.com/Candy-649)",
+  "homepage": "https://github.com/Candy-649/SSMP",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/Candy-649/SSMP.git"
+  },
+  "keywords": [
+    "silksong",
+    "bepinex",
+    "mod",
+    "installer"
+  ],
+  "files": [
+    "INSTALL.bat",
+    "INSTALL.txt",
+    "install.ps1",
+    "LICENSE",
+    "LICENSE-BouncyCastle.md",
+    "BepInEx_win_x64_5.4.23.4.zip",
+    "SSMP/",
+    "README.md"
+  ]
+}