Vitalize Curation - Revision history

Prostagma: v12 cleanup

2023-07-16T02:39:58Z

v12 cleanup

← Older revision		Revision as of 04:39, 16 July 2023
Line 1:		Line 1:
	This guide will show you how to curate Vitalize using Flashpoint ~~Core~~.		This guide will show you how to curate Vitalize using Flashpoint.

	== Before You Start ==		== Before You Start ==
Line 16:		Line 16:

	==Curation Steps==		==Curation Steps==
	Follow the [[Curation Format]] to add metadata for your game and create its correct content folder. The Platform should be <code>Vitalize</code> and the Application Path should be <code>FPSoftware\~~Basilisk~~-~~Portable~~\~~Basilisk-Portable~~.exe</code>.		Follow the [[Curation Format]] to add metadata for your game and create its correct content folder. The Platform should be <code>Vitalize</code> and the Application Path should be <code>FPSoftware\fpnavigator-portable\FPNavigator.exe</code>.

	* If running the bare .ccn file, link to the <code>.ccn</code> file, for example <code>http://www.angelfire.com/indie/mojofltr/games/attack.htm</code>.		* If running the bare .ccn file, link to the <code>.ccn</code> file, for example <code>http://www.angelfire.com/indie/mojofltr/games/attack.htm</code>.

Prostagma: /* Wrapping It Up */

2021-07-14T17:24:49Z

Wrapping It Up

← Older revision		Revision as of 19:24, 14 July 2021
Line 22:		Line 22:

	==Wrapping It Up==		==Wrapping It Up==
	When you're finished testing, export the curation and name the .7z file with the name of the app, and submit it to the #other-game-curations channel of the Flashpoint Discord, or #animation-curations if it's an animation. Use the Vitalize emoji when submitting.		{{:Wrapping It Up}}

	<noinclude>		<noinclude>
	[[Category:Curation Guides]]		[[Category:Curation Guides]]
	</noinclude>		</noinclude>

Childishbeat: Improved

2021-06-18T14:54:58Z

Improved

