Door entrance to Black Knights Fortress for quest

Report potential bugs here, and if they seem valid we can create gitlab issues for them.

Moderator: Bug Janitor

Forum rules
- Check if a topic exists before creating a new one.
- Duplicate topics will be immediately deleted.
- Issues lacking detail or sources (where applicable) will be deleted immediately.
- Unimplemented content is not bugged content. Do not report unimplemented content.
- IF YOUR BUG IS EXPLOITABLE DO NOT REPORT IT HERE. DM the report to a Bug Janitor instead.
- Repeated violation of these rules may result in a user being denied access to this section.
Locked
User avatar
Tacomac
Noob
Posts: 1
Joined: Tue Mar 07, 2023 3:10 am

Door entrance to Black Knights Fortress for quest

Post by Tacomac »

What did you do?
Equipped the iron chainbody, bronze medium helmet, unequipped everything else, talked to the fortress guard, then clicked on the door to go in.

What happened?
The door did not open, nor give any message that I can't use it, retried several times from different directions, equipment, talked to different guards, ect.

What did you expect to happen? (Provide a source from runescape wiki/youtube/etc if possible)
The door would open and I would be able to continue the quest.

Are there any relevant item/npc IDs? (use ::debug command in chat)
[SCENERY INTERACT]
ID: 2337, Option: Open[0]
Loc: [3016, 3514, 0], Dir: EAST
-----
Received interaction request Open

Any screenshots/recordings?
Attached screenshot

Have you reproduced it on the test server? If so, what are the steps?
I have not.
User avatar
meskof
Noob
Posts: 1
Joined: Thu Mar 09, 2023 8:01 pm

Re: Door entrance to Black Knights Fortress for quest

Post by meskof »

I've had exactly the same problem today.
User avatar
TheChimpken
Froob
Posts: 59
Joined: Tue Dec 27, 2022 7:59 pm
Has thanked: 30 times
Been thanked: 29 times

Re: Door entrance to Black Knights Fortress for quest

Post by TheChimpken »

The below change will fix this:
https://gitlab.com/2009scape/2009scape/ ... uests/1174

Next release this will be fixed. :)
Locked