[DiscordArchive] With how much the NPCBots changes, would there be any issues converting an existing server to Tricke
[DiscordArchive] With how much the NPCBots changes, would there be any issues converting an existing server to Tricke
Original source
With how much the NPCBots changes, would there be any issues converting an existing server to Trickerer's fork or does it need to be on a completely new build? And if so, I guess I would just need to backup the character database to save the progress we've made?
rektbyfaith
06-20-2023, 05:11 PM #1Archived author: Dreathean • Posted: 2023-06-20T17:11:43.161000+00:00
Original source
With how much the NPCBots changes, would there be any issues converting an existing server to Trickerer's fork or does it need to be on a completely new build? And if so, I guess I would just need to backup the character database to save the progress we've made?
Original source
You should always back it up regardless so you're safe in case of issues. I don't think you should switch from the official repository to his repository without doing a clean build. You could apply the included npcbots.patch to your existing code, which of course also allows you to update whenever you feel like it instead of waiting for him to merge the official repository into his fork.
rektbyfaith
06-20-2023, 05:23 PM #2Archived author: Revision • Posted: 2023-06-20T17:23:09.132000+00:00
Original source
You should always back it up regardless so you're safe in case of issues. I don't think you should switch from the official repository to his repository without doing a clean build. You could apply the included npcbots.patch to your existing code, which of course also allows you to update whenever you feel like it instead of waiting for him to merge the official repository into his fork.
Original source
As far as I know, he merges it every Saturday. It's not always great if there are important fixes.
rektbyfaith
06-20-2023, 05:23 PM #3Archived author: Revision • Posted: 2023-06-20T17:23:49.904000+00:00
Original source
As far as I know, he merges it every Saturday. It's not always great if there are important fixes.
Original source
A full backup of the auth and characters databases, frequently enough, is a good safety for many, many reasons.
rektbyfaith
06-20-2023, 05:25 PM #4Archived author: Revision • Posted: 2023-06-20T17:25:03.474000+00:00
Original source
A full backup of the auth and characters databases, frequently enough, is a good safety for many, many reasons.
Original source
Yeah it's just me and my friend so I typically do a backup every other session
rektbyfaith
06-20-2023, 05:28 PM #5Archived author: Dreathean • Posted: 2023-06-20T17:28:53.440000+00:00
Original source
Yeah it's just me and my friend so I typically do a backup every other session
Original source
That's good.
rektbyfaith
06-20-2023, 05:29 PM #6Archived author: Revision • Posted: 2023-06-20T17:29:22.494000+00:00
Original source
That's good.
Original source
With the npcbots.patch method, if he were to make any updates then I would just apply an updated patch from his end? And otherwise continue updating like normal from the official repository with my current setup? And I should be able to apply the patch to my current build? (will backup like you said just in case I do run into any issues)
rektbyfaith
06-20-2023, 05:35 PM #7Archived author: Dreathean • Posted: 2023-06-20T17:35:01.237000+00:00
Original source
With the npcbots.patch method, if he were to make any updates then I would just apply an updated patch from his end? And otherwise continue updating like normal from the official repository with my current setup? And I should be able to apply the patch to my current build? (will backup like you said just in case I do run into any issues)
Original source
You would apply the patch again. I honestly don't know if you can straight up do it without resetting the source first but in that case it's as easy as `git reset origin/master`, you might have to do `git reset --hard origin/master` though. Keep in mind that it will reset *everything* to what the master is so only ever use it if you don't have any custom changes done. Performing a reset and applying the patch again wouldn't need a clean build, just do the steps and build (without cleaning it) and it should be fine.
rektbyfaith
06-20-2023, 05:38 PM #8Archived author: Revision • Posted: 2023-06-20T17:38:08.882000+00:00
Original source
You would apply the patch again. I honestly don't know if you can straight up do it without resetting the source first but in that case it's as easy as `git reset origin/master`, you might have to do `git reset --hard origin/master` though. Keep in mind that it will reset *everything* to what the master is so only ever use it if you don't have any custom changes done. Performing a reset and applying the patch again wouldn't need a clean build, just do the steps and build (without cleaning it) and it should be fine.
Original source
All this is exactly why I forked AC, added a branch to it to simplify things, added the trickerer repo that's already applied with npcbots as a remote and just merge his repo into my fork when I update it all.
rektbyfaith
06-20-2023, 05:41 PM #9Archived author: Revision • Posted: 2023-06-20T17:41:11.241000+00:00
Original source
All this is exactly why I forked AC, added a branch to it to simplify things, added the trickerer repo that's already applied with npcbots as a remote and just merge his repo into my fork when I update it all.
Original source
When you say custom changes I assume you're referring to code changes? My changes generally just extend to .conf files changes/custom modules
rektbyfaith
06-20-2023, 05:43 PM #10Archived author: Dreathean • Posted: 2023-06-20T17:43:23.465000+00:00
Original source
When you say custom changes I assume you're referring to code changes? My changes generally just extend to .conf files changes/custom modules