[DiscordArchive] I fixed my issue with the playerbots.conf.dist and removed the .dist after the server was already ma
[DiscordArchive] I fixed my issue with the playerbots.conf.dist and removed the .dist after the server was already ma
Original source
I fixed my issue with the playerbots.conf.dist and removed the .dist after the server was already made. Once fixed, I got off for the night as it was late. Seems the server is looking for the .dist at the end still.
What do I do to fix? Run CMake and that's it? Or what all is needed, and will it lose anything progress related?
rektbyfaith
06-23-2025, 03:23 AM #1Archived author: BootlessFawn007 • Posted: 2025-06-23T03:23:58.520000+00:00
Original source
I fixed my issue with the playerbots.conf.dist and removed the .dist after the server was already made. Once fixed, I got off for the night as it was late. Seems the server is looking for the .dist at the end still.
What do I do to fix? Run CMake and that's it? Or what all is needed, and will it lose anything progress related?
Original source
-- I just added .dist back to it after editing and it works. Technically I can just keep changing it back to edit and back again to .dist to play, correct? Seems if that's the easy way, I'm good with that
rektbyfaith
06-23-2025, 03:26 AM #2Archived author: BootlessFawn007 • Posted: 2025-06-23T03:26:33.458000+00:00
Original source
-- I just added .dist back to it after editing and it works. Technically I can just keep changing it back to edit and back again to .dist to play, correct? Seems if that's the easy way, I'm good with that
Original source
The .conf.dist files are for defaults and shouldn't usually be edited directly for changing settings. Instead, you'd make a copy of the file in the same location and without the .dist and edit that .conf file instead.
Also, the conf files for modules are found in two places after you build the server with them. Ignore the ones within the module folders themselves (like `azerothcore-wotlk\modules\mod-playerbots\conf\playerbots.conf.dist`), and instead go to `azerothcore-wotlk\env\dist\etc\modules\` where you'll find copies of the .conf.dist files for all the modules in your build. That's where you should copy the playerbots.conf.dist to make a playerbots.conf in the same location for changing settings in it.
rektbyfaith
06-23-2025, 05:38 AM #3Archived author: Spargel • Posted: 2025-06-23T05:38:53.024000+00:00
Original source
The .conf.dist files are for defaults and shouldn't usually be edited directly for changing settings. Instead, you'd make a copy of the file in the same location and without the .dist and edit that .conf file instead.
Also, the conf files for modules are found in two places after you build the server with them. Ignore the ones within the module folders themselves (like `azerothcore-wotlk\modules\mod-playerbots\conf\playerbots.conf.dist`), and instead go to `azerothcore-wotlk\env\dist\etc\modules\` where you'll find copies of the .conf.dist files for all the modules in your build. That's where you should copy the playerbots.conf.dist to make a playerbots.conf in the same location for changing settings in it.
Original source
Got it, thank you. Next question, I add a module and rebuild the server in Visual Studio and them use CMake? like I did originally, correct?
rektbyfaith
06-23-2025, 05:40 AM #4Archived author: BootlessFawn007 • Posted: 2025-06-23T05:40:49.589000+00:00
Original source
Got it, thank you. Next question, I add a module and rebuild the server in Visual Studio and them use CMake? like I did originally, correct?
Original source
Yeah, whenever you'd add or remove a module, or change anything in the source somewhere, you build again for it to affect the new version. Editing .conf files should go into effect with just a server restart.
rektbyfaith
06-23-2025, 05:41 AM #5Archived author: Spargel • Posted: 2025-06-23T05:41:37.075000+00:00
Original source
Yeah, whenever you'd add or remove a module, or change anything in the source somewhere, you build again for it to affect the new version. Editing .conf files should go into effect with just a server restart.
Original source
Note that 'rebuild' is specifically a thing, you should instead just repeat the 'build' after the change unless you get errors. If you actually use rebuild every time, it'll add unnecessary time and work.
rektbyfaith
06-23-2025, 05:43 AM #6Archived author: Spargel • Posted: 2025-06-23T05:43:12.661000+00:00
Original source
Note that 'rebuild' is specifically a thing, you should instead just repeat the 'build' after the change unless you get errors. If you actually use rebuild every time, it'll add unnecessary time and work.
Original source
Ok, to make sure I have this, I wanna ensure I don't mess it up bad enough to lose it or something.
I clone the repo to the module folder and follow whatever steps it says for the module. Then, go into VS to 'rebuild' the ALL_BUILD. Then, go to CMake to Compile and Generate?
rektbyfaith
06-23-2025, 05:46 AM #7Archived author: BootlessFawn007 • Posted: 2025-06-23T05:46:56.841000+00:00
Original source
Ok, to make sure I have this, I wanna ensure I don't mess it up bad enough to lose it or something.
I clone the repo to the module folder and follow whatever steps it says for the module. Then, go into VS to 'rebuild' the ALL_BUILD. Then, go to CMake to Compile and Generate?
Original source
other way around, first cmake, then build
rektbyfaith
06-23-2025, 05:47 AM #8Archived author: Tereneckla • Posted: 2025-06-23T05:47:20.842000+00:00
Original source
other way around, first cmake, then build
Original source
Oh, right, my bad
rektbyfaith
06-23-2025, 05:48 AM #9Archived author: BootlessFawn007 • Posted: 2025-06-23T05:48:40.583000+00:00
Original source
Oh, right, my bad
Original source
I dunno, personally. It's simpler to do with WSL in my opinion, so I'm not familiar with the VS specific steps.
rektbyfaith
06-23-2025, 05:49 AM #10Archived author: Spargel • Posted: 2025-06-23T05:49:21.346000+00:00
Original source
I dunno, personally. It's simpler to do with WSL in my opinion, so I'm not familiar with the VS specific steps.
1 Guest(s)
1 Guest(s)