Difference between revisions of "Vitalize Curation"

From Flashpoint Database
Jump to: navigation, search
(Please note there may be more information that could be added to this tutorial.)
 
m (Wrapping It Up)
 
(11 intermediate revisions by 4 users not shown)
Line 5: Line 5:
  
 
==Recognizing Vitalize==
 
==Recognizing Vitalize==
When entering a page with Vitalize content, right-click the page and click "View Page Source" (or alternatively, use the keyboard shortcut Ctrl+Shift+I), then look for an <code>object</code> or <code>embed</code> tag with a link to the content file. Vitalize content files use the .ccn file extension.
+
[[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:
 +
# 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 "Inspect Element" (or alternatively, use the keyboard shortcut Ctrl+Shift+I), then click "Network", then refresh the page. If a .ccn file appears, click on it in the list, and a link to the file will be available.
  
 
==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 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.
 +
# Submit them along with the Vitalize version. See [[#Wrapping It Up]] for more information.
  
 
==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\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==
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 if it's an animation. Use the Vitalize emoji when submitting.
+
{{:Wrapping It Up}}
 +
<noinclude>
 +
[[Category:Curation Guides]]
 +
</noinclude>

Latest revision as of 18:24, 14 July 2021

This guide will show you how to curate Vitalize using Flashpoint Core.

Before You Start

This tutorial will assume you've read the standard Curation Tutorial, which is highly recommended to go through.

Recognizing Vitalize

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:

  1. Right-click the page and click "View Page Source" (or alternatively, use the keyboard shortcut Ctrl+U), then look for an object or embed tag with a link to the content file.
  2. Right-click the page and click "Inspect Element" (or alternatively, use the keyboard shortcut Ctrl+Shift+I), then click "Network", then refresh the page. If a .ccn file appears, click on it in the list, and a link to the file will be available.

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 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 here), the Vitalize version of which looks for www.clickteam.com/vitalize4/extensions/sv1/v4u/onu.mox, 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:

  1. Add them to the file directories FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v, one for each necessary version number (for example, FPSoftware\BrowserPlugins\Vitalize\Clickteam\Vitalize\v4) in the .7z file, then submit it to the #pending-fixes channel of the Flashpoint Discord.
  2. Submit them along with the Vitalize version. See #Wrapping It Up for more information.

Curation Steps

Follow the Curation Format to add metadata for your game and create its correct content folder. The Platform should be Vitalize and the Application Path should be FPSoftware\Basilisk-Portable\Basilisk-Portable.exe.

Wrapping It Up

First, make sure that you have thoroughly tested your curation and followed the Curation Format. Scroll down in the Curate tab and click the Export button at the bottom of your curation to save it as a .7z file. After you've exported the curation, you can find it by clicking the Exported Curations button on the Curate tab (as long as you didn't choose to save it somewhere else). Once you have the file, submit it to the Flashpoint Submission System. An explanation of how the site works is available here.

After you have uploaded your curation to the website, a Curator will check it. This can take some time, so please be patient. You will be pinged in the #fpfss-notifications channel about whether or not your submission was approved, and if any changes need to be made.

Congratulations! Your submitted game/animation will appear in the next version of Flashpoint.