KKS port and project code merge #9
No reviewers
Labels
No labels
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
question
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
IllusionMods/Stiletto!9
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "kks-port-merge"
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?
Hi,
Just:
Did not look in depth into Stiletto_KKS since the code is so different it was easier to work on the Stiletto code base.
I don't use Studio so no testing there. It seems to work fine in KKS.
For the method OnHeelInfoUpdate had to use try {} block. It gives and error the second time you invoke Maker in the same
game session. Don't have KK installed for testing this change in the code for KK. Though logic dictates that the problem should be present in KK also. The nullchecks fix if active will permit the plug-in to continue to run as is the case in KKS.
Thank you for the PR! The changes look good overall, just some minor issues to button up.
If you are going with the KK codebase, are you sure the KKS version didn't have anything worth keeping? e.g. fixes or UI changes.
@ -0,0 +171,4 @@MakerHeelInfoProcess(heel => StilettoContext.CustomHeelProvider.Save(heel.heelName, new CustomHeel(heel))));button_Reload.OnClick.AddListener(StilettoContext.ReloadConfigurations);Wouldn't using InsideAndLoaded fix this issue? A blank catch is not great because it will hide unexpected issues, at least log the exceptions once caught.
You can also use
MakerAPI.MakerExitingto clean up any hooks or fields that were set when entering maker so that you return to the clean initial state.@ -0,0 +1,10 @@using System.Runtime.InteropServices;Assembly version is not set. It's better to move AssemblyInfo into the shared project and have both game versions share the same file.
@ -0,0 +1,165 @@<?xml version="1.0" encoding="utf-8"?>There are some inconsistent settings between KK and KKS projects, nothing major.
@ -0,0 +1,165 @@<?xml version="1.0" encoding="utf-8"?>I work this and look into the KKS that is quite different. There was some recent work done one the KK branch that why I pick that one.
@ -0,0 +171,4 @@MakerHeelInfoProcess(heel => StilettoContext.CustomHeelProvider.Save(heel.heelName, new CustomHeel(heel))));button_Reload.OnClick.AddListener(StilettoContext.ReloadConfigurations);Yes this does fix the issue.
@ -0,0 +1,10 @@using System.Runtime.InteropServices;Addressed this the way I usually do on my projects
Properties/StilettoInfo.cs
I have a name for debug Stiletto (Debug) to make it easier to now if version is released by mistake.
@ -0,0 +1,165 @@<?xml version="1.0" encoding="utf-8"?>Also did a fast check on the Stiletto_KKS project the code is to different. Right now I won't be able to do a good analysis to see what code base is more efficient. I won't promise anything but I'll try to make time.
Just a fast check the code for the Stiletto_KKS compiles as is for KK but I can't test if it works in KK.
Alright, let me know when it's ready for a review.
Nice work! I'm happy to give it a try on KK and see if anything is obviously broken.
No obvious breakage in about an hour of testing in both KK and KKS (mostly KK). I'll try to do some additional testing in the next few days, but so far LGTM.
Tested in KK for another couple hours, no issues connected to this PR. I did find a bug in the shoe warp feature, but I'm 90% sure that's a bug in master branch that I accidentally introduced while optimizing that feature at the last minute, not this PR's fault -- I'll send in a PR to fix that after this PR is merged, so that we don't have to deal with merge conflicts.
@IDontHaveIdea is there anything you still need to do before this gets merged?
@Splendide-Imaginarius I merged it since the issues appear to have been resolved. Feel free to send PRs now :)