HTML5 Curation - Revision history

ThePowerPlayer: Moved HTTPS removal to the main part of the tutorial

2026-03-03T20:01:30Z

Moved HTTPS removal to the main part of the tutorial

@@ Line 6: / Line 6: @@
 If a web game doesn't ask to enable Adobe Flash Player and there's no sign or mention of any of the other [[Platforms]], it is very likely an HTML5 game. Many use game engines as their base, the most prominent example being Unity WebGL, which replaced the previous [[Unity_Curation|Unity NPAPI implementation]] that no longer works.
-To confirm this, press F12 to open the Developer Tools of your browser, click on the Inspect Element button and click on the game area. This will show you in the <code>Elements</code> tab the iframe the game is located in, and there you'll find the link for the main file of the game. You can also look for a <code>.html</code> file, likely with the filename <code>index.html</code>. However this is not always present, the iframe for many modern games will have no filename or extension at the end. These look like a regular URL rather than a link to a file.
+To confirm this, press F12 to open the Developer Tools of your browser, click on the Inspect Element button, and click on the game area. In the <code>Elements</code> tab, this will show you the <code>iframe</code> the game is located in, and there you'll find the link for the main file of the game. You can also look for a <code>.html</code> file, likely with the filename <code>index.html</code>. However, this is not always present; the <code>iframe</code> for many modern games will have no filename or extension at the end. These look like a regular URL rather than a link to a file.
 Copy the file's link and go to it. If it plays an unobstructed version of the game, you've found the source of your Launch Command. Keep in mind that not all games should be divorced from the page they are found in, such as individual games outside of webgame websites.
@@ Line 13: / Line 13: @@
 == Grabbing The Game From The Internet ==
