I was playing around with Scopability but I noticed the example that comes with it doesn’t seem to work, if you extend it just slightly. To wit, if you “jump” (which reveals the artifact) and then try to take the alien artifact, you are told it’s still fixed in place. This is even though the code does remove the scenery property.
Is that a known thing about moving something into scope? I’m guessing not since it would seem against the intent of the extension.
I’m also curious about this because I found the archived away Hidden Items extension.
So I guess my question – beyond the possible scopability issue – would be more about why I would want to put something out of scope as opposed to just hiding it. From what I can tell, the impact on the player would be the same in that they can’t refer to something that’s hidden any more than they could if that same something was out of scope.
I just want to make sure there isn’t a nuance I’m missing.