- 
                Notifications
    You must be signed in to change notification settings 
- Fork 58
update (3.3.5-solocraft): Maintence #141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The login issue is resolved with this change.Getting in instance (in a group) lead to crash. Being solo is OK. I think there might be an extra modification to make, line 528 :
    526             {
    527                 //Exclude player from the tally because the player is the one entering the dungeon
    528                 if (itr->guid != player->GetGUID)
    529                 {
    530                     //Database query to find difficulty for each group member that is currently in an instance
    531                     QueryResult result = CharacterDatabase.PQuery("SELECT `GUID`, `Difficulty`, `GroupSize` FROM `custom_solocraft_character_stats` WHERE GUID = {}", itr->guid);
| Post the crashlog pls | 
| I can't reproduce this issue anymore. I can enter instance with both players and bots (npcbots) without disconnection/crash. I'll try to perform some more tests. Patch used : https://patch-diff.githubusercontent.com/raw/TrinityCore/TrinityCoreCustomChanges/pull/141.patch  | 
| 
 Given the revision you recompiled with my last commit adjustment for a sql query i over looked. It should be good to go unless u have any other issue then please let me know. | 
| I've performed some more tests. Everything is OK now ! Thank you all for your quick support and commitment ! | 
Changes proposed:
Target branch(es): 3.3.5-solocraft
Issues addressed: Fixes # #140
Tests performed: (Does it build, tested in-game, etc)
Known issues and TODO list: