Difference between revisions of "Vitalize Curation"

From Flashpoint Database
Jump to: navigation, search
m
(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.)
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.

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

  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

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.