[DiscordArchive] This happens with default configs?
[DiscordArchive] This happens with default configs?
Original source
This happens with default configs?
rektbyfaith
02-19-2023, 03:45 PM #1Archived author: Rngbeast • Posted: 2023-02-19T15:45:04.844000+00:00
Original source
This happens with default configs?
Original source
I'm using two builds in testing currently: both use the master branch posted from the git link above, one excludes the solo prog module and the other includes it
rektbyfaith
02-19-2023, 03:46 PM #2Archived author: VerboseLamp • Posted: 2023-02-19T15:46:58.435000+00:00
Original source
I'm using two builds in testing currently: both use the master branch posted from the git link above, one excludes the solo prog module and the other includes it
Original source
they *are* however sharing the same database
rektbyfaith
02-19-2023, 03:47 PM #3Archived author: VerboseLamp • Posted: 2023-02-19T15:47:11.992000+00:00
Original source
they *are* however sharing the same database
Original source
so if there's something in the world table that could be causing it, it's possible solo prog might have made sql changes that would be causing the issue to show up on the "clean" build
rektbyfaith
02-19-2023, 03:48 PM #4Archived author: VerboseLamp • Posted: 2023-02-19T15:48:17.558000+00:00
Original source
so if there's something in the world table that could be causing it, it's possible solo prog might have made sql changes that would be causing the issue to show up on the "clean" build
1 Guest(s)
1 Guest(s)