[DiscordArchive] client 3.3.5a and default azerothcore?
[DiscordArchive] client 3.3.5a and default azerothcore?
Original source
The logical thing to do is to remove modules, starting with individual progression, to see if it starts working again.
rektbyfaith
07-04-2024, 08:12 PM #11Archived author: Revision • Posted: 2024-07-04T20:12:39.608000+00:00
Original source
The logical thing to do is to remove modules, starting with individual progression, to see if it starts working again.
Original source
if the client aint the problem i would by disabling all modules
rektbyfaith
07-04-2024, 08:13 PM #12Archived author: bash • Posted: 2024-07-04T20:13:01.001000+00:00
Original source
if the client aint the problem i would by disabling all modules
Original source
and try again
rektbyfaith
07-04-2024, 08:13 PM #13Archived author: bash • Posted: 2024-07-04T20:13:03.407000+00:00
Original source
and try again
Original source
You can start by disable them in the config files, if that doesnt work. Move them from ur env folder and rebuild preferable recompile just to be sure.
rektbyfaith
07-04-2024, 08:14 PM #14Archived author: bash • Posted: 2024-07-04T20:14:16.527000+00:00
Original source
You can start by disable them in the config files, if that doesnt work. Move them from ur env folder and rebuild preferable recompile just to be sure.
Original source
If that works u might wanna make ur your using the lastest version of every repo, core and modules
rektbyfaith
07-04-2024, 08:15 PM #15Archived author: bash • Posted: 2024-07-04T20:15:24.048000+00:00
Original source
If that works u might wanna make ur your using the lastest version of every repo, core and modules
Original source
double check with 'git status' you dont have any unwanted changes by accident locally
rektbyfaith
07-04-2024, 08:15 PM #16Archived author: bash • Posted: 2024-07-04T20:15:48.791000+00:00
Original source
double check with 'git status' you dont have any unwanted changes by accident locally
Original source
another approach might be doing the following: in every repo, azerothcore and underlaying modules. Use the following command 'git reset --hard origin/<branchYourUsing>'. Be ware it will remove all local changes, so might wanna make copy of ur env folders or possible custom core/mod changes before doing that
rektbyfaith
07-04-2024, 08:17 PM #17Archived author: bash • Posted: 2024-07-04T20:17:48.237000+00:00
Original source
another approach might be doing the following: in every repo, azerothcore and underlaying modules. Use the following command 'git reset --hard origin/<branchYourUsing>'. Be ware it will remove all local changes, so might wanna make copy of ur env folders or possible custom core/mod changes before doing that
Original source
then followed with ./acore compiler all
rektbyfaith
07-04-2024, 08:18 PM #18Archived author: bash • Posted: 2024-07-04T20:18:03.838000+00:00
Original source
then followed with ./acore compiler all
Original source
Since i cant find the error in core code, possible in one of mod codebases? When found remove that module, update whatever test it
rektbyfaith
07-04-2024, 08:21 PM #19Archived author: bash • Posted: 2024-07-04T20:21:05.728000+00:00
Original source
Since i cant find the error in core code, possible in one of mod codebases? When found remove that module, update whatever test it
Original source
Yeah or just remove one module at a time to see if it gets fixed instead of making it over-complicated right out of the gate.
rektbyfaith
07-04-2024, 08:24 PM #20Archived author: Revision • Posted: 2024-07-04T20:24:06.252000+00:00
Original source
Yeah or just remove one module at a time to see if it gets fixed instead of making it over-complicated right out of the gate.
1 Guest(s)
1 Guest(s)