Flash Curation - Revision history

Coldice2: reading logs with powershell

2026-02-09T18:08:42Z

reading logs with powershell

← Older revision		Revision as of 20:08, 9 February 2026
Line 120:		Line 120:
	</ol>		</ol>


			You can read the flash logs using Powershell continuously like so:<pre>
			get-content "$env:APPDATA\Macromedia\Flash Player\Logs\flashlog.txt" -wait
			</pre>If you need to clear the flash log files you can do it so in Powershell<pre>
			set-content -path "$env:APPDATA\Macromedia\Flash Player\Logs\flashlog.txt" ""
			</pre>
	== Using HTML Embed Codes ==		== Using HTML Embed Codes ==

Coldice2: external link for helping with flash debug

2026-02-09T18:00:47Z

external link for helping with flash debug

← Older revision		Revision as of 20:00, 9 February 2026
Line 98:		Line 98:
	Flashpoint Navigator will now load the debug plugin instead of the standard plugin. To undo this, just revert the same line of <code>FPNavigator.ini</code>.		Flashpoint Navigator will now load the debug plugin instead of the standard plugin. To undo this, just revert the same line of <code>FPNavigator.ini</code>.

	=== Using the Flashlog ===		=== Using the Flashlog - debugging ===

	The debug player is also useful for advanced tasks such as reimplementing game servers or recreating missing XML assets, where you need more info about what data the game expects to receive. Often in these cases, the info you need will be contained in a warning message, not an error. To see log/warning messages and more detailed errors, you will need to activate the flashlog by creating an <code>mm.cfg</code> file in your user folder:		The debug player is also useful for advanced tasks such as reimplementing game servers or recreating missing XML assets, where you need more info about what data the game expects to receive. Often in these cases, the info you need will be contained in a warning message, not an error. To see log/warning messages and more detailed errors, you will need to activate the flashlog by creating an <code>mm.cfg</code> file in your user folder following the guide below. See also this document if you are stuck https://docs.unity3d.com/450/Documentation/Manual/flash-debugging.html
	<ol>		<ol>
	<li>		<li>

Coldice2 at 20:03, 19 January 2026

2026-01-19T20:03:52Z

← Older revision		Revision as of 22:03, 19 January 2026
Line 1:		Line 1:
			See also [[Flash]]

	This page goes over some of the advanced techniques specific to Flash curation. If you know of any advanced tips and tricks for curating Flash games, please add a section to this article!		This page goes over some of the advanced techniques specific to Flash curation. If you know of any advanced tips and tricks for curating Flash games, please add a section to this article!

Al 2712: Updated Flash embed attributes link to a working Wayback Machine link

2025-10-12T04:28:25Z

Updated Flash embed attributes link to a working Wayback Machine link

