Closed Roadcrosser closed 3 years ago
I also found this same error in the #69 issue, so I'm unsure if my version is actually outdated.
Digging through the code, it looks like this error came about because the CivModCore database config was commented out, despite the config itself saying uncommenting it was a bad idea. I wonder if I'm doing something wrong here.
I populated the db info with my namelayer db and it seems to work fine now.
Should I have seperate dbs for CivModCore, Namelayer and Citadel or can they all be the same db?
As far as I know they can be either same or separate DBs, but I do not have the most recent knowledge of changes made.
On Thu, Feb 11, 2021 at 12:16 AM Roadcrosser notifications@github.com wrote:
Digging through the code, it looks like this error came about because the CivModCore database config was commented out, despite the config itself saying uncommenting it was a bad idea. I wonder if I'm doing something wrong here.
I populated the db info with my namelayer db and it seems to work fine now.
Should I have seperate dbs for CivModCore, Namelayer and Citadel or can they all be the same db?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/DevotedMC/Citadel/issues/71#issuecomment-777207770, or unsubscribe https://github.com/notifications/unsubscribe-auth/AADD5DSVC4JO73J2WW3RMNTS6NR2PANCNFSM4XHK67NA .
I grabbed Citadel 4.1.1 off the CI for MC 1.16.5 (I hope I got the right version) and got this error:
This was after I uncommented the database lines in the Citadel config that point to the namelayer database (I did try making a seperate database for citadel at some point, though I think that was a mistake so I undid that).
(I'm also using MariaDB instead, if that's relevant)
Leaving those lines commented produces an error about migrations, I'll post the exact error for that if that's relevant.
Full log is here: