Extract-To Locations of User Created Assets?

A pal and I were just talking about how installing user created assets(maps, textures, etc) is frustrating, since we don't have any sort of UMOD installer brought over from Unreal(since VU went with InstallSheild). So, we're working on creating a TMOD format for T:V, and the appropiate installer to handle the TMODs, but since T:V hasn't been documented well yet, we're not sure where everything needs to go. So, if you guys could be so kind, could you help us flesh out this list of what things are and where they need to go?


TVM - Map file - /Content/Maps
MOPP - Havok data - /Content/Havok
U - Unreal class? - /Program/Bin
INI - Config file - /Content/System

If anyone could add something to that list, point out something we didn't think of, etc, we'd appreciate it. Thanks. :)

Thanks for this!

For those of us running servers, add a directory for compressed redirected resources. This could be Redirect, or Web/Redirect. The latter could be used if you wanted to use the built-in web server to supply compressed maps. (Only stuff below Web can be served by the built-in server, as a security measure.)

For those of us running a server on Linux, please make it possible for us to use the format. That means pay attention to the case of filenames. Avoid funny characters (including spaces) in filenames. Document the internals of the file format so we have a chance of using it.

You might take the Java approach, using ZIP as the format and including an XML manifest file to guide the unpacking. I think Open Office uses the same thing.

Thanks for this!

For those of us running servers, add a directory for compressed redirected resources. This could be Redirect, or Web/Redirect. The latter could be used if you wanted to use the built-in web server to supply compressed maps. (Only stuff below Web can be served by the built-in server, as a security measure.)

For those of us running a server on Linux, please make it possible for us to use the format. That means pay attention to the case of filenames. Avoid funny characters (including spaces) in filenames. Document the internals of the file format so we have a chance of using it.

You might take the Java approach, using ZIP as the format and including an XML manifest file to guide the unpacking. I think Open Office uses the same thing.Woah, slow down chief. Right now we're just looking at making this utility for the n00bs/end-users, so that they can install maps, mods, etc without having to go through all the extraction crud they usually do. You're about 3 steps ahead of us right now, although we appreciate the enthusiam.:)

I'm just "adding things we didn't think of" so that, as you design, you'll keep the final target in mind. Don't write yourself into a corner! ;)