Below are the downloads of the MultiPath OP File Management System for Worlds in ActiveWorlds

Underneath is a brief "what is it" description of MultiPath, there is also a link to display the install instructions so you can see if you think you want to try it before downloading it.

MultiPath Version 1.12beta - Altered and enhanced search criteria. Added test file handling. Other fixes and enhancements.

MultiPath OP Zip download
MultiPath OP tar.gz download

MultiPath Version 1.01beta - Initial Release
Install Text  
 
 

A basic Understanding of how it all works.

The database OP system relies on a different attitude to world OP servers in order to work. On a normal OP files are distributed under 5 directories (avatars, models, seqs, sounds, textures). On the MultiPath system the number of directories is theoretically unlimited. Thus files may be placed in directories that have more relevance to the file. These extra directories are referred to here as "Categories".

For example think of the object tree1.rwx. Now most people know this is a tree object and is in the "models" directory on most OP servers. Its there, mixed up with most probably thousands of other files. On the MultiPath system we can assign a "category" (a new directory) for tree1.rwx and also for all other trees and plant objects.
We create a "plants" category for our tree1 and the system automatically creates a plants directory to match.
Now we can add our tree1.rwx (actually its a .zip file) to the system OP using the systems inbuilt "Add file" or "Edit file" functions which are available to all that are given a login password to the system. While those users are accessing these features futher differences (features!) of the MultiPath system are seen.

Firstly, each user has their own login and can be added and created from within the web system - no more having to give out ftp passwords! There are multiple levels of user access, thus allowing some Caretaker like access while others something more appropriate to builders or even a guest access just so someone can upload files. Each user can upload using the web system, from within AW or using an external browser. The system automatically matches the uploaded file to that user.

The striking feature of the system is that it uses a database driven backend to keep track of all the files, where and what they are. As a database has the ability to keep records on a lot of information, it has the ability to not only have the files under categories but to also list whatever information about the file we would like to see. This system employs the use of a number of fields for various object information, these are described further below. All information provided at the time of file inclusion, or edited in later, is then held in the database with the file for later searching and retrieval.

What does all this mean?
Well, overall, it provides an automatic system that allows a user to search the lists of files in order to find one suitable to their needs. Searches can be done via categories ie: models - plants, lists all the files in the "plants" directory or, better yet, by using word specific searches within the files search, like "tree1" or "tree", a more comprehensive and accurate result is obtained.
With the implementation of the other fields in the database (descriptions etc) it is possible to build up a search criteria based on any query.

Also, it provides the means for a single OP to provide all forms of objects, textures and other files to a number of worlds. Due to the basic nature of the MultiPath system to incorporate multiple directories, this allows for the creation of special directories for different avatar.dat files for different worlds. It also provides, via the same medium, for the possibility to have "author owned" directories. Thus a particular 3D modeller might use a single diectory for their created items and thus have the ability to share this category (directory) to certain worlds and not have them available to others.

A filesystem with a database backend basically means that, now, everything is possible!

Database Fields: The following fields are currently supported by this MultiPath System.

Models:

• Object Name - the name of the object without the extension
• Textures - the names of the textures the object uses by default
• Tag - Whether the object includes tag's for multitexturing
• Prelit - Whether the object is lit or not
• Solid - Whether the object is naturally solid off or solid on
• Size - The 3D size of the object, not the file size eg: a walk object "4x4"
• Origin - The original creator of the object, to keep track of modellers :)
• Uploader - The person responsible for placing the object on this OP
• Description - a descriptive text describing the object, the better the description, the better searches work :)
• Comments - a field for including "notes" about an object. Not used in search queries, this field is like a reminder pad for object modellers etc. You could leave a note like "have to change the ambience on this object" or any other 'work to do' or helpful notes.

Textures:

• Name - as per models
• Mask - whether the texture includes a mask. The system is semi-intelligent about masks, if you upload (or edit) a texture and say "yes" to mask, the system will automatically ask you to upload the mask as well, or transparently act upon the mask file as it acts upon the jpg file when editing.
• Filmstrip - indicates whether the texture is actually an animate or not.
• Display - automatically selected this field allows users to display the texture after searches (opens in a popup window)
• Origin - The original creator of the texture, to keep track of artists :)
• Uploader - as per models
• Description - as per models
• Comments - as per models

Avatars:

• Name - as per models
• Av dat Name - The name given to the avatar within a world
• In Use - The worlds in which the avatar is currently included in the worlds av dat. This field is user set, the system does nothing with the av dat files.
• Origin - The original creator of the avatar, to keep track of modellers :)
• Uploader - as per models
• Description - as per models
• Comments - as per models

Sounds:

• Name - as per models
• File Type - whether the sound is a midi, wav or mp3
• Origin - The original creator of the sound, to keep track of musicians :)
• Uploader - as per models
• Description - as per models
• Comments - as per models

Seqs:

• Name - as per models
• Origin - The original creator of the sequence, to keep track of modellers :)
• Uploader - as per models
• Description - as per models
• Comments - as per models