Setting Up A Tiny Sandbox Shard - Revision history

Phoenix: correct

2011-08-09T18:21:15Z

correct

Phoenix: fix

2011-08-09T18:20:34Z

fix

Phoenix: edit

2011-08-09T18:18:59Z

edit

Phoenix: edit

2011-08-09T18:17:48Z

edit

Phoenix: edit

2011-08-09T18:09:34Z

edit

Phoenix: edit

2011-08-09T18:09:04Z

edit

Phoenix: fix

2011-08-09T17:08:47Z

fix

Phoenix: internal vs external client

2011-08-09T17:08:11Z

internal vs external client

Phoenix: format

2011-08-09T17:01:14Z

format

Phoenix: fix

2011-08-09T16:59:33Z

fix

← Older revision		Revision as of 18:21, 9 August 2011
Line 1:		Line 1:
−	==TINY SANDBOX SHARD ~~howto~~==	+	==TINY SANDBOX SHARD without Dataserver==

	===For Non-Programmers===		===For Non-Programmers===

@@ Line 1: / Line 1: @@
-== How to create a TINY SANDBOX SHARD without Dataserver ==
+==TINY SANDBOX SHARD howto==
 ===For Non-Programmers===
@@ Line 6: / Line 6: @@
 by Phoenix Rising
-version 0.02
+version 0.1
 August 2011

← Older revision		Revision as of 18:18, 9 August 2011
Line 688:		Line 688:

	Here is where you now hold your breath, because you are about to see if your recently compiled plClient.exe (and all the work you have done) can establish a connection with your shard.		Here is where you now hold your breath, because you are about to see if your recently compiled plClient.exe (and all the work you have done) can establish a connection with your shard.
		+
		+	== A Little History ==
		+
		+	Cyan has come a long way since the release of Myst. Their original 2D "point and click" game eventually evolved into a fully three dimensional gameplay with unrestricted movement and engaging avatar animations. Although Myst was the forefather of MOUL, in our wiki we wont be covering the MYST engine or how to set it up. It is too outdated. If you really want to play Myst you can use your original Myst CD content, Drizzle and TPOTS.
		+
		+	We need to draw a line as to what versions of Cyan's engine we use, and what purpose each version serves. Below is a list of the commonly accepted Versions.
		+
		+	Only one version will be used to setup our SANDBOX SHARD. The CWE Client using the MOULa content!
		+
		+
		+	* '''Choru''' - Cyan's Closed Beta.
		+	* '''Ubiru''' - Ubisoft's Closed Beta.
		+	* '''ABM''' - Ages Beyond Myst - The vanilla single player version of Uru.
		+	* '''Prologue''' - The original MMO version of Uru. (Essentially an Open Beta)
		+	* '''UruUpdate12''' - Update package to fix bug with ATI Graphics cards.
		+	* '''DNI''' - To D'ni Expansion Pack - an add-on extension that adds some of the Prologue Ages along with a recap of the Prologue story.
		+	* '''TPOTS''' - The Path of the Shell Expansion Pack - adds even more content to ABM.
		+	* '''CC''' - Complete Chronicles - a compilation of the first 4 packages as a single distribution.
		+	* '''UU''' - Untìl Uru - A no longer officially supported online version of ABM.
		+	* '''D'mala''' - The Cyan Worlds Until Uru Shard.
		+	* '''MOUL''' - Myst Online: Uru Live - The Third Online Incarnation of Uru
		+	* '''MOULagain / MOULa''' - Myst Online: Uru Live Again - Resurrected version of MOUL
		+
		+	and finally the Open Source Client that has been given to the community by Cyan Worlds, namely:
		+
		+	* '''CWE''' - CyanWorlds.com Engine - the recently released Open Source client based on MOUL - Note: not a full source release.
		+
		+
		+
		+	If you want to start building ages, we do not recommend following this wiki beyond the following few lines. There are many tutorials on the Guild of Writers to help you build your first age.