← Older revision		Revision as of 16:54, 18 June 2021
Line 11:		Line 11:

	==Notes==		==Notes==
	Before you begin, keep in mind some software titles may ask to update extensions. These are often a single MOX file (COX for v2 titles), or DLL files in some cases. Downloading these straight from the URL is unlikely to work outside DLL files, but copying the plugin from another version is possible in many cases. However, changing the file extension to the other is necessary if copying COX or MOX files from or to the v2 folder, and v2 titles are ~~likely~~ to crash to the splash screen when calling for the extensions outside the initial loading process. If these extension updates are not saved, the title will not work. However, if an EXE version exists, as is the case with Lollipop Eater X (available [https://dsxcorner.com/download.htm here]), [https://dsxcorner.com/code.htm the Vitalize version of which] looks for <code>www.clickteam.com/vitalize4/extensions/sv1/v4u/onu.mox</code>, it may be possible to extract any necessary files. If they are, submit them to the Flashpoint Discord in a .7z file in either of the two ways:		Before you begin, keep in mind some software titles may ask to update extensions. These are often a single MOX file (COX for v2 titles), or DLL files in some cases. Downloading these straight from the URL is unlikely to work outside DLL files, but copying the plugin from another version is possible in many cases. However, changing the file extension to the other is necessary if copying COX or MOX files from or to the v2 folder, and v2 titles are unlikely to work properly. For example, some titles crash to the splash screen when calling for the extensions outside the initial loading process. If these extension updates are not saved, the title will not work. However, if an EXE version exists, as is the case with Lollipop Eater X (available [https://dsxcorner.com/download.htm here]), [https://dsxcorner.com/code.htm the Vitalize version of which] looks for <code>www.clickteam.com/vitalize4/extensions/sv1/v4u/onu.mox</code>, it may be possible to extract any necessary files, though in practise, it is not. If they are, submit them to the Flashpoint Discord in a .7z file in either of the two ways:
	# Add them to the file directories <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v</code>, one for each necessary version number (for example, <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v4</code>) in the .7z file, then submit it to the #pending-fixes channel of the Flashpoint Discord.		# Add them to the file directories <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v</code>, one for each necessary version number (for example, <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v4</code>) in the .7z file, then submit it to the #pending-fixes channel of the Flashpoint Discord.
	# Submit them along with the Vitalize version. See [[#Wrapping It Up]] for more information.		# Submit them along with the Vitalize version. See [[#Wrapping It Up]] for more information.
Line 18:		Line 18:
	Follow the [[Curation Format]] to add metadata for your game and create its correct content folder. The Platform should be <code>Vitalize</code> and the Application Path should be <code>FPSoftware\Basilisk-Portable\Basilisk-Portable.exe</code>.		Follow the [[Curation Format]] to add metadata for your game and create its correct content folder. The Platform should be <code>Vitalize</code> and the Application Path should be <code>FPSoftware\Basilisk-Portable\Basilisk-Portable.exe</code>.

	* If running the bare .ccn file, link to the <code>.ccn</code> file, for example <code>http://www.angelfire.com/~~mech~~/~~crisalo~~/~~Games~~/~~Crisalo~~.~~ccn~~</code>.		* If running the bare .ccn file, link to the <code>.ccn</code> file, for example <code>http://www.angelfire.com/indie/mojofltr/games/attack.htm</code>.
	* If running the .ccn file embedded, link to the URL of the page where it's located~~. It can be a simple URL like~~ <code>http://www.angelfire.com</code>, ~~or it~~ can ~~link to the~~ <code>~~.htm~~</code> or ~~<code>.html</code> file for~~ the ~~page~~, for example <code>http://www.angelfire.com~~/mech/crisalo/Games/Crisalo.ccn~~</code>.		* If running the .ccn file embedded, link to the URL of the page where it's located, for example <code>http://www.angelfire.com/indie/mojofltr/Games/attack.htm</code>. If you can't find this page, you can use something like <code>http://localvitalize</code>, or the original website URL, for example <code>http://www.angelfire.com</code>.

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

Childishbeat: Some parts more concise, v2 crashes highlighted, made clear to submit the curation only one of the ways.

2021-06-14T09:30:29Z

Some parts more concise, v2 crashes highlighted, made clear to submit the curation only one of the ways.

← Older revision		Revision as of 11:30, 14 June 2021
Line 11:		Line 11:

	==Notes==		==Notes==
	Before you begin, keep in mind some software titles may ask to update extensions. ~~Much of the time, these~~ are ~~files with the~~ file ~~extension MOX, or~~ COX for v2 titles, ~~but are~~ DLL files in some cases. Downloading these straight from the URL ~~does not~~ work ~~in the vast majority of cases~~, but copying the plugin from another version is possible in many cases. However, changing the file extension to the other ~~may be~~ necessary. If these extension updates are not saved, the title will not work. However, if an EXE version exists, as is the case with Lollipop Eater X (available [https://dsxcorner.com/download.htm here]), [https://dsxcorner.com/code.htm the Vitalize version of which] looks for <code>www.clickteam.com/vitalize4/extensions/sv1/v4u/onu.mox</code>, it may be possible to extract ~~the~~ necessary ~~.mox~~ files. If they are, submit them to the Flashpoint Discord in a .7z file in two ways:		Before you begin, keep in mind some software titles may ask to update extensions. These are often a single MOX file (COX for v2 titles), or DLL files in some cases. Downloading these straight from the URL is unlikely to work outside DLL files, but copying the plugin from another version is possible in many cases. However, changing the file extension to the other is necessary if copying COX or MOX files from or to the v2 folder, and v2 titles are likely to crash to the splash screen when calling for the extensions outside the initial loading process. If these extension updates are not saved, the title will not work. However, if an EXE version exists, as is the case with Lollipop Eater X (available [https://dsxcorner.com/download.htm here]), [https://dsxcorner.com/code.htm the Vitalize version of which] looks for <code>www.clickteam.com/vitalize4/extensions/sv1/v4u/onu.mox</code>, it may be possible to extract any necessary files. If they are, submit them to the Flashpoint Discord in a .7z file in either of the two ways:
	# Add them to the file directories <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v</code>, one for each necessary version number (for example, <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v4</code>) in the .7z file, then submit it to the #pending-fixes channel of the Flashpoint Discord.		# Add them to the file directories <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v</code>, one for each necessary version number (for example, <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v4</code>) in the .7z file, then submit it to the #pending-fixes channel of the Flashpoint Discord.
	# Submit them along with the Vitalize version. See [[#Wrapping It Up]] for more information.		# Submit them along with the Vitalize version. See [[#Wrapping It Up]] for more information.

Childishbeat: I've found Vitalize curations can be fixed by copying extensions from other versions, changing file extensions if the file extension used by the Vitalize version is different. This article reflects what I've found while curating.

2021-06-11T06:13:09Z

I've found Vitalize curations can be fixed by copying extensions from other versions, changing file extensions if the file extension used by the Vitalize version is different. This article reflects what I've found while curating.

← Older revision		Revision as of 08:13, 11 June 2021
Line 11:		Line 11:

	==Notes==		==Notes==
	Before you begin, keep in mind some software titles may ask to update extensions. ~~These~~ are files with the file extension .~~mox. Some Vitalize titles do~~ not work ~~due~~ to these extension updates not ~~being~~ saved. However, if ~~a .exe~~ version ~~of the title~~ exists, as is the case with Lollipop Eater X (available [https://dsxcorner.com/download.htm here]), the Vitalize version of which looks for <code>www.clickteam.com/vitalize4/extensions/sv1/v4u/onu.mox</code>, it may be possible to extract the necessary .mox files. If ~~you do~~, ~~you can~~ submit them to the Flashpoint Discord in a .7z file in two ways:		Before you begin, keep in mind some software titles may ask to update extensions. Much of the time, these are files with the file extension MOX, or COX for v2 titles, but are DLL files in some cases. Downloading these straight from the URL does not work in the vast majority of cases, but copying the plugin from another version is possible in many cases. However, changing the file extension to the other may be necessary. If these extension updates are not saved, the title will not work. However, if an EXE version exists, as is the case with Lollipop Eater X (available [https://dsxcorner.com/download.htm here]), [https://dsxcorner.com/code.htm the Vitalize version of which] looks for <code>www.clickteam.com/vitalize4/extensions/sv1/v4u/onu.mox</code>, it may be possible to extract the necessary .mox files. If they are, submit them to the Flashpoint Discord in a .7z file in two ways:
	# Add them to the file directories <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v</code>, one for each necessary version number (for example, <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v4</code>) in the .7z file, then submit it to the #pending-fixes channel of the Flashpoint Discord.		# Add them to the file directories <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v</code>, one for each necessary version number (for example, <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v4</code>) in the .7z file, then submit it to the #pending-fixes channel of the Flashpoint Discord.
	# Submit them along with the Vitalize version. See [[#Wrapping It Up]] for more information.		# Submit them along with the Vitalize version. See [[#Wrapping It Up]] for more information.

Prostagma at 15:47, 29 January 2021

2021-01-29T15:47:26Z

← Older revision		Revision as of 17:47, 29 January 2021
Line 23:		Line 23:
	==Wrapping It Up==		==Wrapping It Up==
	When you're finished testing, export the curation and name the .7z file with the name of the app, and submit it to the #other-game-curations channel of the Flashpoint Discord, or #animation-curations if it's an animation. Use the Vitalize emoji when submitting.		When you're finished testing, export the curation and name the .7z file with the name of the app, and submit it to the #other-game-curations channel of the Flashpoint Discord, or #animation-curations if it's an animation. Use the Vitalize emoji when submitting.

			<noinclude>
			[[Category:Curation Guides]]
			</noinclude>

Childishbeat: /* Wrapping It Up */ The typo in #animation-curations has been fixed.

2020-11-12T19:35:54Z

Wrapping It Up: The typo in #animation-curations has been fixed.

← Older revision		Revision as of 21:35, 12 November 2020
Line 22:		Line 22:

	==Wrapping It Up==		==Wrapping It Up==
	When you're finished testing, export the curation and name the .7z file with the name of the app, and submit it to the #other-game-curations channel of the Flashpoint Discord, or #~~animations~~-curations if it's an animation. Use the Vitalize emoji when submitting.		When you're finished testing, export the curation and name the .7z file with the name of the app, and submit it to the #other-game-curations channel of the Flashpoint Discord, or #animation-curations if it's an animation. Use the Vitalize emoji when submitting.

Childishbeat: /* Notes */ The first point is more clear.

2020-11-07T08:16:57Z

Notes: The first point is more clear.

← Older revision		Revision as of 10:16, 7 November 2020
Line 12:		Line 12:
	==Notes==		==Notes==
	Before you begin, keep in mind some software titles may ask to update extensions. These are files with the file extension .mox. Some Vitalize titles do not work due to these extension updates not being saved. However, if a .exe version of the title exists, as is the case with Lollipop Eater X (available [https://dsxcorner.com/download.htm here]), the Vitalize version of which looks for <code>www.clickteam.com/vitalize4/extensions/sv1/v4u/onu.mox</code>, it may be possible to extract the necessary .mox files. If you do, you can submit them to the Flashpoint Discord in a .7z file in two ways:		Before you begin, keep in mind some software titles may ask to update extensions. These are files with the file extension .mox. Some Vitalize titles do not work due to these extension updates not being saved. However, if a .exe version of the title exists, as is the case with Lollipop Eater X (available [https://dsxcorner.com/download.htm here]), the Vitalize version of which looks for <code>www.clickteam.com/vitalize4/extensions/sv1/v4u/onu.mox</code>, it may be possible to extract the necessary .mox files. If you do, you can submit them to the Flashpoint Discord in a .7z file in two ways:
	# ~~Put~~ the file directories <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v</code>, one for each necessary version number (for example, <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v4</code>) in the .7z file, then submit it to the #pending-fixes channel of the Flashpoint Discord.		# Add them to the file directories <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v</code>, one for each necessary version number (for example, <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v4</code>) in the .7z file, then submit it to the #pending-fixes channel of the Flashpoint Discord.
	# Submit them along with the Vitalize version. See [[#Wrapping It Up]] for more information.		# Submit them along with the Vitalize version. See [[#Wrapping It Up]] for more information.

Childishbeat: The possibility of extracting .mox files to find them and where from is discussed.

2020-11-07T08:15:18Z

The possibility of extracting .mox files to find them and where from is discussed.

← Older revision		Revision as of 10:15, 7 November 2020
Line 11:		Line 11:

	==Notes==		==Notes==
	Before you begin, keep in mind some software titles may ask to update extensions. These are files with the file extension .mox. Some Vitalize titles ~~may~~ not work due to these extension updates not being saved.		Before you begin, keep in mind some software titles may ask to update extensions. These are files with the file extension .mox. Some Vitalize titles do not work due to these extension updates not being saved. However, if a .exe version of the title exists, as is the case with Lollipop Eater X (available [https://dsxcorner.com/download.htm here]), the Vitalize version of which looks for <code>www.clickteam.com/vitalize4/extensions/sv1/v4u/onu.mox</code>, it may be possible to extract the necessary .mox files. If you do, you can submit them to the Flashpoint Discord in a .7z file in two ways:
			# Put the file directories <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v</code>, one for each necessary version number (for example, <code>FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v4</code>) in the .7z file, then submit it to the #pending-fixes channel of the Flashpoint Discord.
			# Submit them along with the Vitalize version. See [[#Wrapping It Up]] for more information.

	==Curation Steps==		==Curation Steps==

404 11: Added download button

2020-11-05T02:04:13Z

Added download button

← Older revision		Revision as of 04:04, 5 November 2020
Line 5:		Line 5:

	==Recognizing Vitalize==		==Recognizing Vitalize==
			[[File:Vitalbutton.gif\|frame\|Plug-in download button, this one being from when Vitalize! belonged to Corel.]]
	Vitalize content files use the .ccn file extension. When entering a page with Vitalize content, these are some ways to find the location of the file:		Vitalize content files use the .ccn file extension. When entering a page with Vitalize content, these are some ways to find the location of the file:
	# Right-click the page and click "View Page Source" (or alternatively, use the keyboard shortcut Ctrl+U), then look for an <code>object</code> or <code>embed</code> tag with a link to the content file.		# Right-click the page and click "View Page Source" (or alternatively, use the keyboard shortcut Ctrl+U), then look for an <code>object</code> or <code>embed</code> tag with a link to the content file.