Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

VPU Remix Patching Support #584

Open
jasoncross opened this issue Nov 9, 2024 · 6 comments
Open

VPU Remix Patching Support #584

jasoncross opened this issue Nov 9, 2024 · 6 comments
Labels
fixed This issue is fixed but not yet shipped.

Comments

@jasoncross
Copy link

As more table updates (especially the cabinet mod updates by LoadedWeapon) are using the VPU Remix System, it would be great to integrate this functionality with VPin Studio.

https://vpuniverse.com/files/file/2581-vpuremix-system-vppatching-system-vpx-only/

Potentially useful would be to store the mod file separately so it could be automatically reapplied when the base VPX file is updated.

@syd711
Copy link
Owner

syd711 commented Nov 9, 2024

image

It is already implemented, but the 3.10 release takes a bit longer than usual ;)

@jasoncross
Copy link
Author

jasoncross commented Nov 9, 2024

Sweet! Does it retain the patch to repatch if the base table updates?

@syd711
Copy link
Owner

syd711 commented Nov 9, 2024

Depends on the option you choose, cloning will create a new copy and leaves the original untouched.

@jasoncross
Copy link
Author

Sorry, let me clarify. Let's say I patched the VPW version of Diner with the cabinet mod, and then VPW releases an update? I assume I would need to re-patch. Just think how cool it would be if the patch files were retained via the VPinStudio so the patch could be automatically re-applied to the updated version?

@syd711
Copy link
Owner

syd711 commented Nov 9, 2024

Ah, I see. No, right now we do not manage any assets files that have been downloaded, so these patch files are handled like any other asset.
But we are planing the improve the drop-in folder so that after an installation, files are moved from the drop-in folder into a configurable backup folder.

@syd711 syd711 added the fixed This issue is fixed but not yet shipped. label Nov 9, 2024
@Ltek
Copy link

Ltek commented Nov 10, 2024

@syd711 suggestions for DIFF file mgmt:

Naming... TableName_DIFF.ZIP
... helps users and Studio know which DIFFs are in use

Storing the ZIP'd DIFFs...
Directly in the tables folder
-or-
In an 'Active Table Patches' folder in the root of the Tables folder

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
fixed This issue is fixed but not yet shipped.
Projects
None yet
Development

No branches or pull requests

3 participants