-[[File:Individual-Sprites-HTML5-example.png|thumb|300px|Some games have one or more image files that act as sprite sheets, others will have each unique texture as an individual file, so make sure to get them all.]]
+[[File:Individual-Sprites-HTML5-example.png|thumb|300px|Some games have one or more image files that act as sprite sheets, while others will have each unique texture as an individual file, so make sure to get them all.]]
 There are an extremely low number of HTML5 games that are single-asset. For multi-asset curations, you have two main options, both of which are [[Curation Tutorial#Using cURLsDownloader for Multi-Asset Games|described here]], but each is more suited for different tasks which we'll explain here.
@@ Line 27: / Line 27: @@
 Wayback will not save these missing assets on a normal capture, and computers/browsers tend to clear cache much more frequently for optimization, making cache dumps unlikely to yield anything, so once it's gone, it's likely gone for good. Better to catch everything first try and make sure it's not lost. For more information on multi-assets in general, [[Curation Tutorial#Using cURLsDownloader for Multi-Asset Games|go here]].
-Once you've finished playing through the game, you need to make sure that all of the game's assets have actually been downloaded. To do this, first close Navigator, and clear it's cache by following [[Extended FAQ#ClearBasiliskCache|these instructions]], then close Navigator. Next, press the <code>Run</code> button to test the game again, this time without using MAD4FP. If the game does not work, MAD4FP likely failed to download some of the required assets. Follow the instructions in the [[#Missing Assets|Missing Assets]] section to complete the curation.
+Once you've finished playing through the game, you need to make sure that all of the game's assets have actually been downloaded. To do this, first close Navigator, and clear its cache by following [[Extended FAQ#ClearBasiliskCache|these instructions]], then close Navigator. Next, press the <code>Run</code> button to test the game again, this time without using MAD4FP. If the game does not work, MAD4FP likely failed to download some of the required assets. Follow the instructions in the [[#Missing Assets|Missing Assets]] section to complete the curation.
 == Other Browsers ==
@@ Line 133: / Line 148: @@
 == Troubleshooting ==
-=== HTTPS Removal ===
+=== HTTPS Removal from Unity WebGL Games ===
 Before following these steps, write down all the '''hostnames''' of the HTTPS requests.
 <ol>

Prostagma: /* Grabbing The Game From The Internet */

2026-01-27T21:18:41Z

Grabbing The Game From The Internet

← Older revision		Revision as of 23:18, 27 January 2026
Line 15:		Line 15:
	[[File:Individual-Sprites-HTML5-example.png\|thumb\|300px\|Some games have one or more image files that act as sprite sheets, others will have each unique texture as an individual file, so make sure to get them all.]]		[[File:Individual-Sprites-HTML5-example.png\|thumb\|300px\|Some games have one or more image files that act as sprite sheets, others will have each unique texture as an individual file, so make sure to get them all.]]

	There are an extremely low number of HTML5 games that are single-asset. For multi-asset curations, you have two main options, both of which are [[Curation Tutorial#Multi-~~Asset_Games~~\|described here]], but each is more suited for different tasks which we'll explain here.		There are an extremely low number of HTML5 games that are single-asset. For multi-asset curations, you have two main options, both of which are [[Curation Tutorial#Using cURLsDownloader for Multi-Asset Games\|described here]], but each is more suited for different tasks which we'll explain here.

	Create a new curation in the Curate tab of Flashpoint and fill it out with as much information as you can, including the Launch Command you found earlier. The Platform should be <code>HTML5</code>, and the Application Path should be <code>FPSoftware\fpnavigator-portable\FPNavigator.exe</code>, referring to the Flashpoint Navigator browser used for most HTML5 games.		Create a new curation in the Curate tab of Flashpoint and fill it out with as much information as you can, including the Launch Command you found earlier. The Platform should be <code>HTML5</code>, and the Application Path should be <code>FPSoftware\fpnavigator-portable\FPNavigator.exe</code>, referring to the Flashpoint Navigator browser used for most HTML5 games.
Line 25:		Line 25:
	'''REMEMBER, ALWAYS TEST THE GAME 100%, NO MATTER HOW BIG OR SMALL!''' This is true for all games, but especially HTML5, as nearly none are single-asset, you are almost guaranteed to find a multi-asset. Because of how it works, most games will only call assets when needed, so make sure to navigate all the menus, click all the buttons, and play the game as thoroughly as possible. This may include hidden collectables, unique voice lines, downloadables, completion bonuses, etc.		'''REMEMBER, ALWAYS TEST THE GAME 100%, NO MATTER HOW BIG OR SMALL!''' This is true for all games, but especially HTML5, as nearly none are single-asset, you are almost guaranteed to find a multi-asset. Because of how it works, most games will only call assets when needed, so make sure to navigate all the menus, click all the buttons, and play the game as thoroughly as possible. This may include hidden collectables, unique voice lines, downloadables, completion bonuses, etc.

	Wayback will not save these missing assets on a normal capture, and computers/browsers tend to clear cache much more frequently for optimization, making cache dumps unlikely to yield anything, so once it's gone, it's likely gone for good. Better to catch everything first try and make sure it's not lost. For more information on multi-assets in general, [[Curation Tutorial#Multi-~~Asset_Games~~\|go here]].		Wayback will not save these missing assets on a normal capture, and computers/browsers tend to clear cache much more frequently for optimization, making cache dumps unlikely to yield anything, so once it's gone, it's likely gone for good. Better to catch everything first try and make sure it's not lost. For more information on multi-assets in general, [[Curation Tutorial#Using cURLsDownloader for Multi-Asset Games\|go here]].

	Once you've finished playing through the game, you need to make sure that all of the game's assets have actually been downloaded. To do this, first close Navigator, and clear it's cache by following [[Extended FAQ#ClearBasiliskCache\|these instructions]], then close Navigator. Next, press the <code>Run</code> button to test the game again, this time without using MAD4FP. If the game does not work, MAD4FP likely failed to download some of the required assets. Follow the instructions in the [[#Missing Assets\|Missing Assets]] section to complete the curation.		Once you've finished playing through the game, you need to make sure that all of the game's assets have actually been downloaded. To do this, first close Navigator, and clear it's cache by following [[Extended FAQ#ClearBasiliskCache\|these instructions]], then close Navigator. Next, press the <code>Run</code> button to test the game again, this time without using MAD4FP. If the game does not work, MAD4FP likely failed to download some of the required assets. Follow the instructions in the [[#Missing Assets\|Missing Assets]] section to complete the curation.

BoskoLasta: switched up the order of the alternative browsers

2024-05-26T17:28:38Z

switched up the order of the alternative browsers

← Older revision		Revision as of 19:28, 26 May 2024
Line 35:		Line 35:

	Sometimes a game that doesn't work in Navigator will show an error message. A message similar to the examples is typically a sure sign that another browser must be used for the curation. In other cases, the game may work to some degree, but certain elements may be missing or not working properly. Common issues include: the game loading with no graphics, the game's music and/or sound effects not playing, the game's controls not working, or the game experiencing lag issues not present in other browsers. Performance issues are especially common with Unity WebGL games in Navigator.		Sometimes a game that doesn't work in Navigator will show an error message. A message similar to the examples is typically a sure sign that another browser must be used for the curation. In other cases, the game may work to some degree, but certain elements may be missing or not working properly. Common issues include: the game loading with no graphics, the game's music and/or sound effects not playing, the game's controls not working, or the game experiencing lag issues not present in other browsers. Performance issues are especially common with Unity WebGL games in Navigator.

			=== Chromium ===
			Ungoogled Chromium is included in Flashpoint as a second full browser alongside Navigator, and is usually the first alternative to try when a game doesn't work in Navigator. The main limitation Chromium has over the other two browsers is that it cannot load Flash content for the few HTML5/Flash hybrid games.

			'''The Application Path for Chromium is''' <code>FPSoftware\startChrome.bat</code>.

	=== Browser Mode ===		=== Browser Mode ===
Line 40:		Line 45:

	The limitations of Browser Mode include:		The limitations of Browser Mode include:

	* Cannot open multiple tabs or windows.		* Cannot open multiple tabs or windows.
	* Doesn't support games that require webcam or microphone access.		* Doesn't support games that require webcam or microphone access.
Line 46:		Line 52:

	'''The Application Path for Browser Mode is''' <code>:browser-mode:</code>.		'''The Application Path for Browser Mode is''' <code>:browser-mode:</code>.

	~~=== Chromium ===~~
	Ungoogled Chromium is included in Flashpoint as a second full browser alongside Navigator, and is usually the first alternative to try when a game doesn't work in Navigator. The main limitation Chromium has over the other two browsers is that it cannot load Flash content for the few HTML5/Flash hybrid games.

	~~'''The Application Path for Chromium is''' <code>FPSoftware\startChrome.bat</code>.~~

	== Google Fonts Elements ==		== Google Fonts Elements ==

Cheesey: Chromium > Browser Mode

2024-05-18T17:23:44Z

Chromium > Browser Mode

← Older revision		Revision as of 19:23, 18 May 2024
Line 37:		Line 37:

	=== Browser Mode ===		=== Browser Mode ===
	Browser Mode is a way of running games using Flashpoint's launcher. It ~~is usually the first one to try~~ when a game ~~doesn't work~~ in Navigator. However, since Browser Mode is not a full web browser, it has some limitations that mean it isn't an option for all games.		Browser Mode is a way of running games using Flashpoint's launcher. It can be used when a game does not run in Navigator or Chromium. However, since Browser Mode is not a full web browser, it has some limitations that mean it isn't an option for all games.

	The limitations of Browser Mode include:		The limitations of Browser Mode include:
Line 48:		Line 48:

	=== Chromium ===		=== Chromium ===
	Ungoogled Chromium is included in Flashpoint as a second full browser alongside Navigator~~. It~~ is ~~currently not used for many games but fixes issues that~~ Navigator ~~and Browser Mode cannot~~. The main limitation Chromium has over the other two browsers is that it cannot load Flash content for the few HTML5/Flash hybrid games.		Ungoogled Chromium is included in Flashpoint as a second full browser alongside Navigator, and is usually the first alternative to try when a game doesn't work in Navigator. The main limitation Chromium has over the other two browsers is that it cannot load Flash content for the few HTML5/Flash hybrid games.

	'''The Application Path for Chromium is''' <code>FPSoftware\startChrome.bat</code>.		'''The Application Path for Chromium is''' <code>FPSoftware\startChrome.bat</code>.

Cheesey: /* Grabbing The Game From The Internet */ mentioned how to grab favicons (since using FPNavigator with MAD4FP doesn't)

2024-05-05T01:15:25Z

Grabbing The Game From The Internet: mentioned how to grab favicons (since using FPNavigator with MAD4FP doesn't)

← Older revision		Revision as of 03:15, 5 May 2024
Line 20:		Line 20:

	After inputting the launch command, use <code>Run with MAD4FP</code>, and start playing the game. [[MAD4FP]] will download any assets automatically as you play and make progress.		After inputting the launch command, use <code>Run with MAD4FP</code>, and start playing the game. [[MAD4FP]] will download any assets automatically as you play and make progress.

			If the game's webpage has a favicon (a small unique icon that appears on a webpage's browser tab), MAD4FP will not be able to grab it if you launch the game with FPNavigator. To get around this issue, use the launch command <code>FPSoftware\startChrome.bat</code> and run it with MAD4FP at least once, and that should grab the favicon file once it loads. You can then change the launch command back to FPNavigator.

	'''REMEMBER, ALWAYS TEST THE GAME 100%, NO MATTER HOW BIG OR SMALL!''' This is true for all games, but especially HTML5, as nearly none are single-asset, you are almost guaranteed to find a multi-asset. Because of how it works, most games will only call assets when needed, so make sure to navigate all the menus, click all the buttons, and play the game as thoroughly as possible. This may include hidden collectables, unique voice lines, downloadables, completion bonuses, etc.		'''REMEMBER, ALWAYS TEST THE GAME 100%, NO MATTER HOW BIG OR SMALL!''' This is true for all games, but especially HTML5, as nearly none are single-asset, you are almost guaranteed to find a multi-asset. Because of how it works, most games will only call assets when needed, so make sure to navigate all the menus, click all the buttons, and play the game as thoroughly as possible. This may include hidden collectables, unique voice lines, downloadables, completion bonuses, etc.
Line 122:		Line 124:
	#Use the <code>Rotate</code> button (the curved arrow) to test whether the game works, as some games do not allow you to play in a certain device orientation, and will load warning messages until the device is rotated.		#Use the <code>Rotate</code> button (the curved arrow) to test whether the game works, as some games do not allow you to play in a certain device orientation, and will load warning messages until the device is rotated.

	To enable Responsive Design Mode in Chromium, open the developer tools by pressing F12 and then click the icon that looks like a computer screen and cell phone to the left of the <code>Elements tab of the menu.~~</code>~~		To enable Responsive Design Mode in Chromium, open the developer tools by pressing F12 and then click the icon that looks like a computer screen and cell phone to the left of the <code>Elements</code> tab of the menu.

	Make sure to skim through the entire game where these elements might show up, like parts with game controls or menus.		Make sure to skim through the entire game where these elements might show up, like parts with game controls or menus.

Cheesey: /* Responsive Design Mode and Mobile Elements */ Mentioned how to open responsive design mode in chromium as well.

2024-05-05T01:01:03Z

Responsive Design Mode and Mobile Elements: Mentioned how to open responsive design mode in chromium as well.

← Older revision		Revision as of 03:01, 5 May 2024
Line 115:		Line 115:
	Unlike traditional plugins, HTML5 allows games to be played on both desktop devices (Windows, Mac, Linux, etc.) and mobile devices (iOS, Android, etc.). This means that some games will implement Responsive Design elements, allowing them to work better on mobile platforms. This can load new assets such as pages, scripts, elements, images, etc.		Unlike traditional plugins, HTML5 allows games to be played on both desktop devices (Windows, Mac, Linux, etc.) and mobile devices (iOS, Android, etc.). This means that some games will implement Responsive Design elements, allowing them to work better on mobile platforms. This can load new assets such as pages, scripts, elements, images, etc.

	To check whether a game has these elements, play the game both in desktop and Responsive Design Mode. Here's how to enable Responsive Design Mode in ~~Navigator~~:		To check whether a game has these elements, play the game both in desktop and Responsive Design Mode. Here's how to enable Responsive Design Mode in FPNavigator:
	#First, access the developer tools: click the menu button in the top-right corner and select <code>Developer</code>, then <code>Toggle Tools</code>, or use the shortcut Ctrl+Shift+I.		#First, access the developer tools: click the menu button in the top-right corner and select <code>Developer</code>, then <code>Toggle Tools</code>, or use the shortcut Ctrl+Shift+I.
	#A menu should appear at the bottom of the window; look for a phone icon on the right side of this menu, and click it to enable <code>Responsive Design Mode</code>. This will activate the Responsive Design menu, which will surround the game window.		#A menu should appear at the bottom of the window; look for a phone icon on the right side of this menu, and click it to enable <code>Responsive Design Mode</code>. This will activate the Responsive Design menu, which will surround the game window.
Line 121:		Line 121:
	#Make sure to reload the page after this, as these elements might not have been loaded in the default desktop mode.		#Make sure to reload the page after this, as these elements might not have been loaded in the default desktop mode.
	#Use the <code>Rotate</code> button (the curved arrow) to test whether the game works, as some games do not allow you to play in a certain device orientation, and will load warning messages until the device is rotated.		#Use the <code>Rotate</code> button (the curved arrow) to test whether the game works, as some games do not allow you to play in a certain device orientation, and will load warning messages until the device is rotated.

			To enable Responsive Design Mode in Chromium, open the developer tools by pressing F12 and then click the icon that looks like a computer screen and cell phone to the left of the <code>Elements tab of the menu.</code>

	Make sure to skim through the entire game where these elements might show up, like parts with game controls or menus.		Make sure to skim through the entire game where these elements might show up, like parts with game controls or menus.

Prostagma at 02:04, 1 April 2024

2024-04-01T02:04:59Z

← Older revision		Revision as of 04:04, 1 April 2024
Line 49:		Line 49:

	'''The Application Path for Chromium is''' <code>FPSoftware\startChrome.bat</code>.		'''The Application Path for Chromium is''' <code>FPSoftware\startChrome.bat</code>.

	~~====Microphone Support====~~
	Chromium is the only browser in Flashpoint that supports games which ask for access to the system's microphone; these games are tagged with the <code>Microphone</code> tag. However, currently, a workaround must be used to enable microphone access:
	~~#Open Chromium. Press Ctrl + T to open a new tab, and paste the following text into the URL bar: <code>chrome://flags/#unsafely-treat-insecure-origin-as-secure</code>~~
	#This should open Chromium's Flags list, particularly the flag "Insecure origins treated as secure". In the accompanying window, paste the domain of the game's Launch Command (such as <code>https://www.newgrounds.com/</code>), then change the setting from "Disabled" to "Enabled".
	~~#Click the "Relaunch" button that appears in the bottom right corner.~~
	~~Play the game in Chromium again, and it should request microphone permissions properly. An upcoming update to Flashpoint will eliminate the need for this workaround.~~

	== Google Fonts Elements ==		== Google Fonts Elements ==
Line 215:		Line 208:
	If a game that needs the camera and/or the microphone has this feature blocked by all browsers, try the steps below:		If a game that needs the camera and/or the microphone has this feature blocked by all browsers, try the steps below:
	# Run the curation on Chrome, press CTRL + T and go to <code>chrome://flags/#unsafely-treat-insecure-origin-as-secure</code> in the URL bar.		# Run the curation on Chrome, press CTRL + T and go to <code>chrome://flags/#unsafely-treat-insecure-origin-as-secure</code> in the URL bar.
	# Paste the website you need into the field (values are separated by commas) and restart the browser via the button on the corner.		# Paste the domain of website you need into the field, such as <code>https://www.newgrounds.com</code> (values are separated by commas), and restart the browser via the button on the corner.
	If this works, add the steps above in the Curation Notes field and ask staff at #curators on our Discord server to update startChrome.bat in Flashpoint's [https://gitlab.unstable.life/flashpoint/components/support-packs/common-files/chromium/-/blob/master/startChrome.bat GitLab], so the user doesn't need to manually add the website on their end.		If this works, add the steps above in the Curation Notes field and ask staff at #curators on our Discord server to update startChrome.bat in Flashpoint's [https://gitlab.unstable.life/flashpoint/components/support-packs/common-files/chromium/-/blob/master/startChrome.bat GitLab], so the user doesn't need to manually add the website on their end.

Prostagma: /* Troubleshooting */

2024-04-01T01:56:46Z

Troubleshooting

← Older revision		Revision as of 03:56, 1 April 2024
Line 147:		Line 147:

	This is a really common form of modification for HTML5 games, but it is minor enough that games with altered https requests don't really need to be marked as Hacked. Note that this rule only applies to text files (such as HTML and JS files); you must always mark a game as Hacked if you edit binary files (such as SWFs).		This is a really common form of modification for HTML5 games, but it is minor enough that games with altered https requests don't really need to be marked as Hacked. Note that this rule only applies to text files (such as HTML and JS files); you must always mark a game as Hacked if you edit binary files (such as SWFs).


	If you need to remove <code>https</code> from a Unity WebGL game/files (<code>.unityweb</code>), then follow the instructions below:		If you need to remove <code>https</code> from a Unity WebGL game/files (<code>.unityweb</code>), then follow the instructions below:
Line 212:		Line 211:

	Upload this curation to #curators on our Discord server for safekeeping, as it might be able to work in the future.		Upload this curation to #curators on our Discord server for safekeeping, as it might be able to work in the future.

			=== Camera/Microphone access ===
			If a game that needs the camera and/or the microphone has this feature blocked by all browsers, try the steps below:
			# Run the curation on Chrome, press CTRL + T and go to <code>chrome://flags/#unsafely-treat-insecure-origin-as-secure</code> in the URL bar.
			# Paste the website you need into the field (values are separated by commas) and restart the browser via the button on the corner.
			If this works, add the steps above in the Curation Notes field and ask staff at #curators on our Discord server to update startChrome.bat in Flashpoint's [https://gitlab.unstable.life/flashpoint/components/support-packs/common-files/chromium/-/blob/master/startChrome.bat GitLab], so the user doesn't need to manually add the website on their end.

	== Wrapping It Up ==		== Wrapping It Up ==

ThePowerPlayer: /* Microphone Support */

2024-04-01T01:51:33Z

Microphone Support

← Older revision		Revision as of 03:51, 1 April 2024
Line 39:		Line 39:
	The limitations of Browser Mode include:		The limitations of Browser Mode include:
	* Cannot open multiple tabs or windows.		* Cannot open multiple tabs or windows.
	* Doesn't support games that require a webcam		* Doesn't support games that require webcam or microphone access.
	* Games that require the cursor to be captured may not work properly.		* Games that require the cursor to be captured may not work properly.
	* Currently cannot be used for Alternate Applications (but may support them in the future).		* Currently cannot be used for Alternate Applications (but may support them in the future).
Line 49:		Line 49:

	'''The Application Path for Chromium is''' <code>FPSoftware\startChrome.bat</code>.		'''The Application Path for Chromium is''' <code>FPSoftware\startChrome.bat</code>.

			====Microphone Support====
			Chromium is the only browser in Flashpoint that supports games which ask for access to the system's microphone; these games are tagged with the <code>Microphone</code> tag. However, currently, a workaround must be used to enable microphone access:
			#Open Chromium. Press Ctrl + T to open a new tab, and paste the following text into the URL bar: <code>chrome://flags/#unsafely-treat-insecure-origin-as-secure</code>
			#This should open Chromium's Flags list, particularly the flag "Insecure origins treated as secure". In the accompanying window, paste the domain of the game's Launch Command (such as <code>https://www.newgrounds.com/</code>), then change the setting from "Disabled" to "Enabled".
			#Click the "Relaunch" button that appears in the bottom right corner.
			Play the game in Chromium again, and it should request microphone permissions properly. An upcoming update to Flashpoint will eliminate the need for this workaround.

	== Google Fonts Elements ==		== Google Fonts Elements ==

Syndiate.ajax: Better instructions

2023-08-05T19:03:36Z

Better instructions

← Older revision		Revision as of 21:03, 5 August 2023
Line 145:		Line 145:

	==== Unity WebGL Games ====		==== Unity WebGL Games ====

	~~'''NOTE: You may need to follow these steps for multiple <code>.unityweb</code> files in a given curation before finding the file that contains the HTTPS URLs in question.'''~~

	Before following these steps, write down all the '''hostnames''' of the HTTPS requests.		Before following these steps, write down all the '''hostnames''' of the HTTPS requests.
	<ol>		<ol>
			<li>
			First, find the <code>.unityweb</code> file that contains the HTTPS URLs. There are a few ways to find this file:
			<ul>
			<li>
			This file's filename is most likely to contain <code>Build.data</code> in it. If there is no file with that filename present, then look at the next method.
			</li>
			<li>
			There may be a <code>.json</code> file that lists several <code>.unityweb</code> files. In this case, look for the line that contains <code>dataUrl</code>, which should list the filename of the <code>.unityweb</code> file that contains the requests.
			</li>
			</ul>
			If none of these methods work, you may need to follow the following steps for multiple <code>.unityweb</code> files in a given curation before finding the file that contains the HTTPS URLs in question.
			</li>
	<li>		<li>
	Open the <code>.unityweb</code> file in WinRAR or 7-Zip. Inside the archive, there should be another <code>.unityweb</code> file with the exact same name. Extract this file out of the archive into another folder (so that you don't face filename conflictions).		Open the <code>.unityweb</code> file in WinRAR or 7-Zip. Inside the archive, there should be another <code>.unityweb</code> file with the exact same name. Extract this file out of the archive into another folder (so that you don't face filename conflictions).
	</li>		</li>
	<li>		<li>
	Open the file in any text editor, preferably Notepad++. In the editor, for each unique hostname in the HTTPS requests, replace all occurrences of <code>https://{hostname}</code> with <code>http://{hostname}/</code>. '''Note the slash at the end. This is important as the newly modified request URL MUST match the length of the original request URL.'''		Open the file in any text editor, preferably Notepad++. In the editor, for each unique hostname in the HTTPS requests, replace all occurrences of <code>https://{hostname}</code> with <code>http://{hostname}/</code>. '''Note the slash at the end. This is important as the newly modified request URL MUST match the length of the original request URL. Additionally, we must replace <code>https://</code> AND the hostname instead of just <code>https://</code>, as this is too prone to error.'''
	</li>		</li>
	<li>		<li>
	Save and close. Rename the original <code>.unityweb</code> file to its original filename with <code>_unhacked</code> at the end (to preserve the original, unhacked file), and move the newly modified file to the same directory as the unhacked file. You can now relaunch the game and your HTTPS requests ~~will~~ have been changed to HTTP requests!		Save and close. Rename the original <code>.unityweb</code> file to its original filename with <code>_unhacked</code> at the end (to preserve the original, unhacked file), and move the newly modified file to the same directory as the unhacked file. You can now relaunch the game and your HTTPS requests should have been changed to HTTP requests!
	</li>		</li>
	</ol>		</ol>
			If some HTTPS requests are still happening, first clear your cache to ensure that the changes have been applied. If they're ''still'' happening, you need to do additional searching for HTTPS URLs in the <code>.unityweb</code> file, as sometimes, some request URLs are not fully listed (i.e. a request URL may be listed as <code>ttps://{request URL}</code> instead of <code>https://{request URL}</code>), although this is relatively rare.

	=== Missing Assets ===		=== Missing Assets ===