OnexExplorer
OnexExplorer copied to clipboard
Standardize patching archives to easily replace things in .NOS files
Hi,
As we discussed earlier, I think we should provide some kind of standardized way to have "patching archives"
Those patching archives should be available for :
- Images/Sprites
- .dat files
- whatever that is related to client files
I think we should have a designed tool to :
- Facilitate patching archive generation
- Facilitate patching archive application
Here is the "directory structure" I already thought about :
./
- manifest.json
- {nostaleFileName}
- randomFileName.fileExtension
- randomFileName.fileExtension
- randomFileName.fileExtension
We will have to clarify how the manifest.json should be architectured as well
{
"author": "",
"project-name": "wings-blabla",
"version": "1.0.0",
"files": [
{
// todo, i'm looking for the different use cases we could have for different files
}
]
}