So PAKEd is moving along but it’s not doing anything visually interesting yet. I’ve been breaking down stuff like the global class I have into application specific sub classes so that, for example, WADEd doesn’t have to parse all the PAK files in your Quake directory when it starts up (it won’t ever need that information so why eat the extra start up time?). I think the next step is going to be to get PAKEd to simply write out the PAK file that it currently has loaded. Once that works, I’ll add file importing/deleting and then it should be basically functional. Then the real fun begins! Previews of models, levels, and other great stuff. It’s like dessert once you’ve eaten your coding vegetables.
Tags: PAKEd