Me and my team were just wondering if there is an easier/safer way to keep our modifications to Dialogue System's source code (or any other library, really) every time we update it.
We added and changed a few lines of code, but we have to remember/rewrite them whenever we update the plugin to its latest version. Our current "method" is to add a specific comment beside every altered line such as "// CUSTOMIZED" to serve as kind of a tag, so we can CTRL+F them and take note before updating and rewriting them. But we feel like there's maybe a tool or something we're not aware of that could make this process easier.
Recommended way to update plugin without losing modifications to source?
Re: Recommended way to update plugin without losing modifications to source?
Hi,
The best way is to let me know what makes the direct code modifications necessary so I can add hooks instead. That way you can add your own code (e.g., C# events, subclasses, etc.) instead of directly modifying source code.
Barring that, the only realistic, but ugly, solution is global search for that special CUSTOMIZED comment.
The best way is to let me know what makes the direct code modifications necessary so I can add hooks instead. That way you can add your own code (e.g., C# events, subclasses, etc.) instead of directly modifying source code.
Barring that, the only realistic, but ugly, solution is global search for that special CUSTOMIZED comment.
Re: Recommended way to update plugin without losing modifications to source?
Yeah, that makes sense. Will talk with my team about it, thanks for clarifying that for us!
Re: Recommended way to update plugin without losing modifications to source?
Glad to help! If your team comes up with any hooks or methods that could be changed to virtual, let me know.