NSPack Switch: Difference between revisions

Revision as of 05:35, 7 Haziran 2023

NSPack is a simple GUI tool to build NSP packages and NCA contents, using an embedded hacPack executable.

There are some basic elements you need to provide at least to be able to make a NSP:

Title ID	16 hex characters (example: 0100CAFE1234BEEF) - any title ID should work.
Name	The title's name, which will be the same for all the languages.
Author	The author/developer's name, which will also be the same for all the languages.
Version	The version string (1.0.0, 2.0beta1), limited to 16 characters.
Product code	A simple code string (SMO's product code: LA-H-AAACA), no matter what does it have.
ExeFS directory	Any title needs to have a ExeFS, which contains the compiled source code and the metadata NPDM.
Icon	Provide any icon, as it will be resized to 256x256, otherwise the defaut one will be used. It's recommended to use an image which is 256x256 or bigger.

Apart from those, there are some other optional features to add or customize:

RomFS	The directory containing extra files for the title.
Logo	The custom PNG and GIF images which are shown when booting a title.
Support HTML / Important / IPNotices	This three are legal information HTML documents, which can be accessed from the home menu.
Offline HTML	This HTML documents are useless when making homebrew NSPs, but can be used (if you know how) to make your own video players...
Screenshots	Will the title allow taking screenshots?
Video	Will the title allow recording gameplay?
User account	Will the title ask for a user account when booting it?

You can also save the assets as a asset file (*.nsxml format) if you are going to use that as a template for making NSPs.

Installing and running NSPs can get you banned. Although this NSPs are not titlekey-encrypted, using them can be dangerous.
If the NSP doesn't run on your console, it can be for various reasons: used a title ID which is smallet than the NPDM's max title ID, not using a correct key generation.
Don't try building titles which ask for a user, because they could fail as generated NSPs don't ask for a user.
For the build process the program creates a temporary directory on the same folder as the EXE. Don't try messing up with that folder or deleting it while *the NSP making process, because it could crash the program. Anyway, reopening the program should reset the directory.
As this program is made using WPF, it won't probably work on any other OSs but Windows (Wine supports WinForms but doesn't support WPF).

v2.0 2018/11/03

Fixed Offline HTML and custom logo, they didn't work properly work.
Huge UI redesign, now with a gray-purple theme.
Added NCA building support, for control, program, legalinfo and offline NCA types.
Added new NSP options: screenshot, video capture, startup user account.
Fixed data size and data journal size, now building retail games should work.

v0.1.1 2018/10/05

Quick internal fixes were done, assembly information was edited.. and that's it.
Any bugs you find, please comment them! Your feedback is really important.

v0.1 2018/10/04

Making NSPs from ExeFS, RomFS, custom logo, legal info (important, ipnotices and support HTML) and offline HTML documents.
Auto image patching (submit any size image, it will be converted to a 256x256 JPEG).
be the same for all the 16 languages.
You also need to provide a keyset file, which can be browsed within the UI. Only keys required: header_key, key_area_key_application_XX (for any supported key generation).

@@ Line 52: / Line 52: @@
 | The custom PNG and GIF images which are shown when booting a title.
 |-
-| Important / IPNotices / Support HTML
+| Support HTML / Important / IPNotices
 | This three are legal information HTML documents, which can be accessed from the home menu.
 |-