Meaning you can't interact with it. Using "Actions debug" you can interact with it, but those change on server restart.
My personal guess would be it's different in the map somehow; if we could get a map editor, we could do some good work.
For those testing on localhost, you can easily get to a trapdoor by typing ::tp 3405 3506.
An easy fix to this might be to just add another interactable object underneath it for now. Or, if this is a Parabot thing (rather than the server just doing something weird), this will just be closed.
Originally created by @dginovker on GitHub (Dec 9, 2019).
Original GitHub issue: https://github.com/2006-Scape/2006Scape/issues/247
Parabot's Object Debug does not find it:
Meaning you can't interact with it. Using "Actions debug" you can interact with it, but those change on server restart.
My personal guess would be it's different in the map somehow; if we could get a map editor, we could do some good work.
For those testing on localhost, you can easily get to a trapdoor by typing `::tp 3405 3506`.
An easy fix to this might be to just add another interactable object underneath it for now. Or, if this is a Parabot thing (rather than the server just doing something *weird*), this will just be closed.
I wasn't able to find the thread he's talking about
<!-- gh-comment-id:563332346 -->
@dginovker commented on GitHub (Dec 9, 2019):
scriptss from Parabot said this:
I wasn't able to find the thread he's talking about
So we have to test if it's a ground/wall decoration (which won't get picked up like regular objects), and if it still doesn't work, it's a hooking issue. I think Jetfox is on just that.
<!-- gh-comment-id:563443240 -->
@dginovker commented on GitHub (Dec 9, 2019):
Shadowrs from Parabot:
So we have to test if it's a ground/wall decoration (which won't get picked up like regular objects), and if it still doesn't work, it's a hooking issue. I think Jetfox is on just that.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @dginovker on GitHub (Dec 9, 2019).
Original GitHub issue: https://github.com/2006-Scape/2006Scape/issues/247
Parabot's Object Debug does not find it:
Meaning you can't interact with it. Using "Actions debug" you can interact with it, but those change on server restart.
My personal guess would be it's different in the map somehow; if we could get a map editor, we could do some good work.
For those testing on localhost, you can easily get to a trapdoor by typing
::tp 3405 3506.An easy fix to this might be to just add another interactable object underneath it for now. Or, if this is a Parabot thing (rather than the server just doing something weird), this will just be closed.
@dginovker commented on GitHub (Dec 9, 2019):
scriptss from Parabot said this:
I wasn't able to find the thread he's talking about
@dginovker commented on GitHub (Dec 9, 2019):
Shadowrs from Parabot:
So we have to test if it's a ground/wall decoration (which won't get picked up like regular objects), and if it still doesn't work, it's a hooking issue. I think Jetfox is on just that.
@dginovker commented on GitHub (Dec 9, 2019):
Seems they're just ground/wall decorations. Closing