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
[3.3.5] Core/LFD LBRS tele location&different Instance after wipe #23569
Comments
I Will try to explain this issue, it's an old one, when players starts a big dungeon specially vanilla 50+ (stratholm, LBRS,..) if after a while a player(s) died and release spirit, when he try to enter the instance to resurrect he will get the message "wrong instance", in this case if he resurrect in the graveyard and try to enter the dungeon he will end up in a different instance than the other players, it's like the first lock is lost or deleted, maybe the soft reset happen even if players are inside the instance and that result the instance ID to be deleted. |
That's right. It seems the server resets the Dungeon after wipe. |
This could be related:
|
fix LFGDungeons LBRS tele issue and confirmed on my server,
|
The SQL from @soniczhang11 should be added. Dont know if this is 100% Retail or not but it works correctly. |
@soniczhang11 : The TC SQL codestyle version of your suggested solution looks like this: DELETE FROM `lfg_dungeon_template` WHERE `dungeonId` IN (32, 44);
INSERT INTO `lfg_dungeon_template` (`dungeonId`, `name`, `position_x`, `position_y`, `position_z`, `orientation`, `VerifiedBuild`) VALUES
(32, 'Lower Blackrock Spire', 78.5083, -225.044, 49.839, 5.1, 0),
(44, 'Upper Blackrock Spire', 78.5083, -225.044, 49.839, 5.1, 0); edit: I have replaced your |
Where dungeonId comes from so I can check if it's valid? |
Description:
2 Bugs with LFD
Current behaviour:
The tele location for LBRS in LFD system is wrong. Now it tele players to the location near entrance of BWL. It should tele players to the entrance of BRS.
When player use LFD and wipe in instance, they may walk in a new instance(all mobs are respawned) after their souls running back. However, players who have not release their souls are still in the old one. It is a annoying issue but appears only sometimes.
Expected behaviour:
Steps to reproduce the problem:
Branch(es):
3.3.5
TC rev. hash/commit:
4529a94
Operating system: CentOS 7
The text was updated successfully, but these errors were encountered: