The client application is controlled by the files ending with "matrixclientrc"
found in the client_application folder.
All the options there are heavily annotated beginning with a "#" sign.
The server application is controlled by the files ending with "matrixrc"
found in the server_application folder.
All the options there are heavily annotated beginning with a "#" sign as well.
IMPORTANT! All text files should ONLY be edited by a plain text editor
like Window's Notepad!
Other word processing programs will leave characters in the text files that will make them unreadable by the
Java client, server and bot applications! Remember to back up all text files before editing!
To access admin server commands simply type: /admin followed by a space
and the password into the chat:
like this (minus quotes): "/admin SecretPassWord"
If the password is correct the server will acknowledge and both an admin input field and an admin command choice
IMPORTANT! The admin password is found in the matrixrc file and should be changed for your own server!
To quit the admin session choose "Close" from the admin command menu.
Just choose a command from the Admin command menu and matrix will will tell you what and how to type it into the admin input.
In some cases it will provide examples.
If a listed command is not yet implemented matrix will say so.
Available admin menu commands can:
A. Remove or boot both worlds and persona-non-grata from the server.
1. Admin can remove a world or remove a world and ban its builder (or rather the person that posted it) too.
2. Admin can ban single users.
3. Booted socio-paths' names and IP addresses will be written to the "bootedrc" file found in the server_application folder.
B. Approve a world so it is listed permanently without having to reboot the server.
Approved worlds of users will remain open after the user leaves and be written to "aux_roomsrc" file found in the server_application folder.
Unapproved worlds will be removed as soon as they are empty of users.
C. If the password level is at two or three, new users with their passwords can be added to the system.
These are written to file in the "usersrc" file found in the server_application folder.
D. Add a blaxxun-style backpack object to any world for demo purposes (since backpack object implementation is not yet complete).
These objects and their positions/rotations will be listed in the "(world name)_Objects.txt" file found it the respective world's folder in the server_application directory.
E. Also, if the world is made private by its owner a list of its members will found in a "(world name)_Members.txt" file found in the world's folder.
IMPORTANT! None of the files found in a world's folder should be altered in a text editor!
F. Clear persistent storage events from a particular room. The admin HAS to be in the room for this to work.
There are three security levels for matrix network access:
1. No password (open public) which means anyone can join the 3D chat and post a world.
2. One password for all which is written into the matrixrc file.
3. Each user has their own password. These must be entered by the during an admin session.
The admin has their own bot capabiltiy for testing purposes which is
not subject to the network monitoring
of regular users or bots. This bot must use the password associated with the "admin_bot_pw" tag in the matrixrc file.
How to List and Display
1. Open with a text editor the desired matrixclientrc file found in the client_application folder.
2. Look for the first instance of the key word "avimg_url". Following this word will be the name of an image file.
In the client_matrixrc files included with this download the first image file is "avatar_images1.jpg"
Subsequent instances of "avimg_url" will be followed by "avatar_images2.jpg" and "avatar_images3.jpg"
respectively. All these image file are found in the Avatars directory.
3. For each line containing keyword "avimg_url" and its corresponding image file name there will be somewhere below it a matching
key word of "avlist_end". Think of "avimg_url" and "avlist_end" as book ends with the numerically sequence of Avatars and AvatarUrls
between them as books.
Notice how each "AvatarUrl "ends with the same number as "Avatar"
directly above it! This is very important, because not doing so will cause
the Java client to throw an error and not load!
The keyword "avlist_end" indicates that all "Avatar" names and "AvatarUrls" are to be associated
with the image file "avatar_images1.jpg", so that the names will be displayed in the Java client when the
All "Avatar" names should both correspond and be depicted on that image file.
Ten avatar images seem to fit comfortably each image file, but you can try to have more or less.
You can have as many avatar image files as you like. Each new one should follow directly after
the keyword "avlist_end" of its predessor image file list.
So to add or change the avatar lists to suit your needs just modify the names of the avatars and their urls of the matrixclientrc file
in a text editor and alter the image files in a graphics program to include pictures of your avatars.