Important! Please read the announcement at http://myst.dustbird.net/uru-account.htm
Also! Please read the retirement announcement at http://myst.dustbird.net/uru-retirement.htm

Difference between revisions of "Talcum/Getting Started"

From UamWiki
(Created page with '=Talcum Walkthrough= This walkthrough is particular to Drizzle29. =Folder Layout= (We'll assume you'll put all the talcum files in c:\talcum, but any path should be fine.) c:…')
 
 
(3 intermediate revisions by the same user not shown)
Line 1: Line 1:
=Talcum Walkthrough=
+
This walkthrough will help you get Talcum and a client up and running!
This walkthrough is particular to Drizzle29.
+
 
 +
We'll use Drizzle29, as older versions aren't as easy to use.
  
  
 
=Folder Layout=
 
=Folder Layout=
 
(We'll assume you'll put all the talcum files in c:\talcum, but any path should be fine.)
 
(We'll assume you'll put all the talcum files in c:\talcum, but any path should be fine.)
  c:/talcum/  //root
+
c:/talcum/  //root
  c:/talcum/fileserver  //fileserver root.  Assume that files in here can be seen by clients.
+
c:/talcum/fileserver  //fileserver root.  Assume that files in here can be seen by clients.
  c:/talcum/fileserver/install, game_clients, game_data  //these three folders are created by the dataserver generator, so you don't need to worry about them.
+
c:/talcum/fileserver/install, game_clients, game_data  //these three folders are created by the dataserver generator, so you don't need to worry about them.
  c:/talcum/fileserver/SecureDownload  //Where the "SecureDownloadQueue" files that are downloaded when Uru starts up are found.
+
c:/talcum/fileserver/SecureDownload  //Where the "SecureDownloadQueue" files that are downloaded when Uru starts up are found.
  c:/talcum/fileserver/SecureDownload/SDL, Python  //the subfolder containing the *unencrypted* Python and SDL files.
+
c:/talcum/fileserver/SecureDownload/SDL, Python  //the subfolder containing the *unencrypted* Python and SDL files.
  c:/talcum/fileserver/agefiles  //contains the .age files that the server needs (they are put there by the dataserver generator, so you don't need to worry about it.)
+
c:/talcum/fileserver/agefiles  //contains the .age files that the server needs (they are put there by the dataserver generator, so you don't need to worry about it.)
 +
 
 +
 
 +
=Step 1: Getting the secure download files=
 +
