Vitalize Curation: Difference between revisions
Childishbeat (talk | contribs) (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.) |
Childishbeat (talk | contribs) (Some parts more concise, v2 crashes highlighted, made clear to submit the curation only one of the ways.) |
||
| Line 11: | Line 11: | ||
==Notes== | ==Notes== | ||
Before you begin, keep in mind some software titles may ask to update extensions. | 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. | ||
Revision as of 10:30, 14 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
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
objectorembedtag 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
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 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. 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
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. - 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.
- If running the bare .ccn file, link to the
.ccnfile, for examplehttp://www.angelfire.com/mech/crisalo/Games/Crisalo.ccn. - If running the .ccn file embedded, link to the URL of the page where it's located. It can be a simple URL like
http://www.angelfire.com, or it can link to the.htmor.htmlfile for the page, for examplehttp://www.angelfire.com/mech/crisalo/Games/Crisalo.ccn.
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.