← Older revision		Revision as of 06:28, 12 October 2025
Line 157:		Line 157:
	Next, replace the width and height in the template embed code with the SWF width and height that you just found. Finally, replace <code>example.swf</code> with the filename of your SWF.		Next, replace the width and height in the template embed code with the SWF width and height that you just found. Finally, replace <code>example.swf</code> with the filename of your SWF.

	You can also add or change additional properties of the embed as desired. [https://helpx.adobe.com/flash/kb/flash-object-embed-tag-attributes.html See this page] for a reference of those properties.		You can also add or change additional properties of the embed as desired. [https://web.archive.org/web/20230208173231/https://helpx.adobe.com/flash/kb/flash-object-embed-tag-attributes.html See this page] for a reference of those properties.

	Once you have your embed code, complete the curation by following [[#Using HTML Embed Codes\|steps 5-9 above]].		Once you have your embed code, complete the curation by following [[#Using HTML Embed Codes\|steps 5-9 above]].

NanerBag: Fixed typos and clarified the format and the wording in various places.

2024-08-26T18:14:22Z

Fixed typos and clarified the format and the wording in various places.

Show changes

NanerBag: /* Identifying Flash Deviations */

2024-08-26T17:28:30Z

Identifying Flash Deviations

← Older revision		Revision as of 19:28, 26 August 2024
Line 269:		Line 269:
	==== Identifying Flash Deviations ====		==== Identifying Flash Deviations ====

	Due to DeviantArt being primarily an art site, and the fact that after the flash kill switch there is no clear indication of what deviation may have originally been a flash file or not, it is often difficult to find flash deviations in a gallery unless the preview made by the author indicates ~~that~~. Other ways of identifying flash deviations are:		Due to DeviantArt being primarily an art site, and the fact that after the flash kill switch there is no clear indication of what deviation may have originally been a flash file or not, it is often difficult to find flash deviations in a gallery unless the preview made by the author indicates so. Other ways of identifying flash deviations are:
	* Links to other flash portals like Newgrounds, Kongregate, or a dedicated site for the content, or links to file hosting services like Google Drive or Dropbox. The deviation sometimes only serves to advertise the game on those platforms. Additionally, DeviantArt allows uploading archive files, which could mean that games could be included.		* Links to other flash portals like Newgrounds, Kongregate, or a dedicated site for the content, or links to file hosting services like Google Drive or Dropbox. The deviation sometimes only serves to advertise the game on those platforms. Additionally, DeviantArt allows uploading archive files, which could mean that games could be included in those.
	* Tags like "swf", "flash", "game".		* Tags like "swf", "flash", "game".
	* Word of mouth from the comments.		* Word of mouth from the comments.
	* The <code>originalFile</code> object which is only accessibly in the page source as part of other JSON data. This object holds information like the file dimensions, size, and the type (extension), but only the file dimensions and file size are displayed normally. This tends to be the best way to determine whether an undownloadble deviation is or is not a swf. Not to be confused with the <code>content</code> object accessible via the DeviantArt API, which has the metadata for the deviation preview, not the original file.		* The <code>originalFile</code> object which is only accessibly in the page source as part of other JSON data. This object holds information like the file dimensions, size, and the type (extension), but only the file dimensions and file size are displayed normally. This tends to be the best way to determine whether an undownloadble deviation is or is not a swf. Not to be confused with the <code>content</code> object accessible via the DeviantArt API, which has the metadata for the deviation preview, not the original file.
	: '''Note: There are rare cases where the author has changed the content of the deviation to another file, in this case <code>originalFile</code> will reflect that change. This content change was not done retroactively by DeviantArt on the flash kill switch, it must be done manually by the author, which makes it exceedingly unlikely to happen.'''		: '''Note: There are very rare cases where the author has changed the content of the deviation to another file, in this case <code>originalFile</code> will reflect that change. This content change was not done retroactively by DeviantArt on the flash kill switch, it must be done manually by the author, which makes it exceedingly unlikely to happen.'''

	Currently unviable ~~means~~ to identify flash deviations:		Currently unviable ways to identify flash deviations:
	* DeviantArt categories were a mechanism for authors to to categorize deviations in a hierarchy of ranging specificity. One of these categories was <code>flash</code> and its corresponding categories <code>flash/animations</code>, <code>flash/interactive</code>, etc., these are still accessible through the DeviantArt API, but all category information always returns an empty string as of version <code>20240701</code> despite no mentions of such in the changelog. It is unknown whether this is a bug or whether they are being phased out.		* DeviantArt categories were a mechanism for authors to categorize deviations in a hierarchy of ranging specificity. One of these categories was <code>flash</code> and its corresponding categories <code>flash/animations</code>, <code>flash/interactive</code>, etc., these are still accessible through the DeviantArt API, but all category information always returns an empty string as of version <code>20240701</code> despite no mentions of such in the changelog. Using earlier versions of the API does not fix this. It is unknown whether this is a bug or whether they are being phased out.

	==== Finding Deviations on the Wayback Machine ====		==== Finding Deviations on the Wayback Machine ====

NanerBag: Rewrote whole DeviantArt section to match newfound knowledge about the orig link format and bruteforcing. Plus some nice info about identifying flash deviations.

2024-08-26T11:25:12Z

Rewrote whole DeviantArt section to match newfound knowledge about the orig link format and bruteforcing. Plus some nice info about identifying flash deviations.

Show changes

NanerBag: /* DeviantArt */

2024-07-21T12:42:13Z

DeviantArt

← Older revision		Revision as of 14:42, 21 July 2024
Line 288:		Line 288:
	The orig links adhere to the following format with the following properties:		The orig links adhere to the following format with the following properties:
	<pre>https://orig<0-15>.deviantart.net/<*>/f/<year>/<day>/<First-Character-Of-Filename>/<Second-Character-Of-Filename>/<filename></pre>		<pre>https://orig<0-15>.deviantart.net/<*>/f/<year>/<day>/<First-Character-Of-Filename>/<Second-Character-Of-Filename>/<filename></pre>
	* <code><*></code> is any sequence of characters. Any sequence of characters will work, regardless of link, but you will usually only find <code>fs70`</code> or <code>fs71</code>.		* <code><*></code> is any sequence of characters. Any sequence of characters will work, regardless of link, but you will usually only find <code>fs70</code> or <code>fs71</code>.
	* <code><filename></code> tends to be an UUID with the deviations ID as stored in the [https://www.deviantart.com/developers/console/deviation/deviation_single/bcc296bdf3b5e40636825a942a514816 DeviantArt API] intermixed. The deviation ID can be gotten from the page search of any deviation by searching for <code>da:appurl</code>, which will look something like this <code>DeviantArt://deviation/0054B61D-14A0-D601-E2D4-F4CF496FB8CB</code>, where <code>0054B61D-14A0-D601-E2D4-F4CF496FB8CB</code> is the deviation ID as recognized by the API. It is not known how this the UUID in the orig link filename can be reverse engineered without any deviation snapshots. Additionally, it has been observed to change across time between snapshots, presumably due to backends changes. On rare occasions, this filename will be the <code>prettyName</code> property in the page source of the deviation.		* <code><filename></code> tends to be an UUID with the deviations ID as stored in the [https://www.deviantart.com/developers/console/deviation/deviation_single/bcc296bdf3b5e40636825a942a514816 DeviantArt API] intermixed. The deviation ID can be gotten from the page search of any deviation by searching for <code>da:appurl</code>, which will look something like this <code>DeviantArt://deviation/0054B61D-14A0-D601-E2D4-F4CF496FB8CB</code>, where <code>0054B61D-14A0-D601-E2D4-F4CF496FB8CB</code> is the deviation ID as recognized by the API. It is not known how this the UUID in the orig link filename can be reverse engineered without any deviation snapshots. Additionally, it has been observed to change across time between snapshots, presumably due to backends changes. On rare occasions, this filename will be the <code>prettyName</code> property in the page source of the deviation.
	* <code><year></code> and <code><day></code> seem related to the upload date of the deviation, but they too have changed across time together with the <code><filename></code>. As of yet they don't seem to necessarily be related with the upload date of the deviation in any logical way.		* <code><year></code> and <code><day></code> seem related to the upload date of the deviation, but they too have changed across time together with the <code><filename></code>. As of yet they don't seem to necessarily be related with the upload date of the deviation in any logical way.

NanerBag: /* DeviantArt */

2024-07-21T12:41:51Z

DeviantArt

← Older revision		Revision as of 14:41, 21 July 2024
Line 287:		Line 287:

	The orig links adhere to the following format with the following properties:		The orig links adhere to the following format with the following properties:
	<pre~~><code~~>https://orig<0-15>.deviantart.net/<*>/f/<year>/<day>/<First-Character-Of-Filename>/<Second-Character-Of-Filename>/<filename~~></code~~></pre>		<pre>https://orig<0-15>.deviantart.net/<*>/f/<year>/<day>/<First-Character-Of-Filename>/<Second-Character-Of-Filename>/<filename></pre>
	* <code><*></code> is any sequence of characters. Any sequence of characters will work, regardless of link, but you will usually only find <code>fs70`</code> or <code>fs71</code>.		* <code><*></code> is any sequence of characters. Any sequence of characters will work, regardless of link, but you will usually only find <code>fs70`</code> or <code>fs71</code>.
	* <code><filename></code> tends to be an UUID with the deviations ID as stored in the [https://www.deviantart.com/developers/console/deviation/deviation_single/bcc296bdf3b5e40636825a942a514816 DeviantArt API] intermixed. The deviation ID can be gotten from the page search of any deviation by searching for <code>da:appurl</code>, which will look something like this <code>DeviantArt://deviation/0054B61D-14A0-D601-E2D4-F4CF496FB8CB</code>, where <code>0054B61D-14A0-D601-E2D4-F4CF496FB8CB</code> is the deviation ID as recognized by the API. It is not known how this the UUID in the orig link filename can be reverse engineered without any deviation snapshots. Additionally, it has been observed to change across time between snapshots, presumably due to backends changes. On rare occasions, this filename will be the <code>prettyName</code> property in the page source of the deviation.		* <code><filename></code> tends to be an UUID with the deviations ID as stored in the [https://www.deviantart.com/developers/console/deviation/deviation_single/bcc296bdf3b5e40636825a942a514816 DeviantArt API] intermixed. The deviation ID can be gotten from the page search of any deviation by searching for <code>da:appurl</code>, which will look something like this <code>DeviantArt://deviation/0054B61D-14A0-D601-E2D4-F4CF496FB8CB</code>, where <code>0054B61D-14A0-D601-E2D4-F4CF496FB8CB</code> is the deviation ID as recognized by the API. It is not known how this the UUID in the orig link filename can be reverse engineered without any deviation snapshots. Additionally, it has been observed to change across time between snapshots, presumably due to backends changes. On rare occasions, this filename will be the <code>prettyName</code> property in the page source of the deviation.

NanerBag at 13:38, 20 July 2024

2024-07-20T13:38:22Z

← Older revision		Revision as of 15:38, 20 July 2024
Line 288:		Line 288:
	The orig links adhere to the following format with the following properties:		The orig links adhere to the following format with the following properties:
	<pre><code>https://orig<0-15>.deviantart.net/<*>/f/<year>/<day>/<First-Character-Of-Filename>/<Second-Character-Of-Filename>/<filename></code></pre>		<pre><code>https://orig<0-15>.deviantart.net/<*>/f/<year>/<day>/<First-Character-Of-Filename>/<Second-Character-Of-Filename>/<filename></code></pre>
	* <code><*></code> is any sequence of characters, but you will usually only find <code>fs70`</code> or <code>fs71</code>.		* <code><*></code> is any sequence of characters. Any sequence of characters will work, regardless of link, but you will usually only find <code>fs70`</code> or <code>fs71</code>.
	* <code><filename></code> tends to be an UUID with the deviations ID as stored in the [https://www.deviantart.com/developers/console/deviation/deviation_single/bcc296bdf3b5e40636825a942a514816 DeviantArt API] intermixed. The deviation ID can be gotten from the page search of any deviation by searching for <code>da:appurl</code>, which will look something like this <code>DeviantArt://deviation/0054B61D-14A0-D601-E2D4-F4CF496FB8CB</code>, where <code>0054B61D-14A0-D601-E2D4-F4CF496FB8CB</code> is the deviation ID as recognized by the API. It is not known how this the UUID in the orig link filename can be reverse engineered without any deviation snapshots. Additionally, it has been observed to change across time between snapshots, presumably due to backends changes. On rare occasions, this filename will be the <code>prettyName</code> property in the page source of the deviation.		* <code><filename></code> tends to be an UUID with the deviations ID as stored in the [https://www.deviantart.com/developers/console/deviation/deviation_single/bcc296bdf3b5e40636825a942a514816 DeviantArt API] intermixed. The deviation ID can be gotten from the page search of any deviation by searching for <code>da:appurl</code>, which will look something like this <code>DeviantArt://deviation/0054B61D-14A0-D601-E2D4-F4CF496FB8CB</code>, where <code>0054B61D-14A0-D601-E2D4-F4CF496FB8CB</code> is the deviation ID as recognized by the API. It is not known how this the UUID in the orig link filename can be reverse engineered without any deviation snapshots. Additionally, it has been observed to change across time between snapshots, presumably due to backends changes. On rare occasions, this filename will be the <code>prettyName</code> property in the page source of the deviation.
	* <code><year></code> and <code><day></code> seem related to the upload date of the deviation, but they too have changed across time together with the <code><filename></code>. As of yet they don't seem to necessarily be related with the upload date of the deviation in any logical way.		* <code><year></code> and <code><day></code> seem related to the upload date of the deviation, but they too have changed across time together with the <code><filename></code>. As of yet they don't seem to necessarily be related with the upload date of the deviation in any logical way.