[DiscordArchive] is it a death knight specifically starting at level 55 or does that happen to every class?
[DiscordArchive] is it a death knight specifically starting at level 55 or does that happen to every class?
Original source
<@200677690838220800>TrinityCore rev. e3d375571a49+ 2022-07-29 21:28:06 +0000 (npcbots_3.3.5 branch) (Unix, RelWithDebInfo, Static)
rektbyfaith
07-31-2022, 01:39 PM #11Archived author: Krutok • Posted: 2022-07-31T13:39:14.543000+00:00
Original source
<@200677690838220800>TrinityCore rev. e3d375571a49+ 2022-07-29 21:28:06 +0000 (npcbots_3.3.5 branch) (Unix, RelWithDebInfo, Static)
Original source
2022-07-30 > 2022-07-29
rektbyfaith
07-31-2022, 01:39 PM #12Archived author: Tea • Posted: 2022-07-31T13:39:36.608000+00:00
Original source
2022-07-30 > 2022-07-29
Original source
just saying
rektbyfaith
07-31-2022, 01:39 PM #13Archived author: Tea • Posted: 2022-07-31T13:39:38.194000+00:00
Original source
just saying
Original source
<@200677690838220800>micha@clangaming:~/TrinityCore-3.3.5-with-NPCBots$ git pull
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint:
hint: git config pull.rebase false # merge (the default strategy)
hint: git config pull.rebase true # rebase
hint: git config pull.ff only # fast-forward only
hint:
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
Already up to date.
micha@clangaming:~/TrinityCore-3.3.5-with-NPCBots
rektbyfaith
07-31-2022, 01:40 PM #14Archived author: Krutok • Posted: 2022-07-31T13:40:19.978000+00:00
Original source
<@200677690838220800>micha@clangaming:~/TrinityCore-3.3.5-with-NPCBots$ git pull
hint: Pulling without specifying how to reconcile divergent branches is
hint: discouraged. You can squelch this message by running one of the following
hint: commands sometime before your next pull:
hint:
hint: git config pull.rebase false # merge (the default strategy)
hint: git config pull.rebase true # rebase
hint: git config pull.ff only # fast-forward only
hint:
hint: You can replace "git config" with "git config --global" to set a default
hint: preference for all repositories. You can also pass --rebase, --no-rebase,
hint: or --ff-only on the command line to override the configured default per
hint: invocation.
Already up to date.
micha@clangaming:~/TrinityCore-3.3.5-with-NPCBots
Original source
up to date
rektbyfaith
07-31-2022, 01:40 PM #15Archived author: Krutok • Posted: 2022-07-31T13:40:31.736000+00:00
Original source
up to date
Original source
that "TrinityCore-3.3.5-with-NPCBots" repo might be, but its not using latest "3.3.5"
rektbyfaith
07-31-2022, 01:40 PM #16Archived author: Tea • Posted: 2022-07-31T13:40:50.689000+00:00
Original source
that "TrinityCore-3.3.5-with-NPCBots" repo might be, but its not using latest "3.3.5"
Original source
just because we fixed it in our main repo doesnt mean all forks automatically get that fix
rektbyfaith
07-31-2022, 01:41 PM #17Archived author: Tea • Posted: 2022-07-31T13:41:12.133000+00:00
Original source
just because we fixed it in our main repo doesnt mean all forks automatically get that fix
Original source
the fact is that the bug exists with my repo
rektbyfaith
07-31-2022, 01:41 PM #18Archived author: Krutok • Posted: 2022-07-31T13:41:59.884000+00:00
Original source
the fact is that the bug exists with my repo
Original source
if you need a fix right away you'll need to add the actual trinitycore remote and do the merge yourself, or tell whoever maintains your fork to update
rektbyfaith
07-31-2022, 01:42 PM #19Archived author: <o> • Posted: 2022-07-31T13:42:35.532000+00:00
Original source
if you need a fix right away you'll need to add the actual trinitycore remote and do the merge yourself, or tell whoever maintains your fork to update
Original source
the bug was introduced just a few days ago, and was fixed yesterday
rektbyfaith
07-31-2022, 01:43 PM #20Archived author: <o> • Posted: 2022-07-31T13:43:06.444000+00:00
Original source
the bug was introduced just a few days ago, and was fixed yesterday
1 Guest(s)
1 Guest(s)