← Older revision		Revision as of 18:17, 9 August 2011
Line 567:		Line 567:
	* https://github.com/H-uru/moul-scripts		* https://github.com/H-uru/moul-scripts
	* http://guildofwriters.com/tools/devlibs.zip		* http://guildofwriters.com/tools/devlibs.zip
		+
		+
		+	====SETTING UP pgAdmin3====
		+
		+	To check if you have created a user successfully, you will need to download pgadmin3...
		+
		+	<pre>$ sudo apt-get install pgadmin3</pre>
		+
		+
		+	This will help you access postgres in a friendly gui environment. Setting up pgadmin3 is quite simple once it is installed. Click on "Applications" , "Programming" , "pgAdmin3"
		+
		+	The gui will launch. Once open click on the icon thats looks like an electrical plug to create a new server connection.
		+
		+	The fields should be exactly as below unless you changed them when you set up postgres a number of steps back.
		+
		+	Name: dirtsand
		+	Host: 127.0.0.1
		+	Port: 5432 - (leave this as it is)
		+	SSL: blank - (Not important right now... keep it simple)
		+	Maintenance DB: postgres
		+	Username: dirtsand
		+	Password: <whatever you chose for your password>
		+
		+
		+	Leave the rest of the window as it is. You will notice the windows has no "OK" button. Just after you entered your password, please "Enter" and the connection will be made. A dialog will pop up about "Saving passwords", read it and click "OK".
		+
		+
		+	If it fails, you entered something wrong, so try again by clicking on the plug icon.
		+
		+
		+	You know you have succeeded to login to the database when in the left hand pane you see;
		+
		+
		+	"Server Groups", below that "Servers", and below that "dirtsand"
		+
		+
		+	To check the new player you added, click on "dirtsand", then the + sign to the left of it to expand it. Then "Databases" , "dirtsand" , "Schemas" , "auth" , "Tables" , "Accounts"
		+
		+	Now, look for the little blue icon in the toolbar that looks like a spreadsheet... and click it.
		+
		+	You should be looking at your first account that you created with the command;
		+
		+	ds-902> addacct <username> <password>
		+
		+
		+	If you dont see the exact username you created, you will have to backtrack your steps in this wiki, and try to figure out where you went wrong.
		+
		+	If all looks well, save your connection... "File" , "Save Definition" , then give it a cool name like "Sandbox Shard" and click "Save" otherwise when you next launch pgAdmin3 you will have to manually reconnect again.
		+
		+
		+	====SETTING UP Wireshark====
		+
		+	This tool is very useful to check if your client is connecting to your Ubuntu shard. To install it run...
		+
		+	<pre>$ sudo apt-get install wireshark</source>
		+
		+	It is best to do a reboot, and when back in Ubuntu DON'T run it from the "Applications" menu...
		+
		+	Open a terminal, and type...
		+
		+	<pre>
		+	$ sudo wireshark
		+	</pre>
		+
		+	NOTE: If you run it from the App menu you won't find your ethernet controller.
		+
		+	Now, once wireshark has launched you will get a warning. Acknowledge it, and click "OK". Please don't do anything rash while using wireshark. Just follow these instructions.
		+
		+	Once you click "OK" you should be taken to the wireshark main interface. Look under Capture on the main page, and identify your ethernet controller. Generally it is called "eth0" but you may have some other configuration.
		+
		+	If you click on "eth0" wireshark will start to capture all traffic over that interface immediately. This is a good sign that wireshark and your ethernet controller are both working!
		+
		+	Stop the live capture by clicking on the icon with the little red cross.
		+
		+	Click on "Capture" in the top menu, and click "Options"
		+
		+	Now, be careful... the only field you want to fill out is the one to the right of "Capture Filter".
		+
		+	You will need to jump to your Windows box quickly and in a command terminal run
		+
		+	prompt:> ipconfig
		+
		+
		+	Look through the list and look for the IPv4 address for your computer... Something like this;
		+
		+	Ethernet adapter Local Area Connection:
		+
		+	Connection-specific DNS Suffix . :
		+	Link-local IPv6 Address . . . . . : **:::::%*
		+	IPv4 Address. . . . . . . . . . . : 124.122.23.11 '''<< Your IP address will be here!'''
		+	Subnet Mask . . . . . . . . . . . : 255.255.255.0
		+	Default Gateway . . . . . . . . . : 235.211.11.1
		+
		+
		+	Now back on Ubuntu fill in that field just mentioned, type;
		+
		+	<pre>
		+	host 124.122.23.11 (replace with whatever your IP is - the word "host" is crucial!)
		+	</pre>
		+
		+	Do not change any settings beside this, and simply click "START", then "Continue without Saving"
		+
		+	What this will do is ignore all other internet traffic except traffic from your Windows client. This makes reading wireshark much easier than having to sift through a ton of traffic!
		+
		+	The screen should be blank, so first we need to test the connection. First, in a new terminal on Ubuntu, run...
		+
		+	<pre>$ /sbin/ifconfig</pre>
		+
		+	Look for "inet addr" the IP address under "eth0" of your Sandbox and write it down. Take this to your Windows box.
		+
		+	On your Windows box, your command prompt should still be open after you ran ipconfig. Now run a ping command...
		+
		+	<pre>
		+	prompt:> ping *...* (type out the full IP address)
		+	</pre>
		+
		+	Now brace yourself, hehe! As you hit "enter" keep a beady eye on your Ubuntu wireshark screen. You should get about 10 lines of connection reports. This is great... your client is "seeing" your Server!
		+
		+	Now in wireshark on Ubuntu click "Capture" , "Restart" to clear the screen.
		+
		+	Here is where you now hold your breath, because you are about to see if your recently compiled plClient.exe (and all the work you have done) can establish a connection with your shard.

