TrinityCore#master
May 30, 2026 · 22:43
except that default cmake presets dont pass any debug info creating options like -g with Release
May 30, 2026 · 22:44
and most users just use defaults
May 30, 2026 · 23:08
In retail they have a objective tracker on right side of screen and I think they use scenario system to show how many bosses you killed in the dungeon and stuff like that
May 30, 2026 · 23:08
May 30, 2026 · 23:08
I notice that strat has the live and dead side but the tracker is showing stuff specific to one side
May 30, 2026 · 23:09
How does the game differentiate if it should show live side objective stuff
May 30, 2026 · 23:09
or the undead side objective stuff
May 30, 2026 · 23:13
May 30, 2026 · 23:14
I see the data for it and how its a seperate scenario ID even though they share same map id
May 30, 2026 · 23:14
but i dont know how the game knows to show like scenario Y data if you are player the live version vs undead version
May 30, 2026 · 23:14
areatriggers and manually started scenario
May 30, 2026 · 23:15
As in areatriggers.db2 or a world table? Also can you give me example how to manually start it? Like via db or is it script or both?
May 30, 2026 · 23:16
i never said thats how its implemented, just a an idea how to handle it
May 30, 2026 · 23:17
oh okay! thought you found a hook or trigger in the files somewhere, ty for clarification 🙂
May 31, 2026 · 15:52
didnt someone already handle this
May 31, 2026 · 15:52
or bringing it up
May 31, 2026 · 15:53
i remember scenario data being unique on instance init, but then it was changed to be switchable
May 31, 2026 · 15:54
even I remember that said person used strat as an example
Jun 01, 2026 · 13:44
it should indeed be switchable, even the lfg dungeon id of the map should be switchable (proving grounds works like that + scenario for ready and trial data)
Jun 01, 2026 · 13:45 (edited)
my guess is the gate between living and undead has an areatrigger near it that swaps the scenario
Jun 01, 2026 · 13:48
that gate is permanently closed on retail now
Jun 01, 2026 · 13:51
been a while, so its closed now? are there two lfgdungeon entries then for it?
Jun 01, 2026 · 13:51
also some recent-ish (idk which expansion) changes to dungeon progress checkpoints made it so you cannot go into undead side, exit and enter "living" (crusaders are undead now), it just ports you back to entrance at undead
Jun 01, 2026 · 13:51
you have to fully reset the dungeon from the menu to swap sides
Jun 01, 2026 · 13:53
i looked into it briefly the other day and lfgdungeons had scenario at 0 for both living and undead, he can maybe try to send a hotfix and see if it works
Jun 01, 2026 · 13:53
no spells referenced the id either
Jun 01, 2026 · 13:53
oh its just started by areatriggers on retail
Jun 01, 2026 · 13:53
fair enough
Jun 01, 2026 · 13:53
no scenario here
Jun 01, 2026 · 13:54
yea so areatrigger action does it then, or smart script here i guess
Jun 01, 2026 · 13:55
actually, this side is just broken, no scenario at all
Jun 01, 2026 · 13:55
im already at crusaders
Jun 01, 2026 · 13:56
other side had it already at entrance
Jun 01, 2026 · 13:56
well it is rather fresh data from what i gathered
Jun 01, 2026 · 21:22
Is there any "Known" limitation that would prevent the client from loading/displaying a custom achievement?
Jun 01, 2026 · 21:22
while using the hotfixes ofc
Jun 01, 2026 · 22:21
as far as i recall, no
Jun 01, 2026 · 22:22
for as long as your achievement hotfixes are in place it should work
Jun 01, 2026 · 22:22
remember to delete cache after modifying them
Jun 01, 2026 · 22:23
Yeah am not having any luck tbh and I cannot figure out why. I have an achievement record, criteria and 2 criteria trees. I delete the cache every time but it still won't show up.
Jun 01, 2026 · 22:24
did you add the correct blob?
Jun 01, 2026 · 22:24 (edited)
Can an achievement show up if i remove the criteria/tree?
Jun 01, 2026 · 22:24
I am adding the records in hotfix_data, not using the blob
Jun 01, 2026 · 22:24
as you should, blob only exists to hotfix db2 files we are not loading
Jun 01, 2026 · 22:24
oh yeah, mb, i meant _data
Jun 01, 2026 · 22:25
you're certain you're targeting thecorrect table hash?
Jun 01, 2026 · 22:25
yep i got them from wow.tools
Jun 01, 2026 · 22:26
If I do .achievement add xxxx ingame it says player was awarded achievement ! without any name
Jun 01, 2026 · 22:26
maybe you should go into the command and try to see where the name is taken from
Jun 01, 2026 · 22:29
im assuming he means achievement name
Jun 01, 2026 · 22:29
in that case it would be a clienside db2 lookup, going back to hotfix not creating a record
Jun 01, 2026 · 22:30
but if he allegedly set correct hotfixes, shouldn't that clientside lookup already be modified?
Jun 01, 2026 · 22:32
so the hotfix record is incorrect then?
Jun 01, 2026 · 22:35
This is what i have in hotfix_data
(800010, 800010, 3538802599, 800001, 1, -1), -- Achievement 1 Deadmines
Jun 01, 2026 · 22:35
it is the same pattern i use for custom phases and those work just fine
Jun 01, 2026 · 22:35
your hash is wrong.
Jun 01, 2026 · 22:36
isn't hash supposed to come from the hotfix db anyway
Jun 01, 2026 · 22:36
its 0xD2EE2CA7, not 0xD2EDD7A7
Jun 01, 2026 · 22:36
omg
Jun 01, 2026 · 22:37
works just fine
Jun 01, 2026 · 22:37
Jun 01, 2026 · 22:37
:omegakekW:
Jun 01, 2026 · 22:37
🙁
Jun 01, 2026 · 22:37
ima save that up now
Jun 01, 2026 · 22:38
Thanks let me try it again
Jun 01, 2026 · 22:46
Oh boy... it works... now not to find an excuse but believe it or not... i asked copilot to convert the hex to decimal and IT GAVE THE WRONG value 😛 serves me right
Jun 01, 2026 · 22:48
thats a fail for 2 reasons
Jun 01, 2026 · 22:48
1. ai cant actually do math
Jun 01, 2026 · 22:49 (edited)
2. mysql just accepts hex input without converting
1
Jun 01, 2026 · 22:50
1. Yes it can, ask the right fucking AI lmao
Jun 01, 2026 · 22:50
Idk what you asked it but if I ask GPT to convert something from hex to dec or other way around it’sncorrect
Jun 01, 2026 · 22:50
Yeah I will do that from now. Many thanks
Jun 01, 2026 · 22:50
Just use established algorithms for basic math. Like the usual python interpreter someone has open 24/7 :lul:
Jun 01, 2026 · 22:53
And which is the "right" AI? It is a simple convert request which a basic web based convertor can do... but the AI not.
Jun 01, 2026 · 22:55
I have tried 2 different AI's now and both give wrong answers which kinda proves Shauren's point
Jun 01, 2026 · 22:56
rather ask the correct thing
Jun 01, 2026 · 22:56
:kek:
Jun 01, 2026 · 22:56
you can convince the AI 3 + 3 = 4 if you want
Jun 01, 2026 · 22:57
Claude and Gemini do pretty good things when it comes to math and SQL, at least, that's my experience
Jun 01, 2026 · 22:59
also never use HeidiSQL to import localized strings when they use different ISO standards with bytes encoding
Jun 01, 2026 · 23:00
it will mess the string, don't ask why or how, it's been a bug ever since 2018 minimum
Jun 01, 2026 · 23:01
Jun 01, 2026 · 23:02
:Shrug:
Jun 01, 2026 · 23:02
that just shows ai is not the all purpose tool that ai companies are claiming it to be
Jun 01, 2026 · 23:02
i have seen someone building a calculator from AI
Jun 01, 2026 · 23:03
the calculator took its 4-5 seconds to calculate
Jun 01, 2026 · 23:03
:pikapika:
Jun 01, 2026 · 23:03
thats insane waste of power
Jun 01, 2026 · 23:03
i know right? but it's funny given that there's a basic standard to AI and it takes time to build up answers
Jun 01, 2026 · 23:04
also, windows calc can convert hex, no need to search for any tools
Jun 01, 2026 · 23:04
you can have all the tools in the world
Jun 01, 2026 · 23:04
but if you don't know them, or rather know how to use them :pepehands:
Jun 01, 2026 · 23:10
At least I can learn from my mistake, the AI does not.
Jun 01, 2026 · 23:26
actually it can
Jun 01, 2026 · 23:27
if you teach them to
Jun 01, 2026 · 23:27
again, it's a child that needs investment
Jun 02, 2026 · 10:09
In Trinity, target type 106 was changed on January 21, 2025 from TARGET_DEST_CHANNEL_CASTER to TARGET_DEST_NEARBY_DB. As far as you know, is that change only considered valid for newer clients / newer spell data, or could that newer semantic also be correct retroactively for older expansions?
Reason I’m asking: I have multiple older sniff examples where spells with target type 106 do not appear to behave like CHANNEL_CASTER. The sniff versions I checked are from 9.x and 6.x.
Jun 02, 2026 · 10:14
is that the one that selects random point from one of multiple rows in db?
Jun 02, 2026 · 10:16
its probably a valid change for all versions, 3.3.5 has only 2 spells using it and they kind of fit the "new" impl
Jun 02, 2026 · 10:28
Yes, exactly.
On master, TARGET_DEST_NEARBY_DB uses spell_target_position, can have multiple rows for the same spell/effect, filters them by map/radius, and then picks one of the valid positions at random.
So in your view, that semantic would also be correct for older versions. Thanks a lot for the clarification.