Backporting Wani's mod interface #249
Loading…
x
Reference in New Issue
Block a user
No description provided.
Delete Branch "wani_mod_menu"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
I am reaching levels of 'Fuck it' I haven't done before.
This backports all of Wani's nice mod UI and control to Snoot since the engine update now allows us to take advantage of it. I haven't tested any mod or made any sample mods to try it out, but anyone (especially interested modders) should give it a whirl to test for bugs. UI is a bit slap dash, I'll improve it later.
Also, I'm fixing conflicting properties in screens besides the mod menu, using
config.check_conflicting_properties
. Should this be forced on on release?WIP: Backporting Wani's mod interfaceto Backporting Wani's mod interfaceOnly comment I have is that mods that don't use rpym files shouldn't be able to be enabled/disabled since that would do nothing and it might give users a false sense of security and, although this comment also applies to Wani, this issue is going to be way more prevalent in Snoot due to missing a mod uploader that does to conversion to rpym for them.
But this is already implemented. Mods that soley use rpy files don't have the buttons for managing the mods appear.
Here's Moon Princess, only change I did was create a metadata.json, did not change a single rpy into an rpym and it's 'Scripts' list is empty
New commits pushed, approval review dismissed automatically according to repository settings