TrinityCore#🛡・434
Aug 31, 2026 · 19:46
Really kinda disappointing that Cata is not as popular as others. Like, the option is go play Whitemane for Cata Classic, but without ANY of the quality of life stuff and extra content that Classic added, orrrrrrrrrrrr "Suffer" lol.
Aug 31, 2026 · 19:47
You would get support for cata_classic
Aug 31, 2026 · 19:47
I considered Cata classic as well, but as discussed earlier in this channel, that's also abandoned. https://discord.com/channels/376073286427344897/376457068506382336/1522293709838745661
Aug 31, 2026 · 19:49
Well, cata_classic gets atm some updates from Ovah and Im still into fixxing cata stuff on master which will be picked to classic
Aug 31, 2026 · 19:49
But idk how long the "gets updates" continues ^^
Aug 31, 2026 · 19:51
Gotcha. Then I guess, what would I need in order to set up and need around in a Cata Classic build? And, ultimately, what are/would the pros and cons be for 442 Classic vs 434+Eluna?
Aug 31, 2026 · 19:52
Well, cata_classic is ofc more sandbox then 434. But in terms of future the client is more "future proof" ^^
Aug 31, 2026 · 19:54
A bit of content is allready ported by me to classic (Westfall, first few quests of Gilneas) but I didnt touched dungeons and raids yet to port over.
Aug 31, 2026 · 19:59
Oh and ofc classes are not scripted in classic^^
Aug 31, 2026 · 20:00
and you need a legit client. that shitpile that this pserver trash whitemane ships is incomplete
Aug 31, 2026 · 22:33
Gotcha
Aug 31, 2026 · 22:34
So, how much has actually been done in og-cata so far? Have any of the dungeons or raids been set up?
Aug 31, 2026 · 23:54
I guess mainly I want to know if i'm just, genuinely wasting my time. My server concept kinda is just raid-focused, so if they're not even remotely working.., i'm kinda screwed...
Sep 01, 2026 · 05:39
they are not. If you want things fixed - don't wait until someone else does it, get to work
Sep 01, 2026 · 10:34
Makes sense. So, are there any resources for troubleshooting that kind of stuff? I have deployed servers and such, but I haven't ever done anything like this where I am trying to get stuff back to a blizzlike state with scripts and encounter logic and whatnot.
Sep 01, 2026 · 11:20
Why are my items being removed on login? So the original existing items are kept, but custom items get removed every time I login. If I have the item, logout it will be stored in database I can see it, but when I login back It gets removed. Anyone had similar issue? Can't find any errors in logs.
Sep 01, 2026 · 11:21
The item is added to both db2's for client and server and also in hotfix database
Sep 01, 2026 · 12:02
fixed
Sep 02, 2026 · 23:20 (edited)
does cata classic have the volumetric height fog from the newer clients?
Sep 03, 2026 · 08:13
Depends on when it was added to the retail client and if the classic devs had it enabled for 4.4.x as they did change the visuals to resemble the original style. Which is also why it's not such a blurry mess as retail is
Sep 03, 2026 · 08:51
yeah i was messing around with the 1.15 client but it didn't seem to have it. i'll try 4.4 later and see
Sep 03, 2026 · 09:01
they are doing weird things in classic 1.xx, sticking to the original closer than in progressive classic
Sep 03, 2026 · 09:04
they even blocked one of camera control modes there (only horizontal when moving)
Sep 17, 2026 · 22:17
Hi everyone,
I'm trying to get cata_classic to run locally on Linux+Docker.
I've made it to the point that world+bnetserver are running, and I can start the 4.4.2 client using burralis.
But when I try to log in, I get BLZ51901015 (You have been disconnected).
I have checked the usual spots:
* Config.wtf
* auth.realmlist table
* ports
Not sure what's going wrong. Maybe burralis doesn't like being run via Wine?
Sep 17, 2026 · 22:18 (edited)
you also need port 1119
Sep 17, 2026 · 22:19
Oops, missed that one on the screenshot. It's open as well:
Sep 17, 2026 · 22:20
but do you have 1119 on tcp? not v6
Sep 17, 2026 · 22:21
Ah shit, makes sense
Sep 17, 2026 · 22:21
bnet cannot do ipv6 (this is a client limit), only world can (port 8085)
Sep 17, 2026 · 22:23
Hm, forcing docker to ipv4 didn't change anything:
Sep 18, 2026 · 18:08
I suspect that the client is at fault. I think getting a copy of 4.4.2 is somewhat impossible at this point, so I'll have to call it quits here :/
Sep 18, 2026 · 18:09
it might just be a docker issue, nobody here really tests that, we all run it directly
Sep 18, 2026 · 18:10
(no, i don't have a 4.4.2 client)
Sep 18, 2026 · 18:11
I've investigated a lot with tcpdump - when I just curl 8805, I get a working ssl handshake
Sep 18, 2026 · 18:11
but when the client tries to log in, there is nothing
Sep 18, 2026 · 18:12
hold up
Sep 18, 2026 · 18:12
curl 8085?
Sep 18, 2026 · 18:12
yh
Sep 18, 2026 · 18:12
thats a worldserver port, there should not be any ssl over that
Sep 18, 2026 · 18:12
ah shit I'm mixing up ports
Sep 18, 2026 · 18:13
I meant 8081
Sep 18, 2026 · 18:13
first, do you get a client connection on 1119? (thats the initial connection)
Sep 18, 2026 · 18:13
yes
Sep 18, 2026 · 18:13
then does it fail later when going for 8081?
Sep 18, 2026 · 18:14
yeah, tcpdump sees ssl handshake on 1119, but nothing on 8081
Sep 18, 2026 · 18:15
how do
LoginREST. configs look for you? (bnetserver.conf)
Sep 18, 2026 · 18:16
Sep 18, 2026 · 18:19
this looks fine
Sep 18, 2026 · 18:20
tcpdump for 1119 (trying to log in via client + burralis):
Sep 18, 2026 · 18:20
tcpdump for 8081 (trying to log in via client + burralis):
Sep 18, 2026 · 18:20
(so, nothing)
Sep 18, 2026 · 18:21
then I fire this:
curl -k -v https://127.0.0.1:8081/bnetserver/login/ \
-H "Content-Type: application/json" \
-d '{"inputs":[{"input_id":"account_name","value":"TEST@TEST"},{"input_id":"password","value":"test"}]}'
Sep 18, 2026 · 18:22
waaaaaaaaaaaaait
Sep 18, 2026 · 18:22
why are you getting ssl on 8081?
Sep 18, 2026 · 18:22
... am I not supposed to? x)
Sep 18, 2026 · 18:22
no, you are not
Sep 18, 2026 · 18:22
lol
Sep 18, 2026 · 18:22
it should go over http
Sep 18, 2026 · 18:22
fascinating
Sep 18, 2026 · 18:22
not https
Sep 18, 2026 · 18:23
did you swap the default certificate that ships in repo?
Sep 18, 2026 · 18:24
I generated a new one, because the image didn't come with one (or I could at least not find it)
Sep 18, 2026 · 18:24
yeah that isnt going to work
Sep 18, 2026 · 18:25
for localhost testing only this one works <https://github.com/TrinityCore/TrinityCore/blob/cata_classic/src/server/bnetserver/bnetserver.cert.pem>
Sep 18, 2026 · 18:25
and its private key in same directory
Sep 18, 2026 · 18:25
ah oke, I'll look around in the image
Sep 18, 2026 · 18:25
thank you!
Sep 18, 2026 · 18:25
(or I'll just mount the one from the repo, but lets see first if it is in the image)
Sep 18, 2026 · 18:27
it is
Sep 18, 2026 · 18:27
/home/circleci/project/bin/check_install/bin/bnetserver.cert.pem if you are using our images from docker hub
Sep 18, 2026 · 18:27
and key
/home/circleci/project/bin/check_install/bin/bnetserver.key.pem
Sep 18, 2026 · 23:57
check_install? BARF
Sep 18, 2026 · 23:57
utterly broken and misguided piece of crap
Sep 19, 2026 · 00:02
its lazy af, i know
Sep 19, 2026 · 00:03
its literally just reusing ci setup, it was not made with docker in mind
Sep 19, 2026 · 00:03
no, one can see that 🙂
Sep 19, 2026 · 00:04
bin/check_install/bin/ ? really? 😄
Sep 19, 2026 · 00:05
are these just artifacts from github builds or sth or... ?
Sep 19, 2026 · 00:05
circleci
Sep 19, 2026 · 00:05
right but basically just artifacts
Sep 19, 2026 · 00:05
the first bin is cmake build dir, the second bin is real unix bin
Sep 19, 2026 · 00:06
whatever, it works and is not worth changing
Sep 19, 2026 · 00:06
can you make CI use a different docker config, or would that not be a good option since it would break things?
Sep 19, 2026 · 00:07
actually i dont know where it lands in final docker image
Sep 19, 2026 · 00:07
might be even be /usr/local
Sep 19, 2026 · 00:08
might as well skip checkinstall then and just run make install 😛
Sep 19, 2026 · 00:09
oh that is make install
Sep 19, 2026 · 00:09
its given
-DCMAKE_INSTALL_PREFIX=bin/check_install
Sep 19, 2026 · 00:09
right but I mean make install straight into /usr/local ?
Sep 19, 2026 · 00:10
cant do that
Sep 19, 2026 · 00:10
why bother with a package in the first place? it's docker... 😛
Sep 19, 2026 · 00:10
ci and the pushed image use different base images for size reasons
Sep 19, 2026 · 00:11 (edited)
now you lost me. I thought these were simply the artifacts from CI... ?
Sep 19, 2026 · 00:13
the artifact is a .deb or .rpm that gets installed into another docker image?
Sep 19, 2026 · 00:14
Sep 19, 2026 · 00:15
it grabs stuff from check_install dir
Sep 19, 2026 · 00:25
https://github.com/TrinityCore/TrinityCore/blob/master/.circleci/config.yml#L91
Where does this Dockerfile come from? Is it the same as the one in contrib?
Sep 19, 2026 · 00:26
Ah looks like it
Sep 19, 2026 · 00:27
But I see references to trinitycore/circle-ci:debian-13-builder everywhere and I'm not sure where these are built...
Sep 19, 2026 · 07:23