*Use the command-line interface (you can still do this from the Drizzle GUI using the Advanced->CommandLine tab.
 +
-downloadsecuremoulagainfiles YourMoulagainUsername YourMoulagainPassword c:/talcum/fileserver/SecureDownload
 +
*You can check the folder afterwards to make sure the files show up there!
 +
 
 +
 
 +
=Step 2: Getting the regular files=
 +
*We'll use the command-line interface again
 +
*(The output folder can actually be any folder, because Talcum won't access them directly.  We'll tell the DataserverGenerator where to find them later.)
 +
-downloadmoulagainfiles c:/talcum/DataserverSourceFiles
 +
*(This may take a long while, and you can check the output folder for progress.)
 +
 
 +
 
 +
=Step 3: Patching the .exe files=
 +
*Using the command-line interface:
 +
*(Where yourServerAddress can be either a dns name or ip address, e.g.: example.com or 127.0.0.7  The name may be too long to fit, and Drizzle will give you an error if this is the case.
 +
-patachmoulbinary c:\talcum\DataserverSourceFiles/UruSetup.exe yourServerAddress
 +
-patachmoulbinary c:\talcum\DataserverSourceFiles/UruExplorer.exe yourServerAddress
 +
(In Drizzle30 and newer, that typo is fixed, and so it will be "-patchmoulbinary".)
 +
 
  
 +
=Step 4: Plasma's avi bug workaround=
 +
*(Plasma has a bug where it crashes if it tries to download its first avi file in-game.)
 +
*Create a text file called c:\talcum\DataserverSourceFiles\avi\readme.txt  (It doesn't need anything in it.)
 +
*Create a text file called c:\talcum\DataserverSourceFiles\DrizzleDataserverOverrides.txt  (This is a file that tells Drizzle to associate certain files with certain Ages.)
 +
**Inside this DrizzleDataserverOverrides.txt file, put the following line:
 +
/avi/readme.txt{->}client.mfs
 +
*(This makes sure that the client will create the avi folder before it gets to the in-game downloader.)
  
Step 1: Getting the secure download files
 
Use the command-line interface (you can still do this from the Drizzle GUI using the Advanced->CommandLine tab.
 
-downloadsecuremoulagainfiles YourMoulagainUsername YourMoulagainPassword c:/talcum/fileserver/SecureDownload
 
You can check the folder afterwards to make sure the files show up there!
 
  
Step 2: Getting the regular files
+
=Step 5: Generating the dataserver files=
We'll use the command-line interface again
+
*Using the command-line interface(Change the path to DataserverSourceFiles if you saved them somewhere else in the earlier step.)
(The output folder can actually be any folder, because Talcum won't access them directly.  We'll tell the DataserverGenerator where to find them later.)
+
*(By the way, this is also the same command we use when generating the dataserver for Alcugs shards.)
-downloadmoulagainfiles c:/talcum/DataserverSourceFiles
+
*(This step will take quite a long time the first time it is run, but if you later modify some of the files and re-run it, it will be much quicker.)
(This may take a long while, and you can check the output folder for progress.)
+
*(You'll get some errors about "Moul is listed as having type blah blah blah", but these are normal and can be ignored.)
 +
-generatedataserver c:\talcum\DataserverSourceFiles c:\talcum\fileserver
  
Step 3: Patching the .exe files
 
Using the command-line interface:
 
(Where yourServerAddress can be either a dns name or ip address, e.g.: example.com or 127.0.0.7  The name may be too long to fit, and Drizzle will give you an error if this is the case.
 
-patachmoulbinary c:\talcum\DataserverSourceFiles/UruSetup.exe yourServerAddress
 
-patachmoulbinary c:\talcum\DataserverSourceFiles/UruExplorer.exe yourServerAddress
 
  
Step 4: Plasma's avi bug workaround
+
=Step 6: Starting Talcum=
(Plasma has a bug where it crashes if it tries to download its first avi file in-game.)
+
*First, make sure TCP port 14617 and TCP port 80 aren't blocked by a firewall to your server.
Create a text file called c:\talcum\DataserverSourceFiles\avi\readme.txt (It doesn't need anything in it.)
+
*Secondly, if you have a webserver already running on this server, the Talcum web server won't be able to start.  (Which might be okay, but the status messages and admin interface won't work.) (Oh, also, regular users can open port 80 on Linux machines, unless you change some settings. Windows has no problems.)
Create a text file called c:\talcum\DataserverSourceFiles\DrizzleDataserverOverrides.txt  (This is a file that tells Drizzle to associate certain files with certain Ages.)
+
*Using the command-line interface:
Inside this DrizzleDataserverOverrides.txt file, put the following line:
+
*(MainPassword is what you want the password to be to login to the Admin interface. "yourServerAddress" is the same address you provided above.)
/avi/readme.txt{->}client.mfs
+
-startmoulserver MainPassword yourServerAddress c:/talcum
(This makes sure that the client will create the avi folder before it gets to the in-game downloader.)
 
  
Step 5: Generating the dataserver files
 
Using the command-line interface:  (Change the path to DataserverSourceFiles if you saved them somewhere else in the earlier step.)
 
(By the way, this is also the same command we use when generating the dataserver for Alcugs shards.)
 
(This step will take quite a long time the first time it is run, but if you later modify some of the files and re-run it, it will be much quicker.)
 
(You'll get some errors about "Moul is listed as having type blah blah blah", but these are normal and can be ignored.)
 
-generatedataserver c:\talcum\DataserverSourceFiles c:\talcum\fileserver
 
  
Step 6: Starting Talcum
+
=Step 7: Creating an account=
First, make sure TCP port 14617 and TCP port 80 aren't blocked by a firewall to your server.
+
*Go to yourserver.com/admin.html and put in the MainPassword you gave above, and to the left of the "Add User" button fill in a username and password. Then click "Add User".  (Usernames that are in the form of an email address are treated differently than ones that are not. I test with ones that are *not* in the form of an email address, but both may work.)
Secondly, if you have a webserver already running on this server, the Talcum web server won't be able to start.  (Which might be okay, but the status messages and admin interface won't work.) (Oh, also, regular users can open port 80 on Linux machines, unless you change some settingsWindows has no problems.)
 
Using the command-line interface:
 
(MainPassword is what you want the password to be to login to the Admin interface. "yourServerAddress" is the same address you provided above.)
 
-startmoulserver MainPassword yourServerAddress c:/talcum
 
  
Step 7: Creating an account
 
Go to yourserver.com/admin.html and put in the MainPassword you gave above, and to the left of the "Add User" button fill in a username and password. Then click "Add User".
 
  
Step 8: The Client
+
=Step 8: The Client=
All you have to do is copy c:\talcum\DataserverSourceFiles\UruLauncher.exe to where you want the client installed, and running it should get everything going!
+
*All you have to do is copy c:\talcum\DataserverSourceFiles\UruLauncher.exe to where you want the client installed, and running it should get everything going!
Cross your fingers and hope for the best!!
+
*Cross your fingers and hope for the best!!

Latest revision as of 19:19, 26 October 2010

This walkthrough will help you get Talcum and a client up and running!

We'll use Drizzle29, as older versions aren't as easy to use.


Folder Layout

(We'll assume you'll put all the talcum files in c:\talcum, but any path should be fine.)

c:/talcum/   //root
c:/talcum/fileserver   //fileserver root.  Assume that files in here can be seen by clients.
c:/talcum/fileserver/install, game_clients, game_data   //these three folders are created by the dataserver generator, so you don't need to worry about them.
c:/talcum/fileserver/SecureDownload   //Where the "SecureDownloadQueue" files that are downloaded when Uru starts up are found.
c:/talcum/fileserver/SecureDownload/SDL, Python   //the subfolder containing the *unencrypted* Python and SDL files.
c:/talcum/fileserver/agefiles  //contains the .age files that the server needs (they are put there by the dataserver generator, so you don't need to worry about it.)


Step 1: Getting the secure download files

  • Use the command-line interface (you can still do this from the Drizzle GUI using the Advanced->CommandLine tab.
-downloadsecuremoulagainfiles YourMoulagainUsername YourMoulagainPassword c:/talcum/fileserver/SecureDownload
  • You can check the folder afterwards to make sure the files show up there!


Step 2: Getting the regular files

  • We'll use the command-line interface again
  • (The output folder can actually be any folder, because Talcum won't access them directly. We'll tell the DataserverGenerator where to find them later.)
-downloadmoulagainfiles c:/talcum/DataserverSourceFiles
  • (This may take a long while, and you can check the output folder for progress.)


Step 3: Patching the .exe files

  • Using the command-line interface:
  • (Where yourServerAddress can be either a dns name or ip address, e.g.: example.com or 127.0.0.7 The name may be too long to fit, and Drizzle will give you an error if this is the case.
-patachmoulbinary c:\talcum\DataserverSourceFiles/UruSetup.exe yourServerAddress
-patachmoulbinary c:\talcum\DataserverSourceFiles/UruExplorer.exe yourServerAddress

(In Drizzle30 and newer, that typo is fixed, and so it will be "-patchmoulbinary".)


Step 4: Plasma's avi bug workaround

  • (Plasma has a bug where it crashes if it tries to download its first avi file in-game.)
  • Create a text file called c:\talcum\DataserverSourceFiles\avi\readme.txt (It doesn't need anything in it.)
  • Create a text file called c:\talcum\DataserverSourceFiles\DrizzleDataserverOverrides.txt (This is a file that tells Drizzle to associate certain files with certain Ages.)
    • Inside this DrizzleDataserverOverrides.txt file, put the following line:
/avi/readme.txt{->}client.mfs
  • (This makes sure that the client will create the avi folder before it gets to the in-game downloader.)


Step 5: Generating the dataserver files

  • Using the command-line interface: (Change the path to DataserverSourceFiles if you saved them somewhere else in the earlier step.)
  • (By the way, this is also the same command we use when generating the dataserver for Alcugs shards.)
  • (This step will take quite a long time the first time it is run, but if you later modify some of the files and re-run it, it will be much quicker.)
  • (You'll get some errors about "Moul is listed as having type blah blah blah", but these are normal and can be ignored.)
-generatedataserver c:\talcum\DataserverSourceFiles c:\talcum\fileserver


Step 6: Starting Talcum

  • First, make sure TCP port 14617 and TCP port 80 aren't blocked by a firewall to your server.
  • Secondly, if you have a webserver already running on this server, the Talcum web server won't be able to start. (Which might be okay, but the status messages and admin interface won't work.) (Oh, also, regular users can open port 80 on Linux machines, unless you change some settings. Windows has no problems.)
  • Using the command-line interface:
  • (MainPassword is what you want the password to be to login to the Admin interface. "yourServerAddress" is the same address you provided above.)
-startmoulserver MainPassword yourServerAddress c:/talcum


Step 7: Creating an account

  • Go to yourserver.com/admin.html and put in the MainPassword you gave above, and to the left of the "Add User" button fill in a username and password. Then click "Add User". (Usernames that are in the form of an email address are treated differently than ones that are not. I test with ones that are *not* in the form of an email address, but both may work.)


Step 8: The Client

  • All you have to do is copy c:\talcum\DataserverSourceFiles\UruLauncher.exe to where you want the client installed, and running it should get everything going!
  • Cross your fingers and hope for the best!!