← Older revision		Revision as of 18:09, 9 August 2011
Line 456:		Line 456:


−	To setup your Tiny Sandbox Client you will need your compiled version of plClient and a new server.ini file~~. First, install MOULInstaller887.exe with your internet connection unplugged.~~	+	To setup your Tiny Sandbox Client you will need your compiled version of plClient and a new server.ini file.
−
−	Watch out when the installer finishes... it tries to connect to Cyan, so make sure you got your network cable unplugged temporarily. You don't want their updates for your shard! The reason is, Cyans content is based on python 2.3, and your shard only runs python 2.7.

	Then in the root of your fresh Sandbox installation do this:		Then in the root of your fresh Sandbox installation do this:

@@ Line 350: / Line 350: @@
 The -R flag will make sure "chown" changes the ownership of all files... recursively.
-==On Windows - Encrypted SDL and Python==
+==On Windows - Fresh Install, Encrypted SDL and Python==
-The two tools you will use is plPythonPack.exe that was compiled earlier on and PlasmaCrypt.exe in your 'Plasma_Win32' (libhsplasma) download.
+====Create a Fresh MOUL Installation====
 You will need the Win32 version of libhsPlasma to avoid any potential errors creeping in.

@@ Line 26: / Line 26: @@
 Each has their own advantages and disadvantages;
-* The Tiny Sandbox Shard - Internal Client Setup - is easy to setup, easy to maintain and can help you test CWE compatible ages quickly. However you need to make sure that each client has exactly the same content, and if you test ages on one machine, you need manually copy that content to the other machine as well.
+=====The Tiny Sandbox Shard - Internal Client Setup=====
-* The Sandbox Shard with Dataserver - External Client Setup - is useful for when you are planning (but not yet ready) to release your Shard to the public, and want to keep all the test clients that connect to your Shard in sync. It is quite a beast to setup and has confused a few pro's, so dont try this till until you have attempted the Tiny Sandbox Shard.
+is easy to setup, easy to maintain and can help you test CWE compatible ages quickly. However you need to make sure that each client has exactly the same content, and if you test ages on one machine, you need manually copy that content to the other machine as well.
 ====IMPORTANT NOTE====

@@ Line 125: / Line 125: @@
-An Undocumented item in the above tut: Just remember that you want to compile a 'Release' build. The default tut above compiles a 'debug' build. When you run a debug build it throws out errors with numerous dailog boxes, so it is preferable to build the 'Release' build for uninterrupted gameplay.
+====An Undocumented item in the above tut====
 Here is a brief comparison of the two builds and their dependancies; (You can find these dll's in the 'cwe-prefix' folder)
@@ Line 153: / Line 154: @@
 Now, time to delve into the SERVER. This is based on Zrax's heavily edited README for his Dirtsand server. It is assumed that you have Ubuntu 10.10 installed, and that you wrote down the superuser password somewhere safe!
 == On Ubuntu - DirtSand Howto ==

@@ Line 30: / Line 30: @@
 * The Sandbox Shard with Dataserver is useful for when you are planning (but not yet ready) to release your Shard to the public, and want to keep all the test clients that connect to your Shard in sync. It is quite a beast to setup and has confused a few pro's, so dont try this till until you have attempted the Tiny Sandbox Shard.
-=====IMPORTANT NOTE=====
+====IMPORTANT NOTE====
 This document gets highly technical, and as such is not recommended for newbies. This is almost complete so if you want to add to this wiki, please get persmission from the author first! We want this to appeal to every Non-Programmer young and old and have a really cool wiki to show for it. If you have helpful suggestions, drop the author a post. A lot of hard work has gone into documenting this procedure for the sake of all the Uru fans out there. At the end of the day all this effort is due to teamwork, since no-one can do such a mammoth task alone!