OpenWF/Website
5
1
Fork 4
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Simplify bootstrapper setup

Browse Source 
The EXE is a bit useless given that sideloadify hasn't been needed for a while now and it may prevent people from properly preserving/archiving OpenWF.
This commit is contained in:
Sainan 2025-09-27 13:59:15 +02:00
parent c3844e8732
commit 2043b6181a
3 changed files with 3 additions and 7 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
contribute.php
View File

@ -19,14 +19,11 @@
</ul>
<h2>Seeding</h2>
<p>We are looking into IPFS for censorship-resistance. You could help the project out by pinning some things to your own node(s):</p>
<ul>
<li>Bootstrapper Setup.exe v1.0.0: <code>ipfs pin add /ipfs/bafkreifedzhddsiz4tfxwkzuzu6722seqvzhp7fdxkvdd6ao3canjesyda</code></li>
</ul>
<p>Also some of our more dynamic content, for which we recommend an hourly cronjob as IPNS names are resolved to their CID when pinning:</p>
<ul>
<li>OpenWF Website: <code>ipfs pin add /ipns/openwf.io</code></li>
<li>SpaceNinjaServer git mirror: <code>ipfs pin add /ipns/sns.openwf.io</code> (<a href="https://ipfs.io/ipns/k51qzi5uqu5diybf2prwdxnyiewvnjn5jshwiv5awoqrn9z5tfen8p31x15jk9/#repo=https%3A%2F%2Fipfs.io%2Fipns%2Fsns.openwf.io" target="_blank">gitview</a>)</li>
</ul>
<p>Note that IPNS names are resolved to their CID when pinning, so an hourly cronjob is recommended.</p>
</div>
<script src="https://cdn.jsdelivr.net/npm/bootstrap@5.3.3/dist/js/bootstrap.bundle.min.js" integrity="sha384-YvpcrYf0tY3lHB60NNkmXc5s9fDVZLESaAA55NDzOxhy9GkcIdslK1eN7N6jIeHz" crossorigin="anonymous"></script>
<script src="https://censorcanary.org/censorcanary.js" defer></script>

3
guide.php
View File

@ -36,8 +36,7 @@
<h2>Client Patch</h2>
<p>In order to connect to custom servers, the client needs to be patched, which is what the Boostrapper is for. To set it up:</p>
<ol>
<li>Download the bootstrapper setup <a href="https://ipfs.io/ipfs/bafkreifedzhddsiz4tfxwkzuzu6722seqvzhp7fdxkvdd6ao3canjesyda?filename=Bootstrapper+Setup.exe" target="_blank">for Windows</a> (<a href="https://onlyg.it/OpenWF/Bootstrapper-Setup" target="_blank">source code</a>) or <a href="supplementals/Bootstrapper%20Setup.sh" download>for Linux-ish (Bash)</a>.</li>
<li>Put the setup in the game's installation folder (the one where Warframe.x64.exe is in) and run it there.</li>
<li>Download <a href="https://openwf.io/supplementals/client%20drop-in/latest_dll" target="_blank">the boostrapper DLL (wtsapi32.dll)</a> and put it in your game's installation folder (the one where Warframe.x64.exe is in). On Linux, you may need to rename it to dwmapi.dll and/or use <code>WINEDLLOVERRIDE</code>.</li>
</ol>
<p>With that done, you can double-click Warframe.x64.exe to start the game with OpenWF. Opening the game's launcher will revert it back to normal.</p>
<p>The bootstrapper is <a href="bootstrapper-manual<?=(!empty($_DYNSTAT) ? ".html" : "");?>" target="_blank">documented here</a>, but the most important point is that, while the game is running, you can visit <a href="http://localhost:6155/" target="_blank">http://localhost:6155/</a> to manage options, cheats, and scripts.</p>

2
old-versions.php
View File

@ -34,7 +34,7 @@
<td><code>2025.03.18.09.51</code></td>
<td>&lt;&nbsp;38.6.0</td>
<td>Yareli&nbsp;Prime<!-- Login screen says "Techrot Encore" --></td>
<td><abbr title="Metadata Patches, Scripting API, etc. are fully functional in the bootstrapper.">Full modding support</abbr><!-- 38.6.0 is the only version that needs sideloadify (on Windows, at least). The powershell script just does it for all versions, for now at least. --></td>
<td><abbr title="Metadata Patches, Scripting API, etc. are fully functional in the bootstrapper.">Full modding support</abbr>, Warframe.x64.exe needs to be dropped onto <a href="https://github.com/Sainan/Sideloadify/releases/latest/download/sideloadify.exe" download>sideloadify.exe</a></td>
</tr>
<tr>
<td>4212893560910494140</td>