In the second room section thing of Area 1, blow up every black brick block.

I made this thing in late August/early September but I didn't post it here for some reason?!
Anyway, with this, you can pack your levels on Linux and whatnot, and they properly unpack under vanilla KS!? AMAZING!

I was too lazy to make it easy to use I guess, so you have to be in the same directory as the level you want to compress and /path/to/script level\ directory\ name
Also, it's probably pretty messy, and I'm just commenting it now, but that shouldn't be too much of a problem?!

#!/usr/bin/python

import os, sys

archive = open(sys.argv[1] + ".knytt.bin", "w") # GO GET EM
path = "" # I guess this is the path from the root (where you executed the script)

def tobytestring(data, length): # convert FILE SIZES into base-256 representation things that tell the unpacker how far the file goes
    bytestring = ""
    blahness = data
    for i in range(length):
        x = blahness % 256
        bytestring += chr(x)
        blahness = (blahness - x) / 256
    return bytestring

def putfile(filename): # put a file into the file
    global path
    file = open(filename, "r")
    contents = file.read()
    length = len(contents)
    archive.write("NF%s%s\0%s%s" % (path, filename, tobytestring(length, 4), contents)) # I'm guessing NF is NEW FILE and then that next bit is path, then filename, then a null terminator, then four bytes of size information, then file contents. Yep.
    file.close()

def putdir(dirname, isroot):
    global path
    os.chdir(dirname)
    if not isroot:
        oldpath = path
        path += dirname + "\\"
    for file in os.listdir("."):
        if os.path.isdir(file):
            putdir(file, False)
        else:
            putfile(file)
    os.chdir("..")
    if not isroot:
        path = oldpath

archive.write("NF%s\0BLAH" % sys.argv[1]) # I couldn't find any rhyme or reason to this size thing (the size of the level directory?! I don't even know) so I just put in BLAH and it seems to work just fine.
putdir(sys.argv[1], True)
archive.close()

There is a deal bit of overlap between the two terms, and I have been having trouble establishing in my own mind what definitions they have in the context of this forum.

Firstly, I shall establish my terms:

• An "article", in the following definitions (though not strictly, at all), is an abbreviation for "article describing a project", merely shortened for brevity
• WIP, standing for "work in progress", strictly means anything that is not done, but is being worked on, which does not require an article for qualification, as it is the project itself, rather than an article.
• A preview is an article for anything which is not currently fully available (a view of what is to come).  A preview may include images associated with a WIP, a demo, and textual information.

Now, I present my problem:

As a preview and a WIP are not only overlapping qualifiers, but also descriptive of whole different entities themselves, I think they are not the best of terms for describing articles (of course, describing the associated WIP) presented in the development showcase (assuming the article of interest is a preview).

And, of course, my proposition:

Two new terms be adopted, each describing a preview and WIP acceptable in the development showcase by the current standards, with my own two examples following (the acronyms could use some work, but at least the idea is there):

• IWP (interactive work in progress): A work in progress (WIP) available to the public as an interactive demonstration of current status (unless, of course, in a certain, case some noninteractive form of demo would suffice)
• PWI (Preview with IWP): A preview of a WIP, with an interactive demonstration included, fulfilling the requirements of posting in the showcase board

Any thoughts, or possibly better acronyms?