We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
The AQ instances do not check for the attunement quest - you can clip/jump/slip/be warlock summoned past the scarab wall and access AQ dungeons.
The instance should ping like zul gurub that you need to do a quest in yellow, and deny entry to unattuned players.
The text was updated successfully, but these errors were encountered:
I can't reproduce this. I need progression level 4 to enter the instance.
I made a new character, jumped over the scarab wall, but I'm not able to enter AQ20. Only after setting my progression level to 4 I can enter it.
but if you want this for your own server, this will do it:
DELETE FROM dungeon_access_requirements WHERE dungeon_access_id IN (27, 28); INSERT INTO dungeon_access_requirements (dungeon_access_id, requirement_type, requirement_id, requirement_note, faction, priority, leader_only, comment) VALUES (27, 1, 8286, 'You must complete the quest "What Tomorrow Brings" before entering Ahn Qiraj Ruins.', 2, NULL, 0, NULL), (28, 1, 8286, 'You must complete the quest "What Tomorrow Brings" before entering Ahn Qiraj Temple.', 2, NULL, 0, NULL);
dungeon_access_requirements
dungeon_access_id
requirement_type
requirement_id
requirement_note
faction
priority
leader_only
comment
Sorry, something went wrong.
@StraysFromPath did you have ".gm on" active on the account?
No branches or pull requests
The AQ instances do not check for the attunement quest - you can clip/jump/slip/be warlock summoned past the scarab wall and access AQ dungeons.
The instance should ping like zul gurub that you need to do a quest in yellow, and deny entry to unattuned players.
The text was updated successfully, but these errors were encountered: