LegionCore-7.3.5
LegionCore-7.3.5 copied to clipboard
connection_patcher need for clinet 26124
connection_patcher need for clinet 26124 Unfortunately, I did not find any source about this client anywhere. Please help if you can. @dufernst
Hi, most likely you need about this commit and from it you can see which patcher will be able to patch. At the Legion, he was still working. https://github.com/TrinityCore/TrinityCore/tree/ccbe4404f1806f047c009d14ed1dea9806dd5736/src/tools/connection_patcher
@Arshiya051 https://github.com/ReyDonovan/LegionCore-7.3.5/commit/d869d86670228dc92a287633883873c8fb4bbc8c fork
Thank you for the subscription. It helps a lot. However, I want to find a way to create a 7.1.5 client so that there is no problem with the player. Considering that the 7.2.5 and 7.3.5 patches are off in the world server, I need the client to be 7.1.5. With the aim of making the player experience the feeling of playing season after season. However, if you have time and can help me fix this issue. Thankful @ReyDonovan
it's easy) if you have time..
Well, dear friend, if you can, code this completely for the client, like (https://github.com/dufernst/LegionCore-7.3.5/commit/1da4e30d717b2d46e0f26c01c182bbf5e08d7b75). Because I couldn't. I have patch 7.1.5, 7.2.5 and 7.3.5 separately and I can test it. If you can help. @ReyDonovan
Arshiya051 It makes no sense for you to use version 7.1.5 or 7.2.5 of the client itself. To do this, you will have to rewrite many structures and packages in the kernel itself. For this reason, instead of using client 7.1.5 or 7.2.5, 7.3.5 is used, but in the kernel itself some mechanics are disabled that were not in 7.1.5 or 7.2.5
OK. So I leave this issue and work on other bugs. thanks @Fragrus