From 37152d81f6f37b37605f2b7de644aed3ed34f4ca Mon Sep 17 00:00:00 2001
From: Sainan <sainan@calamity.inc>
Date: Fri, 21 Feb 2025 21:52:07 +0100
Subject: [PATCH] Update manual for 0.10.3

---
 bootstrapper-manual.html | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/bootstrapper-manual.html b/bootstrapper-manual.html
index 179f2d6..f625165 100644
--- a/bootstrapper-manual.html
+++ b/bootstrapper-manual.html
@@ -97,6 +97,7 @@
 
 		<li><code>ee_log_in_console</code> — If true, writes everything that gets written to EE.log to the console as well.</li>
 		<li><code>skip_mission_start_timer</code> — If true, disables the 5 second wait before a mission starts.</li>
+		<li><code>logout_on_request_failure</code> — If false, the game will ignore HTTP request failures/timeouts instead of forcing a logout.</li>
 		<li><code>fov_override</code> — If not 0, overrides the game's FOV setting. You can use any value from 1 to 226.</li>
 		<li><code>forced_profile_dir</code> — An absolute path to a folder that will be used to read and write your game settings. Notably, this can be used to have the same settings regardless of username.</li>
 		<li><code>auto_start_scripts</code> — A list of scripts to automatically start, e.g. <code>["samples/Cycle Camera Hotkey (K).pluto"]</code>.</li>
@@ -126,7 +127,7 @@
 	<h2>HTTP Traffic Deviations</h2>
 	<ul>
 		<li>login.php & worldState.php requests have the extra query parameter <code>buildLabel</code> to indicate the client's buildLabel.</li>
-		<li>login.php requests also have an extra <code>clientMod</code> parameter to indicate that the OpenWF Bootstrapper is being used and what version of it.</li>
+		<li>login.php requests also have an extra <code>clientMod</code> parameter indicating the Bootstrapper's name and version. If Metadata Patches are in use, <code>metadataPatchesInUse=1</code> is added as well.</li>
 		<li>inventory.php & missionInventoryUpdate.php requests have the extra query parameter <code>xpBasedLevelCapDisabled</code> to indicate that the client has been patched to accept any PlayerLevel and doesn't need XPInfo to match.</li>
 	</ul>
 	<h2>Metadata Patches</h2>
@@ -138,6 +139,7 @@
 		<li>If the line starts with <code>&</code>, that character is removed from the line and the rest of the line is assumed to be an absolute path to be added to the current patch.</li>
 		<li>If the line starts with <code>></code>, that character is removed from the line and the rest of the line is assumed to be an absolute path for which a new patch is created.</li>
 		<li>If the line starts with <code>r|</code>, a replacement is added to the current patch in the form <code>r|A|Z</code> which means <code>A</code> in the metadata will be replaced with <code>Z</code>.</li>
+		<li>If the line starts with <code>s|</code>, a regex substitution is added to the current patch, e.g. <code>s|(.+)=1|$1=0</code> would change <code>HasCooldown=1</code> to be <code>HasCooldown=0</code>.</li>
 		<li>The line is added as a metadata prefix to the current patch. This works to add top-level properties but also to replace them because the game resolves duplicates by ignoring subsequent entries.</li>
 	</ol>
 	<p>If multiple patches affect the same absolute path, they are combined.</p>