Posts: 3,659
Threads: 143
Joined: Aug 2009
Staff roles: Server Manager Coding Dev Moderator
(07-05-2020, 03:04 AM)Volgrim Wrote:
(07-05-2020, 03:01 AM)Alex. Wrote:
(07-05-2020, 02:58 AM)Volgrim Wrote:
(07-05-2020, 02:51 AM)Alex. Wrote: Suggest you just apply your changes over the top of disco, resolving any conflicts between official changes and yours as they come up. Otherwise what you want is a hard fork of disco, in which case I suggest not using the disco launcher to run your game.
And how would I go about that? The only way to make changes is to edit the files directly and upon a new patch they're just replaced with new files anyway, so even if I just added my changes as seperate entries and commented out the built-in ones (which would be a pain in the ass to do, anyway, since I edit at least one aspect of EVERY ship), it would still get reverted because it just patches in a whole new file.
Just apply the same diff?
It takes a good 3+ hours of editing, checking, double-checking and further minor edits to completely change it to how my server is run.. it's not a process I enjoy repeating (nor do I always remember the EXACT settings I had), and there's no way to automate the changes (and if there is, it's beyond me).
Why are you doing it by hand every time if it takes 3+ hours? You effectively just want to do the equivalent of a git rebase?
Anyway that sounds like a big enough change to warrant splitting from Discovery properly, not continuing to apply our updates - consider not using our launcher if it's causing problems?