[DiscordArchive] So, should we replace them to be the same ?
[DiscordArchive] So, should we replace them to be the same ?
Original source
well, for your own project you can do what you want
rektbyfaith
01-28-2022, 07:28 PM #21Archived author: Kitzunu • Posted: 2022-01-28T19:28:58.268000+00:00
Original source
well, for your own project you can do what you want
Original source
but touching broadcast_text in AzerothCore repository is forbidden
rektbyfaith
01-28-2022, 07:29 PM #22Archived author: Kitzunu • Posted: 2022-01-28T19:29:14.792000+00:00
Original source
but touching broadcast_text in AzerothCore repository is forbidden
Original source
other variant?
rektbyfaith
01-28-2022, 07:30 PM #23Archived author: Bogir • Posted: 2022-01-28T19:30:02.071000+00:00
Original source
other variant?
Original source
I dont quite understand you
rektbyfaith
01-28-2022, 07:30 PM #24Archived author: Kitzunu • Posted: 2022-01-28T19:30:22.355000+00:00
Original source
I dont quite understand you
Original source
I mean variant to store all texts in one place excepts broadcast table
rektbyfaith
01-28-2022, 07:30 PM #25Archived author: Bogir • Posted: 2022-01-28T19:30:29.961000+00:00
Original source
I mean variant to store all texts in one place excepts broadcast table
Original source
I mean you don't really need it. Because no matter if you want to do custom things in creature_text, gossip_menu_option, or others that can take texts, you can enter the custom text there
rektbyfaith
01-28-2022, 07:31 PM #26Archived author: Kitzunu • Posted: 2022-01-28T19:31:41.317000+00:00
Original source
I mean you don't really need it. Because no matter if you want to do custom things in creature_text, gossip_menu_option, or others that can take texts, you can enter the custom text there
Original source
I suggest to remove text0_0, text0_1 and so on, which duplecated in broadcast text completelly, and leave there only pointing to broadcast_text.ID or in new "text"-table with texts for any customisations
rektbyfaith
01-28-2022, 07:33 PM #27Archived author: Bogir • Posted: 2022-01-28T19:33:23.416000+00:00
Original source
I suggest to remove text0_0, text0_1 and so on, which duplecated in broadcast text completelly, and leave there only pointing to broadcast_text.ID or in new "text"-table with texts for any customisations
Original source
no, that defeats the whole purpose.
Because broadcast_text only holds data that we have sniffed. All data we have is not sniffed.
we only point to broadcast_text when we know it is sniffed aka exists there
rektbyfaith
01-28-2022, 07:34 PM #28Archived author: Kitzunu • Posted: 2022-01-28T19:34:23.938000+00:00
Original source
no, that defeats the whole purpose.
Because broadcast_text only holds data that we have sniffed. All data we have is not sniffed.
we only point to broadcast_text when we know it is sniffed aka exists there
Original source
there are entries of all tables that do not point to broadcast_text, and that is because there is no entry there that confirms it has actually been sniffed
rektbyfaith
01-28-2022, 07:34 PM #29Archived author: Kitzunu • Posted: 2022-01-28T19:34:49.951000+00:00
Original source
there are entries of all tables that do not point to broadcast_text, and that is because there is no entry there that confirms it has actually been sniffed
Original source
it works as it should for us
rektbyfaith
01-28-2022, 07:35 PM #30Archived author: Kitzunu • Posted: 2022-01-28T19:35:11.337000+00:00
Original source
it works as it should for us
1 Guest(s)
1 Guest(s)