OpenUru - User contributions [en]

Build the client with MSVC 2010 Express

2020-11-09T16:46:33Z

Rarified: Remove most of the source changes needed for VS2010 after changing repository head to include those changes.

{{UruDocProj}}

== Introduction ==
This document provides steps to build the CWE client with MSVC 2010 SP1 Express.

== Before you begin ==
* If you have a version of Visual Studio later than 2010 installed, you may need to uninstall it.
* If you have Microsoft Visual C++ 2010 Redistributable installed (x86 and/or x64), [https://support.microsoft.com/en-us/help/2728613/s1023-error-when-you-install-the-directx-sdk-june-2010 you will need to uninstall it before installing DirectX SDK]. While installing Visual Studio, the Redistributable package(s) will be reinstalled for you automatically.

== Items needed to compile ==
See [[Build the client with MSVC 2010 Express|Build preparation steps]] for installation instructions!
* [https://git-scm.com/download/win git] (recommended but not required)
* [https://foundry.openuru.org/gitblit/summary/?r=CWE-ou.git The CWE OpenUru source code] - this does not include the Python code, which can be found in the [https://foundry.openuru.org/gitblit/summary/?r=MOULSCRIPT-ou.git MOULSCRIPT repo]
* [https://www.microsoft.com/en-us/download/details.aspx?id=6812 DirectX 9.0c SDK (June 2010)]
* [https://my.visualstudio.com/Downloads?q=visual%20studio%202010&wt.mc_id=o~msft~vscom~older-downloads Microsoft Visual Studio 2010 SP1 Express] - This will be in two downloads, you'll need to search for and download both "Visual Studio 2010 VC Express" and "Visual Studio 2010 Service Pack 1".
* [https://www.openal.org/downloads/OpenAL11CoreSDK.zip OpenAL v1.1 SDK]
* [http://developer.download.nvidia.com/PhysX/2.6.4/PhysX_2.6.4_SDK_Core.exe Ageia PhysX 2.6.4 Core SDK]
* [http://downloads.xiph.org/releases/ogg/libogg-1.3.2.zip libogg-1.3.2]
* [http://downloads.xiph.org/releases/vorbis/libvorbis-1.3.6.zip libvorbis-1.3.6]
* [https://www.openssl.org/source/openssl-1.0.2t.tar.gz OpenSSL 1.0.2t]
* [https://www.zlib.net/fossils/zlib-1.2.7.tar.gz zlib 1.2.7]
* [https://ftp-osl.osuosl.org/pub/libpng/src/archive/gz/libpng15/libpng-1.5.12.tar.gz libpng 1.5.12]
Newer versions of these libraries may work, but no guarantees are offered; these are what have been tested. See the next section for restrictions on using newer versions.

== Notes ==
* This guide assumes you are going to use the 7.0A SDK installed with Visual Studio 2010, and are using a 64 bit Windows install.
* You can upgrade to a newer version of Speex if you like, but you will need to fix the Speex VS2010 projects first (by removing the architectures we do not have from the Speex project files).
* Libogg 1.3.2 was used because xiph removed the VS2010 projects from 1.3.3 and above.
* You must use a 2.6.x version of PhysX for CWE, because the cooked mesh format was changed in PhysX 2.7.x and later.
* All libraries are compiled with "Whole Program Optimization" turned off.
* Release version libraries are compiled as "Multi-threaded DLL (/MD)"
* Debug version libraries are compiled as "Multi-threaded Debug DLL (/MDd)"
* Crypto keys are located in "CWE-ou\MOULOpenSourceClientPlugin\Plasma20\Sources\Plasma\NucleusLib\pnNetBase". Edit the *.hpp files with a text editor to replace Cyan's keys with your own server's keys. Always clean your solution and rebuild when you change crypto keys, to make sure they are updated.
* Server hostnames, IP addresses, and ports are located in the following files:
: The status URL:
:: "CWE-ou\MOULOpenSourceClientPlugin/Plasma20/Sources/Plasma/Apps/plClient/winmain.cpp"
:: "CWE-ou\MOULOpenSourceClientPlugin/Plasma20/Sources/Plasma/Apps/plUruLauncher/Main.cpp"
: The auth/gatekeeper address
:: "CWE-ou\MOULOpenSourceClientPlugin/Plasma20/Sources/Plasma/NucleusLib/pnNetBase/Private/pnNbSrvs.cpp"
: The default client port
:: "CWE-ou\MOULOpenSourceClientPlugin/Plasma20/Sources/Plasma/NucleusLib/pnNetBase/pnNbConstant.h"

== Build preparation steps ==

=== git (Optional) ===
If you plan to make changes to the source code and contribute to the community, install git (accepting the default options).

=== CWE-ou ===
Obtain CWE-OU source by one of these methods:
* Use '''git clone''' with the repository link found on the webpage referenced above
* Click "tree" in the top menu of the webpage reference above, then click "zip" to download a ZIP archive

=== DirectX ===
Install the DirectX 9.0c SDK and copy it to "CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\DX9.0c".
Install the DirectX SDK before you install VS2010 Express, or the DirectX SDK install will throw error S1023, due to a newer version of the C++ 2010 redistributables being installed.
Directory structure in the CWE tree will look like this:
<pre>
StaticSDKs
Win32
DX9.0c
include
Lib
</pre>


=== Visual Studio 2010 Express ===

* Install Visual Studio 2010 Express
* Install Service Pack 1 (SP1) for Visual Studio 2010, plus security updates (run Windows Update a few times)
* Copy the include and lib directories from the SDK installed with VS2010 SP1 Express to "CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\PlatformSDK". The directory where the SDK resides will most likely be "Program Files (x86)\Microsoft SDKs\Windows\v7.0A". As the SDK is in our path, this step is probably not necessary but we will do it for consistency.
Directory structure in the CWE tree will look like this:
<pre>
StaticSDKs
Win32
PlatformSDK
include
lib</pre>


=== OpenAL SDK ===
Install the OpenAL SDK and copy the include and lib directories to "CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\OpenAL 1.1 with EFX SDK"
Directory structure in the CWE tree will look like this:
<pre>
StaticSDKs
win32
OpenAL 1.1 with EFX SDK
include
libs
</pre>


=== PhysX SDK ===
Install PhysX SDK, and copy PhysX subdirectories as follows:
* Copy from "Program Files (x86)\AGEIA Technologies\AGEIA PhysX SDK\v2.6.4\SDKs" to "CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\PhysX"
* Copy from and "Program Files (x86)\AGEIA Technologies\AGEIA PhysX SDK\v2.6.4\Bin" to "CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\PhysX"
Directory structure in the CWE tree will look like this:
<pre>
StaticSDKs
Win32
PhysX
Bin
Cooking
Docs
Foundation
Framework
lib
...</pre>


=== libogg and libvorbis ===

Build Ogg and Vorbis
<ol style="list-style-type:lower-latin">
<li>Create a directory and extract Ogg and Vorbis archives to it.
<pre>
oggvorbis
libogg-1.3.2
libvorbis-1.3.6</pre>
</li>
<li>Change directory to "libvorbis-1.3.6\win32\vs2010" and edit the libogg.props file. Make sure the "LIBOGG_VERSION" value matches your version of Ogg (1.3.2 in this document).</li>
<li>Open "libogg-1.3.2\win32\VS2010\libogg_static.sln" in the Visual Studio IDE and perform the following steps:</li>
<ol style="list-style-type:lower-latin">
<li>On the IDE toolbar, click on configuration drop down at the upper left (it defaults to "Debug") and change it to "Release"</li>
<li>Right click on the project (e.g. "libogg_static") in the Solution Explorer at upper left, and select Properties.</li>
<li>In the panel that opens, set (or verify) the following items as follows:
{| class="wikitable"
!Left Pane
!Right pane parameter
!Right pane value (drop down)
|-
|Configuration Properties -> General
|Whole Program Optimization
|No Whole Program Optimization
|-
|C/C++ -> Optimization
|Whole Program Optimization
|No
|-
|C/C++ Code Generation
|Runtime Library
|Multi-threaded DLL (/MD)
|}
<li>Click on "Apply"</li>
<li>Click on configuration drop down at the upper left of the panel and select "Debug". Set (or verify) the following items as follows, noting that the 3rd item is not the same as in the previous list.</li>
{| class="wikitable"
!Left Pane
!Right pane parameter
!Right pane value (drop down)
|-
|Configuration Properties -> General
|Whole Program Optimization
|No Whole Program Optimization
|-
|C/C++ -> Optimization
|Whole Program Optimization
|No
|-
|C/C++ Code Generation
|Runtime Library
|Multi-threaded Debug DLL (/MDd)
|}
</li>
<li>Click "Apply" and then "OK". </li>
<li>On the IDE toolbar, verify the configuration drop down is still set to "Release". Then right click on the project in the solution explorer and select "Build". </li>
<li>On the IDE toolbar, select "Debug" from the drop down. Then right click on the project in the solution explorer and select "Build".</li>
</ol>
<li>Open "libvorbis-1.3.6\win32\VS2010\vorbis_static.sln" in the Visual Studio IDE, and repeat the preceding steps for projects libvorbis_static and libvorbisfile.</li>
</ol>

Copy Ogg and Vorbis files to CWE
<ol style="list-style-type:lower-latin">
<li>Copy the ogg and vorbis include directories into "CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\xiph\include". It is okay to let it overwrite.
<li> Copy the "libogg-1.3.2\win32\VS2010\Win32\Release" and "Debug" directories into "CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\xiph\lib"</li>
<li> Copy the "libvorbis-1.3.6\win32\VS2010\Win32\Release" and "Debug" directories to "CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\xiph\lib"</li>
</ol>
Directory structure in the CWE tree will look like this:
<pre>
StaticSDKs
win32
xiph
include
ogg
vorbis
lib
Debug
Release</pre>


=== Speex ===

Rebuild the Speex 1.0.1 included in the CWE tree.
<ol style="list-style-type:lower-latin">
<li>Open CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\speex-1.0.1\win32\libspeex\libspeex.sln in the Visual Studio 2010 IDE, and convert.</li>
<li>Click on configuration drop-down on the upper left and select "Release"</li>
<li>Right click on project in the solution explorer and select properties.</li>
<li>In the panel that opens, set (or verify) the following items as follows:
{| class="wikitable"
!Left Pane
!Right pane parameter
!Right pane value (drop down)
|-
|Configuration Properties -> General
|Whole Program Optimization
|No Whole Program Optimization
|-
|C/C++ -> Optimization
|Whole Program Optimization
|No
|-
|C/C++ Code Generation
|Runtime Library
|Multi-threaded DLL (/MD)
|}
<li>Click on "Apply".</li>
<li>Click on configuration drop-down on the upper left of the properties page and select "Debug". Set (or verify) the following items as follows, noting that the 3rd item is not the same as in the previous list.</li>
{| class="wikitable"
!Left Pane
!Right pane parameter
!Right pane value (drop down)
|-
|Configuration Properties -> General
|Whole Program Optimization
|No Whole Program Optimization
|-
|C/C++ -> Optimization
|Whole Program Optimization
|No
|-
|C/C++ Code Generation
|Runtime Library
|Multi-threaded Debug DLL (/MDd)
|}
</li>
<li> Click "Apply" and then "OK". </li>
<li> On the IDE toolbar, select "Release" from the drop down. then right click on the project in the solution explorer and select "Build".</li>
<li> On the IDE toolbar, select "Debug" from the drop down. then right click on the project in the solution explorer and select "Build".</li>
<li>Copy the headers (.h files) from CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\speex-1.0.1\libspeex to CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\xiph\include\speex</li>
<li> Copy CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\speex-1.0.1\win32\libspeex\Release\libspeex.lib to CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\xiph\lib\Release</li>
<li> Copy CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\speex-1.0.1\win32\libspeex\Debug\libspeex.lib to CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\xiph\lib\Debug</li>
</ol>

=== OpenSSL ===
Compile and install OpenSSL (see [[Build OpenSSL with MS Visual C++]]), or obtain [https://wiki.openssl.org/index.php/Binaries precompiled binaries] (32-bit, not 64-bit).
If compiling it yourself, you can choose either static or dynamic linking. '''Note:''' If you link it dynamically, it will cause the Uru client to require the OpenSSL DLLs to be present in the client directory or in the system path.
Copy the installed OpenSSL files to "CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\Win32\OpenSSL".
Directory structure in the CWE tree will look like this:
<pre>
StaticSDKs
Win32
OpenSSL
bin
include
openssl
lib</pre>


=== JPEG ===
Build in-tree JPEG library
<ol style="list-style-type:lower-latin">
<li>Open "Visual Studio Command Prompt (2010)" and change to the "CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\XPlatform\jpeg-8c-rgba directory."</li>
<li>Copy makefile.vc to makefile.nmake</li>
<li>Copy jconfig.vc to jconfig.h</li>
<li>Run ''nmake nodebug=1 -f makefile.nmake''. This will build the library in non-debug mode. If you use a debug library, the linker will complain when we link the client executable.</li>
</ol>

=== zlib and libpng ===
Build zlib and libpng
<ol style="list-style-type:lower-latin">
<li>Extract the files in the zlib archive to ''MOULOpenSourceClientPlugin/StaticSDKs/XPlatform/zlib''.</li>
<li>Extract the files in the libpng archive to ''MOULOpenSourceClientPlugin/StaticSDKs/XPlatform/png''.</li>
<li>Edit the ''png/projects/vstudio/zlib.props'' file. Towards the bottom is a path for ZLibSrcDir. Change the value to "..\..\..\..\zlib" (no -1.2.5 or such on the end) and save the file.</li>
<li>Open ''png/projects/vstudio/vstudio.sln'' in the Visual Studio 2010 IDE.</li>
<li>On the IDE toolbar, click on the configuration drop down at the upper left (it defaults to "Debug") and change it to "Release Library".</li>
<li>The VS2010 zlib project file distributed in the png archive is set to build for embedded environments. We need to reconfigure it.</li>
<ol style="list-style-type:lower-latin">
<li>Right click on the zlib project tree in the solution explorer and select "Add > Existing item"</li>
<li>Browse to the zlib source directory (CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\XPlatform\zlib) and select the gzclose.c, gzlib.c, gzread.c, and gzwrite.c files (hold Ctrl while clicking to select multiple files).</li>
<li>Click "Add".</li>
<li>Right click on the zlib project in the solution explorer and select ''Properties''.</li>
<li>In the panel that opens, set (or verify) the following items as follows:
{| class="wikitable"
!Left Pane
!Right pane parameter
!Right pane value (drop down)
|-
|Configuration Properties > C/C++ > Preprocessor
|Preprocessor Definitions
|''Remove '''Z_SOLO''' if present, leave everything else alone''
|}
</li>
<li>Click "Apply" and then "OK".
</ol>
<li>Repeat the following steps for each of these projects: "libpng", "pngtest", "pngvalid", and "zlib".</li>
<ol style="list-style-type:lower-latin">
<li>Right-click on the project in the ''Solution Explorer'' and choose ''Properties''.</li>
<li>In the panel that opens, set (or verify) the following items as follows:
{| class="wikitable"
!Left Pane
!Right pane parameter
!Right pane value (drop down)
|-
|Configuration Properties > General
|Project Defaults > Whole Program Optimization
|No Whole Program Optimization
|-
|Configuration Properties > C/C++ > Optimization
|Whole Program Optimization
|No
|-
|Configuration Properties > C/C++ > Code Generation
|Runtime Library
|Multi-threaded DLL (/MD)
|}
</li>
<li>Click "Apply".</li>
<li>Click on the configuration drop down at the upper left of the panel and select "Debug Library".</li>
<li>Set (or verify) the following items as follows, noting that the 4th item is not the same as in the previous list.
{| class="wikitable"
!Left Pane
!Right pane parameter
!Right pane value (drop down)
|-
|Configuration Properties > General
|Project Defaults > Whole Program Optimization
|No Whole Program Optimization
|-
|Configuration Properties > C/C++ > General
|Treat Warnings As Errors
|No (/WX-)
|-
|Configuration Properties > C/C++ > Optimization
|Whole Program Optimization
|No
|-
|Configuration Properties > C/C++ > Code Generation
|Runtime Library
|Multi-threaded Debug DLL (/MDd)
|}
</li>
<li>Click "Apply" and "OK".
<li>(Remember you need to follow these steps four times, once each for libpng, pngtest, pngvalid, AND zlib!)
</ol>
<li>Select “Debug Library” from the ''Solution Configurations'' drop down in the IDE toolbar, then right click the top line in the Solution Explorer (Solution 'vstudio') and choose ''Build Solution''.</li>
<li>Select the “Release Library” configuration, and build the solution.</li>
<li>In the ''CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\XPlatform\png'' folder, create a ''lib'' folder. Then:</li>
<ul>
<li>Copy ''png/projects/vstudio/Debug Library/libpng15.lib'' to ''CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\XPlatform\png\lib'' and rename it ''libpngd.lib''</li>
<li>Copy ''png/projects/vstudio/Release Library/libpng15.lib'' to ''CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\XPlatform\png\lib'' and rename it ''libpng.lib''</li>
</ul>
<li>In the ''CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\XPlatform\zlib'' folder, create a ''lib'' folder. Then:</li>
<ul>
<li>Copy ''png/projects/vstudio/Debug Library/zlib.lib'' to ''CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\XPlatform\zlib\lib'' and rename it ''zlibd.lib''</li>
<li>Copy ''png/projects/vstudio/Release Library/zlib.lib'' to ''CWE-ou\MOULOpenSourceClientPlugin\StaticSDKs\XPlatform\zlib\lib''</li>
</ul>
</ol>

== Required source code changes for newer version of DirectX SDK ==
Revisions of the client source code after November 2020 (newer than the branch marked '''VS2003_FINAL''') no longer require any changes to compile under Visual Studio 2010. To compile with the Express version of VS2010, you still need the changes marked below.

== Required source changes for Visual Studio 2010 Express ==
<ul>
<li>We do not have MFC with VS2010 SP1 Express, so we need to replace the first reference to afxres.h. The client portion of CWE does not use MFC (I believe the MAX plugin does), so we can make this replacement.</li> 
Note: If you are compiling with VS2010 Professional or greater, you do *not* need to make these edits. Only the Express edition excludes MFC. 
 
<li>Edit '''plClient.rc''' file located in "CWE-ou\MOULOpenSourceClientPlugin\Plasma20\Sources\Plasma\Apps\plClient\res\" 
'''Before''' 
<pre>
// Microsoft Visual C++ generated resource script.
//
#include "resource.h"

#define APSTUDIO_READONLY_SYMBOLS
/////////////////////////////////////////////////////////////////////////////
//
// Generated from the TEXTINCLUDE 2 resource.
//
#include "afxres.h"
</pre>
'''After''' 
<pre>
// Microsoft Visual C++ generated resource script.
//
#include "resource.h"

#define APSTUDIO_READONLY_SYMBOLS
/////////////////////////////////////////////////////////////////////////////
//
// Generated from the TEXTINCLUDE 2 resource.
//
//#include "afxres.h"

#include <windows.h>
#define IDC_STATIC (-1)
</pre></li>
<li>edit '''plUruLauncher.rc''' file located in "CWE-ou\MOULOpenSourceClientPlugin\Plasma20\Apps\plUruLauncher\" 
This is the same change we just made in the previous file. 
'''Before''' 
<pre>
// Microsoft Visual C++ generated resource script.
//
#include "resource.h"

#define APSTUDIO_READONLY_SYMBOLS
/////////////////////////////////////////////////////////////////////////////
//
// Generated from the TEXTINCLUDE 2 resource.
//
#include "afxres.h"
</pre>
'''After''' 
<pre>
// Microsoft Visual C++ generated resource script.
//
#include "resource.h"

#define APSTUDIO_READONLY_SYMBOLS
/////////////////////////////////////////////////////////////////////////////
//
// Generated from the TEXTINCLUDE 2 resource.
//
//#include "afxres.h"

#include <windows.h>
#define IDC_STATIC (-1)
</pre></li>
</ul>

== Build the client ==
Now that the prep is done, you can actually build the client.
<ol>
<li> Open the "CWE-ou\MOULOpenSourceClientPlugin\Plasma20\MSVC10Projects\Plasma\Apps\AllClient\AllClient.sln" in the VS2010 IDE.</li>
<li> Select the type of build you want from the dropdown on the IDE toolbar.
* Release
* Release_Internal
* Debug
* Debug_Internal
</li>
<li> Right click on the "AllClient" project and select "Build".</li>
 
Completed builds are copied into the "CWE-ou\MOULOpenSourceClientPlugin\Plasma20\test" directory.
 
'''Note:''' You '''*must*''' make sure your client is using the same versions of the PhysX DLLs that you built with. They are not compatible from version to version.
</ol>

If, after building the client, you require the server prep tools (plFileSecure, plFileEncrypt, plPythonPak), right click on those specific projects and click "Build". 
The compiled files will be copied into the "CWE-ou\MOULOpenSourceClientPlugin\Plasma20\tools" directory.

[[Category:Cyan_Worlds]]

Build the client with MSVC 2003

2020-11-09T16:39:08Z

Rarified: Note the deprecation of Visual Studio 2003 as a usable build tool after November 2020.

{{UruDocProj}}
== Introduction ==
This document provides steps to build the CWE client with minimal changes from the initial Cyan source release. It is assumed that you have the initial Cyan source commit, the four commits made by a'moaca (add jpeg-8c library, remove EAX, replace IJL with IJG, and remove Bink), and the one made by cjkelly1 (modify the MsDevProjects and add batch files) in your source tree. Be aware that subsequent commits by other developers may invalidate these instructions.

== Notes about Building with Visual Studio 2003 .NET ==
As of November 2020, the main branch of the CWE client source code has ceased to be able to build with VS2003.NET by default. With alterations the current head of the repository might be able to compile with VS2003, but this no longer is guaranteed. Newer additions to the client need to take advantage of C++ features not available in VS2003.

The last revision (commit) in the repositories that were intended to be built with VS2003 are marked by the branch '''VS2003_FINAL'''. By checking out that branch, you should be able to follow the instructions below without issue.

== Items needed to compile ==
* Microsoft Visual Studio 2003 .NET
* Microsoft Platform SDK February 2003 edition (build 5.2.3790.0) (see links and note below)
* [http://www.microsoft.com/downloads/en/details.aspx?familyid=1c8dc451-2dbe-4ecc-8c57-c52eea50c20a&displaylang=en&pf=true Microsoft DirectX 9.0 SDK (October 2005)]
** Mirror: [https://archive.org/details/dxsdk_oct2005 Archive.org]
* [http://www.openssl.org/source/openssl-0.9.8q.tar.gz OpenSSL 0.9.8q]
* [http://downloads.xiph.org/releases/ogg/libogg-1.2.0.zip libogg-1.2.0]
* [http://downloads.xiph.org/releases/vorbis/libvorbis-1.2.0.zip libvorbis-1.2.0]
* [http://connect.creativelabs.com/openal/Downloads/OpenAL11CoreSDK.zip OpenAL v1.1 SDK]
* [http://developer.download.nvidia.com/PhysX/2.6.4/PhysX_2.6.4_SDK_Core.exe Ageia PhysX 2.6.4 Core SDK]

== Instructions to obtain the Microsoft Platform SDK February 2003 edition ==

The old MS Platform SDK is no longer available as a single package from Microsoft. You will have to either order it for $10 from MS, or download the parts and build the install yourself. To build it yourself, download the files from the below links into the same directory.

[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.1.cab PSDK-FULL.1.cab] 
[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.2.cab PSDK-FULL.2.cab] 
[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.3.cab PSDK-FULL.3.cab] 
[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.4.cab PSDK-FULL.4.cab] 
[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.5.cab PSDK-FULL.5.cab] 
[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.6.cab PSDK-FULL.6.cab] 
[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.7.cab PSDK-FULL.7.cab] 
[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.8.cab PSDK-FULL.8.cab] 
[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.9.cab PSDK-FULL.9.cab] 
[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.10.cab PSDK-FULL.10.cab] 
[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.11.cab PSDK-FULL.11.cab] 
[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.12.cab PSDK-FULL.12.cab] 
[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.13.cab PSDK-FULL.13.cab] 
[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/PSDK-FULL.bat PSDK-FULL.bat] 
[http://download.microsoft.com/download/platformsdk/sdk/update/win98mexp/en-us/3790.0/FULL/Extract.exe Extract.exe]

Run the batch file that is in the directory, and it will build the install. After doing this, you can either install the SDK directly, or burn it onto a CD so you will have it for later and install from there (I recommend burning to a CD, as this multi-part thing is a hassle).

'''Note on versions:''' I am using this older stuff because it is closest to what Cyan builds with. These instructions have only been tested with these specific versions. If you use other versions of the SDKs and such, you will have to adjust for the changes. If you do use different versions, it would be greatly appreciated if you would add a section to this document explaining what you had to do to use the newer versions, so everyone can benefit from your work.

== Build steps ==
<ol>
<li> Obtain CWE sources from the repository.</li>
<li> Install MS Platform SDK. You only need the "Core SDK" and the "Internet Development SDK". You do not need to use the setup.exe in the root of the SDK installer directory - this is merely a splash page and requires IE. Instead, go to the "setup" directory and run "CoreSDK-x86.msi" and then run "IESDK-x86.msi". Note that the "-ia64" installers are for Itanium 64 bit machines, and will not run in x64. '''Note:''' Do not copy the .msi files somewhere else and run them. They need to be run in the same directory as all the *.cab files.</li>
<li> Copy the include and lib directories from the SDK to "\CWE\MOULOpenSourceClientPlugin\StaticSDKs\Win32\PlatformSDK". '''Note:'''The directory where the SDK resides will be the one specified in the "Select An Installation Location" dialog when you ran the .msi files. This location will vary by platform. 
Directory structure in the CWE tree will look like this:
<pre>
StaticSDKs
Win32
PlatformSDK
include
lib</pre>
</li>
<li> Build libogg and libvorbis using MSVC 2003.</li>
<ol style="list-style-type:lower-latin">
<li>Create a directory and then create two subdirectories under it called "ogg" and "vorbis".</li>
<li>Unpack the sources into their respective directories. Make sure it does not do ogg\ogg-1.2.0, or some such thing. Vorbis depends on ogg, and it looks for the ogg stuff in ..\ogg.</li>
<li>Fire up MSVC 2003.</li>
<li>Do File -> Open -> Project, and select the ogg\win32\VS6\ogg_static.vcproj file. It will prompt to convert and open the project - click "Yes".</li>
<li>On the drop down box on the top of the window, change it from "debug" to "release".</li>
<li>Right-click on the "ogg_static" project and select build. Accept the "save file as" defaults in the box that pops up and just click "save".</li>
<li>ogg build is done. Under win32\VS6\Static_Release, there will be a ogg_static.lib file.</li>
<li>File -> Close Solution</li>
<li>Do File -> Open -> Project and select the vorbis\win32\vorbis_static.dsp file. It will prompt to convert and open the project - click "Yes".</li>
<li>On the drop down box on the top of the window, change it from "debug" to "release".</li>
<li>Right-click on the "vorbis_static" project and select build. Accept the "save file as" defaults in the box that pops up and just click "save".</li>
<li>vorbis build is done - under win32\Vorbis_Static_Release, there will be a vorbis_static.lib file.</li>
<li>File -> Close Solution</li>
<li>Start at step (i), and repeat the steps, choosing "vorbisfile_static.dsp" instead. You will have under vorbis\win32\VorbisFile_Static_Release a vorbisfile.static.lib file when done. </li>
</ol>

'''Note:''' Warnings in the build process are ogg/vorbis problems, and fixing an old release of ogg/vorbis is outside the scope of this document. Also, we are using the VC6 projects instead of the MSVC 2003 ones so that the file names and such will match what Cyan has in their projects. You can build the MSVC 2003 projects if you wish, but you will have to either change the output file names to match the VC6 ones, or change Cyan's projects to use the names the MSVC 2003 projects use. Building the VC6 ones required the less changing of the projects.

<li>Copy the contents of your ogg directory and then vorbis directory into "CWE\MOULOpenSourceClientPlugin\StaticSDKs\Win32\oggvorbis". It is okay to let it overwrite. Once that is done, copy the lib files you created above into "CWE\MOULOpenSourceClientPlugin\StaticSDKs\Win32\oggvorbis\lib" 
Directory structure in the CWE tree will look like this:
<pre>
StaticSDKs
win32
oggvorbis
doc
examples
include
lib
....</pre>
</li>
<li>Install the OpenAL SDK and copy it to "\CWE\MOULOpenSourceClientPlugin\StaticSDKs\Win32\OpenAL 1.1 with EFX SDK" 
Directory structure in the CWE tree will look like this:
<pre>
StaticSDKs
win32
OpenAL 1.1 with EFX SDK
docs
include
libs
....</pre>
</li>
<li>Install the DirectX 9.0c SDK and copy it to "\CWE\MOULOpenSourceClientPlugin\StaticSDKs\Win32\DX9.0c" 
Directory structure in the CWE tree will look like this:
<pre>
StaticSDKs
Win32
DX9.0c
Developer Runtime
Documentation
include
Lib
.....</pre>
</li>
<li>Install "PhysX 2.6.4 SDK Core" (or, if you have or can obtain it, 2.6.0) and copy it to "\CWE\MOULOpenSourceClientPlugin\StaticSDKs\Win32\PhysX". You must use a 2.6.x version, because the mesh cooking format was changed in 2.7.x.

You will copy subdirectories from "C:\Program Files\AGEIA Technologies\AGEIA PhysX SDK\v2.6.4\SDKs" and C:\Program Files (x86)\AGEIA Technologies\AGEIA PhysX SDK\v2.6.4\Bin" 
Directory structure in the CWE tree will look like this:
<pre>
StaticSDKs
Win32
PhysX
Bin
Cooking
Docs
Foundation
Framework
lib
.....</pre>
</li>
<li>Compile and install OpenSSL (see [[Build OpenSSL with MS Visual C++]]). You can choose either static or dynamic linking. '''Note:''' If you link it dynamically, it will cause the Uru client to require the OpenSSL DLLs to be present in the client directory or in the system path. Copy the installed stuff to "\CWE\MOULOpenSourceClientPlugin\StaticSDKs\Win32\OpenSSL" (created by "make install" - you do not want your development tree here). 
Directory structure in the CWE tree will look like this:
<pre>
StaticSDKs
Win32
OpenSSL
bin
include
openssl
lib</pre>
</li>
<li>Open up "Visual Studio .NET 2003 Command Prompt" and change to the "\CWE\MOULOpenSourceClientPlugin\StaticSDKs\XPlatform\jpeg-8c-rgba directory." Copy makefile.vc to makefile.nmake, and jconfig.vc to jconfig.h and then run ''nmake nodebug=1 -f makefile.nmake''. This will build the library in non-debug mode. If you use a debug library, the linker will complain when we link the client executable.</li>
<li>Install zlib and libpng 
'''For Visual Studio 2003:'''
<ol><li>Download ''zlib127.zip'' (or a newer version) from [http://www.zlib.net/ http://www.zlib.net/], extract the ''zlib-1.2.7'' folder it contains and move/rename it to ''MOULOpenSourceClientPlugin/StaticSDKs/XPlatform/zlib''.</li>
<li>Download ''lpng1511.zip'' (or a newer version) from [http://libpng.org/pub/png/libpng.html http://libpng.org/pub/png/libpng.html], extract the ''lpng1511'' folder it contains and move/rename it to ''MOULOpenSourceClientPlugin/StaticSDKs/XPlatform/png''.</li>
<li>Open ''png/projects/visualc71/libpng.sln'' in Visual Studio 2003.</li>
<li>Right-click on the “libpng” project in the ''Solution Explorer'' and choose ''Properties''.</li>
<li>Select configuration “LIB Debug” in the popup menu at the top.</li>
<li>Select ''Configuration Properties'' > ''C/C++'' > ''Code Generation'' on the left.</li>
<li>Change the ''Runtime Library'' line to “Multi-threaded Debug DLL (/MDd)”. (This step avoids a warning in the final Plasma build. As far as I understand, leaving it out is harmless, but better do it to be sure.)</li>
<li>Choose the “LIB Release” configuration and set ''Runtime Library'' to “Multi-threaded DLL (/MD)”.</li>
<li>Repeat steps 4 to 8 for the other two projects “pngtest” and “zlib”.</li>
<li>Select “LIB Debug” from the ''Solution Configurations'' popup menu in the toolbar, then ''Build'' > ''Build Solution''.</li>
<li>Select the “LIB Release” configuration and build the solution.</li>
<li>Make a new folder ''png/lib'' and move ''png/projects/visualc71/Win32_LIB_Debug/libpngd.lib'' as well as ''png/projects/visualc71/Win32_LIB_Release/libpng.lib'' into it.</li>
<li>Make a new folder ''zlib/lib'' and move ''png/projects/visualc71/Win32_LIB_Debug/ZLib/zlibd.lib'' as well as ''png/projects/visualc71/Win32_LIB_Release/ZLib/zlib.lib'' into it.</li></ol>
'''For Visual Studio 2010:''' (if anyone ever makes a “Build with VS 2010” page, that could be moved there)
<ol><li>Download ''zlib127.zip'' (or a newer version) from [http://www.zlib.net/ http://www.zlib.net/], extract the ''zlib-1.2.7'' folder it contains and move/rename it to ''MOULOpenSourceClientPlugin/StaticSDKs/XPlatform/zlib''.</li>
<li>Download ''lpng1511.zip'' (or a newer version) from [http://libpng.org/pub/png/libpng.html http://libpng.org/pub/png/libpng.html], extract the ''lpng1511'' folder it contains and move/rename it to ''MOULOpenSourceClientPlugin/StaticSDKs/XPlatform/png''.</li>
<li>Open ''png/projects/vstudio/zlib.props'' in a text editor (Notepad or Visual Studio will do) and change the ''<ZLibSrcDir>'' element (third line from the bottom) to read
<code><ZLibSrcDir>..\..\..\..\zlib</ZLibSrcDir></code></li>
<li>Open ''png/projects/vstudio/vstudio.sln'' in Visual Studio 2010.</li>
<li>Right-click on the “zlib” project in the ''Solution Explorer'' and choose ''Properties''.</li>
<li>Select configuration “Debug Library” in the popup menu at the top.</li>
<li>Select ''Configuration Properties'' > ''C/C++'' > ''Preprocessor'' on the left.</li>
<li>Insert <code>_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;</code>
into the ''Preprocessor Definitions'' line (so that it reads <code>WIN32;_DEBUG;_WINDOWS;_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE;%(PreprocessorDefinitions)</code> afterwards).</li>
<li>Select ''Configuration Properties'' > ''C/C++'' > ''Code Generation'' on the left.</li>
<li>Change the ''Runtime Library'' line to “Multi-threaded Debug DLL (/MDd)”. (This step avoids a warning in the final Plasma build. As far as I understand, leaving it out is harmless, but better do it to be sure.)</li>
<li>Choose the “Release Library” configuration and repeat step 8 (so that the line reads <code>_CRT_SECURE_NO_WARNINGS;_CRT_NONSTDC_NO_DEPRECATE</code> afterwards).</li>
<li>Set ''Runtime Library'' to “Multi-threaded DLL (/MD)” like in step 10.</li>
<li>Close the ''zlib Property Pages'' dialog.</li>
<li>Repeat the ''Runtime Library'' setting (steps 10 and 12) on projects ''libpng'', ''pngtest'', ''pngvalid''.</li>
<li>Right-click on the “zlib” project and choose ''Add'' > ''Existing Item…''.</li>
<li>Navigate to ''StaticSDKs/XPlatform/zlib'', select all ''*.c'' files there (sort the list by file type to make this easier), and click ''Add''. This should add files ''gzclose.c'', ''gzlib.c'', ''gzread.c'', ''gzwrite.c'' to the project, the rest should have been there already.</li>
<li>Select “Debug Library” from the ''Solution Configurations'' popup menu in the toolbar, then ''Build'' > ''Build Solution''.</li>
<li>Select the “Release Library” configuration and build the solution.</li>
<li>Make new folders ''png/lib'' and ''zlib/lib'' and move and rename the following files into them:
<ul><li>png/projects/vstudio/Debug Library/libpng15.lib → png/lib/libpngd.lib</li>
<li>png/projects/vstudio/Debug Library/zlib.lib → zlib/lib/zlibd.lib</li>
<li>png/projects/vstudio/Release Library/libpng15.lib → png/lib/libpng.lib</li>
<li>png/projects/vstudio/Release Library/zlib.lib → zlib/lib/zlib.lib</li></ul></li></ol>
</li>
<li>Once you have completed all the setup steps, open a "Visual Studio .NET 2003 Command Prompt" again, and change directory to the root of the CWE source. Run "build-allclient-solution.bat" and wait. If all is well, you will have a plClient.exe and UruLauncher.exe, along with the matching PhysX DLLs, in "CWE\MOULOpenSourceClientPlugin\Plasma20\test". Rename plClient.exe to UruExplorer.exe, and copy the executables and DLLs to your "Uru Live" directory. You do not need to copy in the *.pdb. *.map, or sp.dll files for a live external build. Those are only used by the internal builds.</li>
</ol>
 

== Additional notes ==

* This is built as a '''PLASMA_EXTERNAL_RELEASE''', '''BUILD_TYPE_LIVE''' build.
* Only the "Win32|Release" target will build with the changes I loaded to the repository. I did not modify any other build types, so if you wish to build those, you will have to fix them up first.

* Crypto keys are located in "CWE\MOULOpenSourceClientPlugin\Plasma20\Sources\Plasma\NucleusLib\pnNetBase". Edit the *.hpp files with a text editor to replace the Cyan keys with your own server's keys. A future action item is to move the keys to an external INI and add a dialog which will allow the user to select the keys for the server they are connecting to.
'''Important:''' Make sure to run "clean-allclient-solution.bat" and rebuild when you change crypto keys, to make sure they are updated.

* Server hostnames, IP addresses, and ports are located in the following files:

The status URL: 
"CWE\MOULOpenSourceClientPlugin/Plasma20/Sources/Plasma/Apps/plClient/winmain.cpp"
"CWE\MOULOpenSourceClientPlugin/Plasma20/Sources/Plasma/Apps/plUruLauncher/Main.cpp"

The auth/gatekeeper address 
"CWE\MOULOpenSourceClientPlugin/Plasma20/Sources/Plasma/NucleusLib/pnNetBase/Private/pnNbSrvs.cpp"

The default client port 
"CWE\MOULOpenSourceClientPlugin/Plasma20/Sources/Plasma/NucleusLib/pnNetBase/pnNbConstant.h"

<big>'''IMPORTANT:'''</big> You '''*must*''' make sure your client is using the same versions of the PhysX DLLs that you built with. They
are not compatible from version to version.

[[Category:Cyan_Worlds]]

CyanWorlds.com Engine

2020-10-24T01:32:12Z

Rarified: Update repository description to include migration to Git.

<div style="float: right; padding: 10px;">http://assets.openuru.org/logos/gpl/gplv3-127x51.png</div>
== CyanWorlds.Com Engine (CWE) Open Source Project ==

The wait is over!

=== Introduction ===
Cyan Worlds, Inc. and OpenUru.org jointly announce open source delivery of the CyanWorlds.com Engine client and 3ds Max plugin, aka Plasma, the engine used to power Myst Online: Uru Live.

==== Cyan Worlds Announcement ====
The following message was posted on the MystOnline.com forums on April 6th, 2011:
<blockquote class="bluebox">An Open Letter on Open Source <big>☺</big>
<hr> 

The progress on our open source roadmap has been slow but has never stopped. And now what will look like a large step is really the result of numerous people, both inside and outside of Cyan Worlds, slowly cutting the rock into shape...
 

Today we are announcing that the sources for the MOULA client engine and development tools (CyanWorlds.com Engine) will be made available as open source. At the same time, MOSS which is a MOULA server replacement (written by a'moaca' and cjkelly) will also be released. Both open source projects will be hosted on OpenUru.org.
 

The goal of the open source CyanWorlds.com Engine and the MOSS server is to provide a "playground" where new writers can learn their craft, and new maintainers can inspect it, and new cartographers can map it. The Cyan Worlds MOULA servers will continue to provide a (relatively) safe environment for the D'ni faithful to mingle and share.
 

The path forward from here seems fairly obvious and very exciting - with amazing parallels to the D'ni universe itself. As new writers arise with new books, the books are tested and documented - and books that are approved by some new kind of maintainers guild will (hopefully) find their way to the MOULA server where the public can enjoy new worlds once again.
 

These are exciting times, but not without risk. The tools and skills are new and need to be sharpened. There will be disagreements and strongly expressed opinions. And there will be decisions and mistakes. But keep in mind that the big picture is a lot like rebuilding a long dead civilization - and the forest of common goals far outnumber the few trees of differences. Let's keep it civil. <big>☺</big>
 

There have been numerous people cutting on the rock, and they've kept this project alive. We sincerely thank all of them for the wonderful help. Specifically there are a few people who went above and beyond - JWPlatt, a'moaca', Mac_Fife, cjkelly, rarified and Chogon.
 

Thanks again for the continued support!
 

Shorah, 
Rand</blockquote>

==== OpenUru.org Announcement ====
OpenUru.org introduces the CyanWorlds.Com Engine, Cyan Worlds' Plasma game engine used to power Myst Online: Uru Live. The OpenUru.org team is thrilled that the CyanWorlds.com Engine has been released by Cyan Worlds as open source. We are honored that Cyan Worlds has given OpenUru.org the opportunity to prepare and release it to the Uru community and the world. The initial release of the CyanWorlds.Com Engine includes Cyan Worlds' client and 3ds Max plugin.

OpenUru.org is especially pleased to simultaneously announce a'moaca' and cjkelly1's Myst Online Server Software (MOSS), a Myst Online: Uru Live Again (MOULa) server replacement. MOSS was largely derived from a'moaca's work on her client protocol Wireshark plugin, a project also hosted on OpenUru.org. Cyan Worlds cannot release their server code until more is done to clear it for open source, so a'moaca' and cjkelly1's completion of their open source server couldn't have been more perfectly timed.

OpenUru.org is prepared with tools to support new development of the CyanWorlds.com Engine with MOSS. We welcome all developers, issue reporters and users to contribute to the effort. Contributors can use our Foundry with Atlassian tools such as JIRA, Fisheye and Crucible to manage development projects and Jenkins (previously known as Hudson) for Continuous Integration to produce automated builds.

The OpenUru.org Foundry is initially providing executable builds with the sources for both the MOSS server and MOULa client, thanks to the stellar development and preparatory work by a'moaca' and cjkelly1, and Foundry development from rarified.

What is included in this source release from Cyan Worlds:

* MOULa client engine source
* MOULa 3ds Max plugin source
* MOULa supporting Python and SDL files

What is not in this source release from Cyan Worlds:

* MOULa server code
* Certain parts of the internal client that deal with customer service support

Further details can be found at http://wiki.OpenUru.org/index.php?title=CyanWorlds.com_Engine.

Open Uru is an inclusive concept of a community of creative talent and hard work coming together to make new worlds, new stories, and new content - now able to openly use and develop the CyanWorlds.com Engine to empower it. The OpenUru.org team presently consists of JWPlatt, Mac_Fife, rarified, a'moaca' and cjkelly1 and Chogon. It is hoped that others will join to lead these efforts in the infinite possibilities of Open Uru.

Resources:

* Website: http://OpenUru.org
* Wiki: http://wiki.OpenUru.org
* Foundry: http://foundry.OpenUru.org
* Forums: http://forums.OpenUru.org

Social:

* Facebook: http://www.facebook.com/OpenUru.org
* Twitter: http://twitter.com/openuru_org
* Discord hood - idle talk: https://discord.gg/tVknpHQ
* Discord dev - developers: https://discord.gg/jyp23GF
* Discord play - gameplay discussion: https://discord.gg/vZW5rZQ
* Discord support - general help: https://discord.gg/SgX22BR

=== What It Is ===
CyanWorlds.Com Engine is the client, server and tools used to develop and operate the Myst Online: Uru Live MMO. The server code needs more work before Cyan Worlds can clear it for open source. However, the client and 3ds Max plugin are now available in open source.

=== How To Get It ===
CyanWorlds.Com Engine is available on OpenUru.org's Foundry, hosted on a Git code repository. There was much discussion on the Myst Online forums about the strengths of various repositories after Cyan Worlds' initial open source announcement in 2008. We listened. Mercurial was selected due to the needs of a distributed developer community. Since that time Mercurial has diminished in popularity, and Git has emerged as the dominant SCM for Open Source projects. All OpenUru.org Mercurial repositories were migrated to Git during 2020.

Any developer requiring "commit" access to our repositories needs to [[Foundry_Accounts|register an account]] on the Foundry at https://Foundry.OpenUru.org/jira. Guest access to pull from the repository does not require an account.

Developers with an account will be given access to pull the CyanWorlds.Com Engine repository as quickly as possible. Once the developer traffic has subsided, the repository will be opened to the public and the curious.

'''Steps'''
<ol>
<li> [[Foundry_Accounts|Register]] for a Foundry account at https://Foundry.OpenUru.org/jira (only necessary if you expect to need "commit" access to the repository).</li>

<li> Pull the <abbr title="CyanWorlds.com Engine">CWE-ou</abbr> repository from the address given below. </li>
</ol>

'''View account queue:''' http://forums.OpenUru.org/viewtopic.php?f=91&t=507 (Note: The account queue is longer required)

'''Repository address:''' https://foundry.OpenUru.org/gitblit/summary/?r=CWE-ou.git

As mentioned in step 1, you only need to register for an account if you wish to obtain commit access. To just pull the source, anonymous access works, or use a username of ''guest'', and a password of ''guest''.

=== Development ===
Some developers will be invited to join the team in management and development positions for the CyanWorlds.Com Engine project. But generally, anyone who demonstrates the skills and becomes a positive force in the project may contribute to development.

CyanWorlds.Com Engine "version 1.0" will consist only of a buildable client. The plugin sources will need further work to make it buildable for 3ds Max 7. The initial release from the repositories has had just enough work done to substitute proprietary and third party libraries to allow it to build successfully. There is further work required to fully integrate the new libraries and to replace functionality that was removed in preparing the sources for release. We envisage a road map of essentially three phases: Phase 1 would aim to duplicate the functionality of the current MOUL binaries, Phase 2 would start to introduce fixes for known issues or, for example, upgrade the plugin for the current release of 3ds Max. After that, the fun begins with new features and full steam ahead to keep on chugging down that open source track. While we would ''prefer'' that change submissions follow this roadmap, nothing is set in stone, and changes with clear merit will always be welcome.

Once things get rolling, we'll be looking for people to fill or help with the following positions:

* Project lead (integration of job flow, patches, release schedules)
* Documentation lead (create and integrate cross-platform documentation for JIRA, web, Wiki, PDF, IDE)
* Technology lead (site integration, resource integration, security, builds)
* Development lead (prioritization of issues, issue assignments, tools, set up code review)
* Web community lead (development of web presence and content to introduce, educate and deliver open source projects

=== Documentation ===
What documentation? The code documents itself! Right? Actually, there was an apparent early effort to maintain directives used for automated Doxygen documentation from code. Their use fell off as time went on. Introduction of integrated documentation is considered crucial to the successful development of the CyanWorlds.Com Engine. Therefore, Doxygen directives will be accepted into the main trunk from the start. We want to build integrated documentation originating from the source code for use beginning with Fisheye (our repo browser), HTML, PDF, and the Visual Studio IDE.

=== Everyone ===
Everyone will be able to download and watch progress of the CyanWorlds.Com Engine project and enjoy the benefits of exploring new worlds.

=== The Team ===
The CyanWorlds.com Engine Project was brought to you by Cyan Worlds' Rand Miller, Tony Fryman, Mark DeForest and the collective talents of everyone at Cyan Worlds who ever worked on Uru Live over many years. The original release team at OpenUru.org who are helping to make the open source CyanWorlds.com Engine project possible are JWPlatt, Mac_Fife, rarified, a'moaca', and cjkelly1.

=== Building The Client ===
In the article "[[Build the client with MSVC 2003]]", cjkelly1 describes how to build a working client from the <abbr title="CyanWorlds.com Engine">CWE</abbr> sources. Note that this build uses sources and makefiles that have been modified to substitute some of the libraries that could not be distributed with the original sources. 
You can also [[Build the client with MSVC 2010 Express]].
 

=== Building The Tools ===
For compiling the plPythonPack and plFileSecure projects, there is a tutorial by Mystler in the article "[[Building the plPythonPack and plFileSecure projects]]". It is based on cjkelly1's tutorial "[[Build the client with MSVC 2003]]". 
The "[[Build the client with MSVC 2010 Express]]" article also contains instructions for building tools.

== See Also ==

{{:CWE/See Also}}

[[Category:Cyan_Worlds]]

CyanWorlds.com Engine

2020-05-06T16:40:35Z

Rarified: Update location of CWE-ou repostitory for GIT

<div style="float: right; padding: 10px;">http://assets.openuru.org/logos/gpl/gplv3-127x51.png</div>
== CyanWorlds.Com Engine (CWE) Open Source Project ==

The wait is over!

=== Introduction ===
Cyan Worlds, Inc. and OpenUru.org jointly announce open source delivery of the CyanWorlds.com Engine client and 3ds Max plugin, aka Plasma, the engine used to power Myst Online: Uru Live.

==== Cyan Worlds Announcement ====
The following message was posted on the MystOnline.com forums on April 6th, 2011:
<blockquote class="bluebox">An Open Letter on Open Source <big>☺</big>
<hr> 

The progress on our open source roadmap has been slow but has never stopped. And now what will look like a large step is really the result of numerous people, both inside and outside of Cyan Worlds, slowly cutting the rock into shape...
 

Today we are announcing that the sources for the MOULA client engine and development tools (CyanWorlds.com Engine) will be made available as open source. At the same time, MOSS which is a MOULA server replacement (written by a'moaca' and cjkelly) will also be released. Both open source projects will be hosted on OpenUru.org.
 

The goal of the open source CyanWorlds.com Engine and the MOSS server is to provide a "playground" where new writers can learn their craft, and new maintainers can inspect it, and new cartographers can map it. The Cyan Worlds MOULA servers will continue to provide a (relatively) safe environment for the D'ni faithful to mingle and share.
 

The path forward from here seems fairly obvious and very exciting - with amazing parallels to the D'ni universe itself. As new writers arise with new books, the books are tested and documented - and books that are approved by some new kind of maintainers guild will (hopefully) find their way to the MOULA server where the public can enjoy new worlds once again.
 

These are exciting times, but not without risk. The tools and skills are new and need to be sharpened. There will be disagreements and strongly expressed opinions. And there will be decisions and mistakes. But keep in mind that the big picture is a lot like rebuilding a long dead civilization - and the forest of common goals far outnumber the few trees of differences. Let's keep it civil. <big>☺</big>
 

There have been numerous people cutting on the rock, and they've kept this project alive. We sincerely thank all of them for the wonderful help. Specifically there are a few people who went above and beyond - JWPlatt, a'moaca', Mac_Fife, cjkelly, rarified and Chogon.
 

Thanks again for the continued support!
 

Shorah, 
Rand</blockquote>

==== OpenUru.org Announcement ====
OpenUru.org introduces the CyanWorlds.Com Engine, Cyan Worlds' Plasma game engine used to power Myst Online: Uru Live. The OpenUru.org team is thrilled that the CyanWorlds.com Engine has been released by Cyan Worlds as open source. We are honored that Cyan Worlds has given OpenUru.org the opportunity to prepare and release it to the Uru community and the world. The initial release of the CyanWorlds.Com Engine includes Cyan Worlds' client and 3ds Max plugin.

OpenUru.org is especially pleased to simultaneously announce a'moaca' and cjkelly1's Myst Online Server Software (MOSS), a Myst Online: Uru Live Again (MOULa) server replacement. MOSS was largely derived from a'moaca's work on her client protocol Wireshark plugin, a project also hosted on OpenUru.org. Cyan Worlds cannot release their server code until more is done to clear it for open source, so a'moaca' and cjkelly1's completion of their open source server couldn't have been more perfectly timed.

OpenUru.org is prepared with tools to support new development of the CyanWorlds.com Engine with MOSS. We welcome all developers, issue reporters and users to contribute to the effort. Contributors can use our Foundry with Atlassian tools such as JIRA, Fisheye and Crucible to manage development projects and Jenkins (previously known as Hudson) for Continuous Integration to produce automated builds.

The OpenUru.org Foundry is initially providing executable builds with the sources for both the MOSS server and MOULa client, thanks to the stellar development and preparatory work by a'moaca' and cjkelly1, and Foundry development from rarified.

What is included in this source release from Cyan Worlds:

* MOULa client engine source
* MOULa 3ds Max plugin source
* MOULa supporting Python and SDL files

What is not in this source release from Cyan Worlds:

* MOULa server code
* Certain parts of the internal client that deal with customer service support

Further details can be found at http://wiki.OpenUru.org/index.php?title=CyanWorlds.com_Engine.

Open Uru is an inclusive concept of a community of creative talent and hard work coming together to make new worlds, new stories, and new content - now able to openly use and develop the CyanWorlds.com Engine to empower it. The OpenUru.org team presently consists of JWPlatt, Mac_Fife, rarified, a'moaca' and cjkelly1 and Chogon. It is hoped that others will join to lead these efforts in the infinite possibilities of Open Uru.

Resources:

* Website: http://OpenUru.org
* Wiki: http://wiki.OpenUru.org
* Foundry: http://foundry.OpenUru.org
* Forums: http://forums.OpenUru.org

Social:

* Facebook: http://www.facebook.com/OpenUru.org
* Twitter: http://twitter.com/openuru_org
* Discord hood - idle talk: https://discord.gg/tVknpHQ
* Discord dev - developers: https://discord.gg/jyp23GF
* Discord play - gameplay discussion: https://discord.gg/vZW5rZQ
* Discord support - general help: https://discord.gg/SgX22BR

=== What It Is ===
CyanWorlds.Com Engine is the client, server and tools used to develop and operate the Myst Online: Uru Live MMO. The server code needs more work before Cyan Worlds can clear it for open source. However, the client and 3ds Max plugin are now available in open source.

=== How To Get It ===
CyanWorlds.Com Engine is available on OpenUru.org's Foundry, hosted on a Mercurial code repository. There was much discussion on the Myst Online forums about the strengths of various repositories after Cyan Worlds' initial open source announcement in 2008. We listened. Mercurial was selected due to the needs of a distributed developer community.

Any developer requiring "commit" access to our repositories needs to [[Foundry_Accounts|register an account]] on the Foundry at https://Foundry.OpenUru.org/jira. Guest access to pull from the repository does not require an account.

Developers with an account will be given access to pull the CyanWorlds.Com Engine repository as quickly as possible. Once the developer traffic has subsided, the repository will be opened to the public and the curious.

'''Steps'''
<ol>
<li> [[Foundry_Accounts|Register]] for a Foundry account at https://Foundry.OpenUru.org/jira (only necessary if you expect to need "commit" access to the repository).</li>

<li> Pull the <abbr title="CyanWorlds.com Engine">CWE-ou</abbr> repository from the address given below. </li>
</ol>

'''View account queue:''' http://forums.OpenUru.org/viewtopic.php?f=91&t=507 (Note: The account queue is longer required)

'''Repository address:''' https://foundry.OpenUru.org/gitblit/summary/?r=CWE-ou.git

As mentioned in step 1, you only need to register for an account if you wish to obtain commit access. To just pull the source, anonymous access works, or use a username of ''guest'', and a password of ''guest''.

=== Development ===
Some developers will be invited to join the team in management and development positions for the CyanWorlds.Com Engine project. But generally, anyone who demonstrates the skills and becomes a positive force in the project may contribute to development.

CyanWorlds.Com Engine "version 1.0" will consist only of a buildable client. The plugin sources will need further work to make it buildable for 3ds Max 7. The initial release from the repositories has had just enough work done to substitute proprietary and third party libraries to allow it to build successfully. There is further work required to fully integrate the new libraries and to replace functionality that was removed in preparing the sources for release. We envisage a road map of essentially three phases: Phase 1 would aim to duplicate the functionality of the current MOUL binaries, Phase 2 would start to introduce fixes for known issues or, for example, upgrade the plugin for the current release of 3ds Max. After that, the fun begins with new features and full steam ahead to keep on chugging down that open source track. While we would ''prefer'' that change submissions follow this roadmap, nothing is set in stone, and changes with clear merit will always be welcome.

Once things get rolling, we'll be looking for people to fill or help with the following positions:

* Project lead (integration of job flow, patches, release schedules)
* Documentation lead (create and integrate cross-platform documentation for JIRA, web, Wiki, PDF, IDE)
* Technology lead (site integration, resource integration, security, builds)
* Development lead (prioritization of issues, issue assignments, tools, set up code review)
* Web community lead (development of web presence and content to introduce, educate and deliver open source projects

=== Documentation ===
What documentation? The code documents itself! Right? Actually, there was an apparent early effort to maintain directives used for automated Doxygen documentation from code. Their use fell off as time went on. Introduction of integrated documentation is considered crucial to the successful development of the CyanWorlds.Com Engine. Therefore, Doxygen directives will be accepted into the main trunk from the start. We want to build integrated documentation originating from the source code for use beginning with Fisheye (our repo browser), HTML, PDF, and the Visual Studio IDE.

=== Everyone ===
Everyone will be able to download and watch progress of the CyanWorlds.Com Engine project and enjoy the benefits of exploring new worlds.

=== The Team ===
The CyanWorlds.com Engine Project was brought to you by Cyan Worlds' Rand Miller, Tony Fryman, Mark DeForest and the collective talents of everyone at Cyan Worlds who ever worked on Uru Live over many years. The original release team at OpenUru.org who are helping to make the open source CyanWorlds.com Engine project possible are JWPlatt, Mac_Fife, rarified, a'moaca', and cjkelly1.

=== Building The Client ===
In the article "[[Build the client with MSVC 2003]]", cjkelly1 describes how to build a working client from the <abbr title="CyanWorlds.com Engine">CWE</abbr> sources. Note that this build uses sources and makefiles that have been modified to substitute some of the libraries that could not be distributed with the original sources. 
You can also [[Build the client with MSVC 2010 Express]].
 

=== Building The Tools ===
For compiling the plPythonPack and plFileSecure projects, there is a tutorial by Mystler in the article "[[Building the plPythonPack and plFileSecure projects]]". It is based on cjkelly1's tutorial "[[Build the client with MSVC 2003]]". 
The "[[Build the client with MSVC 2010 Express]]" article also contains instructions for building tools.

== See Also ==

{{:CWE/See Also}}

[[Category:Cyan_Worlds]]

Explorers Memorial

2019-10-20T21:48:33Z

Rarified:

The Explorers Memorial is a monument of four rings with a scrolling list of names, located just outside of the Kahlo Pub on Ae'gura Island in the game, ''Myst Online: Uru Live'' (MOUL). Below is a list of the names that currently appear on the memorial, both real people and fictional Non-Player Characters (NPCs). For more information on the real community members who have been lost to us, please visit the '''[[In Memoriam]]''' page.

Richard "ShadowCats" Bader ... Jeannie "jmb30321" Barcus ... Janet "Pehpsee" Burress ... CAGrayWolf ... James "Aquila" Carpenter ... Virginia "Terra" Cinova ... Al "Wamduskasapa" Edwards ... Willow "Wheely" Engberg'''*''' ... Cindy Farrar ... Gandhar ... Kees "Grassie73" Grashoff ... Ron Hayter ... Jahuti ... Maureen "Mo'zie" Jannot ... JDrake ... Katzi ... William “oldmanjob” Maier ... Len "Flyboy" Mumbower ... Myst'Aken ... Gorma Louise "GLO" O'Conner ... Perlenstern ... Mark “Zardoz” Plummer ... Ramsine ... Jim "Dust'ei" Rhodes ... Josef Riedl ... Sil-Oh-Wet ... Rosette Taylor'''*''' ... Don "Sailor86" Billow ... David Ogden Stiers ... Terri "Tai'lahr" Richardson ...

<nowiki>*</nowiki> Non-Player (fictional) Characters who died as part of a story line in the cavern.

== Background ==

Prior to the installation of this memorial, community members had created memorial webpages/sites, memorials in other worlds (There, Second Life), and even their own Uru ages to honor fellow Myst/Uru community members who had died. Additionally, they had requested that Cyan create a memorial in Uru <ref>[http://www.mystonline.com/forums/viewtopic.php?f=4&t=383 MOUL Forum post by Eleri: Memorial Plaque]</ref><ref>[http://mystonline.com/forums/viewtopic.php?p=85969#p85969 MOUL forum post by Sixdd requesting a memorial]</ref><ref>[http://www.mystonline.com/forums/viewtopic.php?f=4&t=5278 MOUL forum post by Marck: A graveyard]</ref><ref>[http://www.mystonline.com/forums/viewtopic.php?f=1&t=8483 MOUL forum thread by Vormaen: An idea for those who have passed.]</</ref><ref>[http://www.mystonline.com/forums/viewtopic.php?f=4&t=8957 MOUL forum post by Simon_Bitdiddle: DRC ResEng Memorial?]</ref> and Cyan indicated as early as June 2006 that “something along these lines” was already planned.<ref>[http://www.mystonline.com/forums/viewtopic.php?p=7655#p7655 MOUL forum post by RAWA regarding plans for a memorial]</ref>

In early 2006, during the D’mala era, the <abbr title="Non-Player Character">NPC</abbr> "Wheely" was introduced as being Willow Engberg, daughter of D'ni Restoration Council (DRC) member Michael Engberg. She spent quite a bit of time with the explorers in the cavern so that by May 2007, she was well known among the players and many were fond of her. On May 18, 2007, the NPC “Rosette” was introduced as a close friend of Wheely’s from Portland, Oregon.<ref>[http://www.mystonline.com/forums/viewtopic.php?p=168841#p168841 Marck’s chatlog of meeting Rosette] </ref> The MOUL episode, “Scars” began May 19, 2007 with a [http://drcarch.thecitadel.nl/communication/ki-mail/safety-alert/ “Safety Alert”]([https://web.archive.org/web/20150826141933/http://drcarch.thecitadel.nl/communication/ki-mail/safety-alert/ WM]) KI-mail from the DRC warning explorers to be cautious in the Kahlo Pub area due to new cracks being discovered there. The next day, Wheely and Rosette were in the cavern doing marker missions. Other explorers, concerned for their safety, tried to convince the girls to stay out of the city, but failing that, joined them with the intention of keeping a watchful eye and steer them away from the dangerous area.<ref>[http://www.mystonline.com/forums/viewtopic.php?f=1&t=10333 MOUL forum thread by Thend: Wheely & Rosette -05/20/07-Council Hood,Ae'gura,Kadish,G]([https://web.archive.org/web/20150826144540/http://www.mystonline.com/forums/viewtopic.php?f=1&t=10333 WM])</ref> But the girls managed to slip away alone to the city and shortly thereafter, they disappeared from everyone's KI. DRC members and explorers began searching for them while other explorers held vigils and waited both in the cavern and on the forums for more news. Bahros were seen in the city and low rumbles were heard coming from the area of the Kahlo Pub where it was discovered the ceiling had collapsed. Explorers soon learned that Rosette had died in the cave in and Wheely was trapped there.<ref>[http://drcarch.thecitadel.nl/communication/ki-mail/city-reopened/ 05/21/2007 DRC KI-mail, "City Reopened"]</ref> As the DRC attempted to rescue her all the next day, explorers anxiously listened to relayers in the cavern or watched the forums for any news.<ref>[http://www.mystonline.com/forums/viewtopic.php?f=2&t=10010 MOUL forum thread: "Wheely is missing?-Update; Dreadful News"] ([https://web.archive.org/web/20150823201028/http://www.mystonline.com/forums/viewtopic.php?f=2&t=10010 WM])</ref> On May 22nd, they were stunned to learn of her death just before rescuers were able to reach her.<ref>[http://drcarch.thecitadel.nl/communication/ki-mail/tragedy/ 05/22/2007 DRC KI-mail "Tragedy in the Cavern"]([https://web.archive.org/web/20150826142040/http://drcarch.thecitadel.nl/communication/ki-mail/tragedy/ WM])</ref>

== History ==

On June 26, 2007, DRC member Marie Sutherland unveiled the memorial outside of the Kahlo Pub saying, “It seems I should say something for this occasion, but I don't have the words. We have spent the last month trying to decide how to memorialize the explorers that we've lost. Nothing I can say will do justice to their memories, so I won't even try. But this will be a small token.”<ref>[http://forums.guildofgreeters.com/index.php?showtopic=13124 Guild of Greeters’ forum: Marie Sutherland chatlog]</ref>

The initial names on the memorial at that time were Janet "Pehpsi" Burress, James "Aquila" Carpenter, "JDrake", Willow "Wheely" Engberg, Phil "phend" Henderson, Maureen "Mo'zie" Jannot, "Rasmine", Jim "Dust'ei" Rhodes, and Rosette Taylor. (“Rasmine” was actually “Ramsine,” a member of the German community which informed Cyan of the error and it was corrected.<ref>[http://www.uru-reallife.com/viewtopic.php?p=56115#p56115 Uru Reallife forum post about Ramsine] ([https://web.archive.org/web/20150826112508/http://www.uru-reallife.com/viewtopic.php?p=56115 WM])</ref> Also, Janet "Pehpsi" Burress would be corrected to Janet "Pehpsee" Burress.<ref>[http://forums.guildofgreeters.com/index.php?showtopic=14881&st=0&p=231733&#entry231733 December 17, 2008 post by Jarelav to Guild of Greeters forum thread, "Birthday Remembrance For Pepsi, 05 December"] [https://web.archive.org/web/20170109235841/http://forums.guildofgreeters.com/index.php?showtopic=14881&st=0&p=231733& (WM)]</ref>)

Following the unveiling, the DRC sent a KI-mail to all explorers, [http://drcarch.thecitadel.nl/communication/ki-mail/wheely-memorial/ “Wheely Memorial”]([https://web.archive.org/web/20150826141714/http://drcarch.thecitadel.nl/communication/ki-mail/wheely-memorial/ WM]) announcing the memorial and requesting submissions of the names of other explorers who had passed away along with a description of how each contributed to the restoration.

The inclusion of NPC Phil "phend" Henderson on the memorial when it was initially installed was part of a story line in which the DRC believed he had died in 2003 when a wall in the cavern collapsed. Although his body was never found, he was presumed dead. However, phend re-appeared in the cavern on August 3rd, 2007 <ref>[http://www.guildofgreeters.com/index.php?option=com_content&task=view&id=77&Itemid=38#top Guild of Greeters page: A Guide to Characters]</ref> and his name was removed from the memorial.<ref>[http://www.mystonline.com/forums/viewtopic.php?p=198254#p198254 MOUL forum post by ziggy2765]([https://web.archive.org/web/20150827024548/http://www.mystonline.com/forums/viewtopic.php?p=198254 WM])</ref> For some unknown reason, Phil's name was re-added to the memorial when the cavern re-opened in 2010,<ref>[http://www.mystonline.com/forums/viewtopic.php?p=323335#p323335 MOUL forum post by CrisGer with KI shot of memorial] ([https://web.archive.org/web/20150831131821/http://www.mystonline.com/forums/viewtopic.php?p=334616 WM]), [http://www.mystonline.com/forums/viewtopic.php?p=334616#p334616 MOUL forum posts mentioning Phil's name on the memorial] ([https://web.archive.org/web/20150831131856/http://www.mystonline.com/forums/viewtopic.php?p=323335 WM])</ref> but was eventually removed again.

Over the years, new names have been added. Three community members (CAGrayWolf, Jahuti, and Gandhar) died while the cavern was closed between April 2008 and January 2010 and their names were added when the cavern re-opened in 2010.

On February 20, 2010, Ghaelen and the Guild of Healers held a "Memorial and Welcome Home" event at the Kahlo Pub.<ref>[http://www.mystonline.com/forums/viewtopic.php?p=323335#p323335 Saturday Memorial and Welcome Home at Kahlo Pub] ([https://web.archive.org/web/20150831131821/http://www.mystonline.com/forums/viewtopic.php?p=334616 WM])</ref> and on February 4, 2012, held a "Memorial Vigil" during the second anniversary celebrations of the cavern re-opening.<ref>[http://www.mystonline.com/forums/viewtopic.php?p=381546#p381546 2nd Anniversary Cavern Re-(re-)Opening Celebration], ([https://web.archive.org/web/20150831133102/http://www.mystonline.com/forums/viewtopic.php?p=381546 WM])</ref>

A post made to the Uru Obsession forum on the day of the unveiling included a list of the names, but reported the name Maureen "Mo'zie" Jannot only as "Mo'zie" and the list was copied to other forums, including the Guild of Greeters<ref>[http://forums.guildofgreeters.com/index.php?showtopic=13124 Guild of Greeters’ forum post, listing names]</ref> and MOUL<ref>[http://www.mystonline.com/forums/viewtopic.php?p=179703#p179703 Jun 26, 2007 MOUL post, listing names]</ref>. Unfortunately, that list was used as a reference when the memorial was reactivated just before the cavern reopened in 2010. The error was discovered in the course of research for this project, <abbr title="Richard A. Watson">RAWA</abbr> was notified and the name was corrected on September 1, 2015.

The name, "[[Deirdre Karris]]" was added to the memorial on October 9th and removed on October 30, 2015.

Kees "Grassie73" Grashoff was added to the memorial in January 2016.

In January 2017, it was discovered that sometime shortly after the June 2007 unveiling, Janet "Pehpsi" Burress had been changed to Janet "Pehpsee" Burress. It is unknown exactly when or why, but theorized that it had been brought to Cyan's attention that the latter spelling was the one Janet had used for her cavern avatar. And, because the list of names assembled on the day of the unveiling was the one used as a reference, the former spelling was applied when the memorial was reactivated just before the cavern reopened in 2010. This error was corrected on January 9, 2017.

Gorma Louise "GLO" O'Conner and Al "Wamduskasapa" Edwards were added on February 22, 2017. Don "Sailor86" Billow was added in February 2018. David Ogden Stiers was added on 06 March 2018.

== Submissions ==

Requests for adding names to the memorial can be submitted to Cyan, using the format: <firstName> "<avatarName/nickName>" <lastName>.<ref>[http://www.mystonline.com/forums/viewtopic.php?p=419000#p419000 MOUL forum post by RAWA]</ref> Due diligence will be done to verify the person and their passing, so providing as much information as possible (i.e., proof) can expedite the process.

<div class="user-block">'''''Caution'''''<hr>Anyone considering submitting a name not directly tied to an actual death should also consider the repercussions. The memorial is considered sacred by many community members, especially those who knew someone on it. Many of them do not even like that the names of the NPCs Wheely & Rosette are included and would likely be offended by the inclusion of a fake name or one linked to a falsely reported death.</div>

== List in Code ==
For the convenience of shard operators, below is the names list as of 23 Feb 2018 with coding in place to update it directly in the database.
<div class="user-block">'''SQL code for MOSS servers'''<ref>Coding provided by Christian Walthers.</ref><hr>UPDATE textnote SET value = E'Richard "ShadowCats" Bader\nJeannie "jmb30321" Barcus\nJanet "Pehpsee" Burress\nCAGrayWolf\nJames "Aquila" Carpenter\nVirginia "Terra" Cinova\nAl "Wamduskasapa" Edwards\nWillow "Wheely" Engberg\nCindy Farrar\nGandhar\nKees "Grassie73" Grashoff\nRon Hayter\nJahuti\nMaureen "Mo\'zie" Jannot\nJDrake\nKatzi\nWilliam "oldmanjob" Maier\nLen "Flyboy" Mumbower\nMyst\'Aken\nGorma Louise "GLO" O'Conner\nPerlenstern\nMark "Zardoz" Plummer\nRamsine\nJim "Dust\'ei" Rhodes\nJosef Riedl\nSil-Oh-Wet\nRosette Taylor\nDon "Sailor86" Billow\nDavid Ogden Stiers\nTerri "Tai'lahr" Richardson\n' WHERE title = 'MemorialImager';</div>

== Sources ==
[[Category:Explorers_Memorial]]

Minkata Shard: Contributions under Test

2017-04-21T16:54:12Z

Rarified:

This is a list of changes currently accumulating on the Minkata shard for later pick-up into MOULa by Cyan, and how to test them.

== Update 2017-04-21 - Minkata.120 ==

=== Improvement on password hash method standardization ===

[https://bitbucket.org/OpenUru_org/cwe-ou/pull-requests/42 CWE PR #42] by Chogon

Replace PR#40 with a multiple pass password validation attempting all known hashes in sequence until one succeeds or list of hashes is exhausted. This in response to clients being used on alternate servers (Dirtsand) having different hashing techniques for passwords.

== Update 2017-03-25 – Minkata.100 ==

=== Make all account types use the same password hash ===

[https://bitbucket.org/OpenUru_org/cwe-ou/pull-requests/40/make-all-account-types-use-the-same CWE PR #40] by Mac_Fife

Precursor to restoring account creation. Remove conditional on email domain for password hashing. This is only a client modification needed to interface to new code being worked on to reenable Account Creation on MOULa. Verify that you can still log in.

=== Don’t crash the launcher when getting the server status message fails ===

[https://bitbucket.org/OpenUru_org/cwe-ou/pull-requests/38/dont-crash-the-launcher-when-the-http CWE PR #38] by CWalther

This fixes a crash of the launcher after it has already successfully started the game. Verify that you are not getting any “UruLauncher has stopped working” messages before or after logging in.

=== Repair Descent Age ===

[http://forums.openuru.org/viewtopic.php?p=8380#p8380 Minkata bug reports] by rarified

Fixed the database corruption preventing an Avatar from successfully linking into Descent, particularly affected new Avatars. Verify that linking to Descent from Relto or Ae'gura works without getting stuck on a black screen.

== Update 2015-12-14 – Minkata.82 … Update 2015-12-19 – Minkata.88 ==

=== Fix KI chat scrolling issues ===

[https://bitbucket.org/OpenUru_org/cwe-ou/pull-requests/26/add-functions-to-fix-ki-chat-scrolling CWE PR #26], [https://bitbucket.org/OpenUru_org/moulscript-ou/pull-requests/19/fix-ki-chat-scrolling-issue-when-scrolled MOULSCRIPT PR #19] ([https://github.com/H-uru/moul-scripts/pull/40 H-uru PR #40]) by Lyrositor

This fixes a common gripe with KI chat, which has a tendency to scroll down when someone else sends a chat message, even if you have scrolled up. Verify that it now scrolls down only when you are already looking at the bottom, and when scrolled up, flashes the scroll-down arrow instead.

=== Fix stuck-in-intro-cave bug ===

[https://bitbucket.org/OpenUru_org/cwe-ou/pull-requests/37/fix-stuck-in-intro-cave-bug CWE PR #37] by CWalther

Verify that a new avatar is no longer stuck in the intro cave with the rotating wall before arriving on Relto. Instead the cave should just briefly fade in and out.

=== Don't crash when the HTTP request for getting the server status message fails ===

[https://bitbucket.org/OpenUru_org/cwe-ou/pull-requests/31/dont-crash-when-the-http-request-for CWE PR #31] by CWalther

This fixes the crash that keeps Windows 7 (or later) users out of MOULa when support.cyanworlds.com is down.

=== Fix for forgotten logins when removable media attached ===

[https://bitbucket.org/OpenUru_org/cwe-ou/pull-requests/33/fix-for-forgotten-logins-when-removable CWE PR #33] by Mac_Fife

Verify that your saved login/password no longer disappears when you have USB drives or CDs/DVDs inserted.

=== Shadowed Chat and Player List Text ===

[https://bitbucket.org/OpenUru_org/cwe-ou/pull-requests/36/shadowed-chat-and-player-list-text CWE PR #36], [https://bitbucket.org/OpenUru_org/moulscript-ou/pull-requests/23/remove-unneeded-kfontshadowed-flags-in-the MOULSCRIPT PR #23] ([https://github.com/H-uru/Plasma/pull/392 H-uru PR #392]) by CWalther, Hoikas, and Luna

Verify that the text of the player list and chat has a shadow that makes it better readable on light and patterned backgrounds, but the text inside the big KI does not.

=== Bump a public neighborhood to top of list when someone links to it ===

[https://bitbucket.org/OpenUru_org/cwe-ou/pull-requests/35/let-ptvaultsetagepublic-accept CWE PR #35], [https://bitbucket.org/OpenUru_org/moulscript-ou/pull-requests/22/bump-a-public-neighborhood-to-the-top-of MOULSCRIPT PR #22] ([https://github.com/H-uru/moul-scripts/pull/90 H-uru PR #90]) by CWalther

Verify that after linking to a public neighborhood, it appears at the top of the “Public Links” list in the Nexus. This ensures that public neighborhoods that are in active use stay (near the top) on the list in the Nexus, even after their owners disappear (as is the case for the numerous dedicated Delin & Tsogal hoods that have been made over time), with no manual toggling needed, and no need for pinned hoods.

''(<s>As of 2017-03-25, this is known not to work on Minkata and is being investigated.</s> As of 2017-03-31, the problem has been fixed and this feature is ready for testing.)''

=== Second confirmation dialog to make accidental avatar deletion less easy ===

[https://bitbucket.org/OpenUru_org/moulscript-ou/pull-requests/20/second-confirmation-dialog-to-make MOULSCRIPT PR #20] by D'Lanor

This makes it harder to lose an avatar by mistakenly hitting the “delete” button instead of the ”quit” button. [http://mystonline.com/forums/viewtopic.php?t=26127 See this discussion on the MOULa forums.]

How to test: 1. Create a test avatar. 2. Log out. 3. Select the test avatar and hit delete. 4. In the first confirmation dialog press "Yes". 5. In the second confirmation dialog press "Cancel". Your test avatar should still be there. 6. Repeat steps 3 and 4. 7. In the second confirmation dialog press "Yes". Your test avatar should be gone.

=== KI command for deleting age journal folders ===

[https://bitbucket.org/OpenUru_org/moulscript-ou/pull-requests/21/ki-command-for-deleting-age-journal MOULSCRIPT PR #21] by D'Lanor

The ''/deletefolder'' command allows you to delete redundant age journal folders (those holding KI notes, images and marker games) from your KI. It does not touch any other type of KI folder, nor does it remove the Incoming folder, which would be bad(tm). The command is case sensitive. Only empty folders will be deleted. To restore a folder, link to the corresponding age. Note: If you try to delete the folder of the age you are in, the KI immediately restores it.

How to test: To delete a folder named Bevin for example type <code>/deletefolder Bevin</code>

[[Category:Minkata Shard]]

Cyan Content Licensing Proposals

2012-02-15T21:29:38Z

Rarified: /* Signatures */

== Content Licensing Request ==
=== Introduction ===
Open source is succeeding as the community provides its first tested update to MOULa. We are directly experiencing the next challenge in our progress toward "Open Uru," Open Uru being what is created by code, content, creativity and participation. The ability to work with and distribute MOULa content under license will determine what we can and cannot do for the future of the Cyan Worlds Engine and MOULa. Working with content will in large part be responsible for increasing the interest and participation of developers, artists, and players to create a broader audience.

We are not attempting a complete statement of the aspirations of the fans with respect to MOULa content licensing. This is an exemplar of specific cases representative of fan efforts to improve MOULa for the community where it is hindered by the absence of a suitable license for the adaptation and distribution of MOULa content. These examples are used as a means to explore the licensing possibilities with Cyan Worlds and to elicit feedback on its own potential difficulties so that we might collectively establish a way forward.

=== Examples ===

* Localization - Cyan Worlds, Myst, Uru and MOULa all have an international audience. MOULa has an extensible localization system that allows content creators to provide translated text automatically. Unfortunately, many of the dialogs currently in MOULa don't take advantage of this capability and cannot be adapted properly without modifying them. GULP (formerly the Uru Localization Project) has a database of community-contributed translations in a large number of languages. H'uru has done Unicode development to allow non-US keyboards.

* Derivation - We have textures and limited content (KI and avatars) but they are unlicensed. We cannot distribute work such as scrollbars for the KI for the community to enjoy. We would like to be able to create, serve, test, and contribute work that is consistent with existing MOULa ages for eventual inclusion on MOULa.

* Distribution - Shards cannot serve binary MOULa content files. This raises the barrier against non-technical users faced with manually copying MOULa content to their shard folder as part of the shard install. The technical support load is increased, creating barriers of time, effort and cost for shard owners as well.

* Improvements - MOULa ages cannot be repaired by fans to function as designed. For example, a player who links to AhnonayCathedral always finds the automatic door closed while at the same time players who are already there see it wide open. The fix requires a change in the .prp file which currently calls the door responders directly instead of calling an intermediate Python file. We need a content license to change, test and distribute .prp files.

=== Community Needs ===

There are two primary allowances we need from Cyan Worlds to continue efforts to expand MOULa's accessibility:

* A permissive license to allow copying, translation, and distribution of information available in MOULa. For example, the .loc and .prp files. This would legalize, for example, the translation work already done by the community and enable its distribution and enjoyment.

* Access to 3ds Max source files for GUIs or other useful materials used in MOULa to normalize their use of the provided hooks in the code which they currently do not use, and a license to redistribute at least the compiled output with fixes applied. If that is impossible, an alternative is a license to modify and distribute existing .prp files containing fixes or new features such as translatable GUI items.

=== Questions ===

* Is Cyan Worlds able to indicate what difficulties there are in licensing MOULa content?

* Are there any particular aspects to content release issues where Cyan Worlds is open to suggestions?

* Are there specific limitations that fans should place on their hopes for content licensing?

* Can Cyan Worlds indicate if unreleasable content will become available in the future or under other circumstances?

=== Summary ===

We have presented collaborative concerns about the problems the community seeks to resolve regarding content licensing. We believe Cyan Worlds knows best what solutions are available to it. We hope this will be a successful collaborative path to a general solution.

The representative community members who sign below collaborated to discuss and contribute to this letter of many authors. Thank you for reading and considering this request.

This document's history on the wiki: http://wiki.openuru.org/index.php?title=Cyan_Content_Licensing_Proposals

Full discussion on the OpenUru.org forums: http://forums.openuru.org/viewtopic.php?f=91&t=635

=== Signatures ===
[[User:OHB|OHB]] 19:24, 2 February 2012 (MST)

[[User:Hoikas|Hoikas]] 19:31, 2 February 2012 (MST)

[[User:Branan|Branan]] 21:08, 2 February 2012 (MST)

[[User:Christian Walther|Christian Walther]] 05:28, 3 February 2012 (MST)

[[User:Leonardo|Leonardo]] 06:16, 3 February 2012 (MST), guildofmessengers.com

[[User:Mac Fife|Mac Fife]] 12:12, 3 February 2012 (MST), Ian M. McIntosh, OpenUru.org, (Address TBI)

[[User:Nadnerb|Nadnerb]] 14:36, 3 February 2012 (MST)

[[User:Malfhok|Malfhok]], an explorer 05:14, 4 February 2012 (MST)

[[User:Deledrius|Deledrius]] 08:57, 4 February 2012 (MST)

[[User:Marten|Marten]] 09:44, 5 February 2012 (MST)

[[User:D'Lanor|D'Lanor]] 00:00, 8 February 2012 (CET)

[[User:GPNMilano|GPNMilano]] 23:36, 8 February 2012 (MST)

[[User:JWPlatt|JWPlatt]] 10:51, 15 February 2012 (EST), Jonathan W. Platt, OpenUru.org, (Address TBI)

[[User:rarified|rarified]] 14:30, 15 February 2012 (MST), Paul Richards, OpenUru.org, (Address TBI)

<hr>

Following is additional technical information.

=== Technical Information ===
The .loc files are XML files containing translations for all textual items in Uru. GULP (http://rel.to/gulp) already has an extensive library of translations and a system to export that database to Uru-ready .loc files. Not all of Uru uses these however, as some values are hard-coded in Python scripts or the PRPs themselves, but this can be converted as the GUI items have the ability to reference the XML paths directly. Much of this Python code references the GUI items by TagIDs, which are arbitrary unique numbers used to refer to the resource. This is messy, as it must be updated when the GUI is updated and can otherwise become out of sync; it is also problematic in the current data set as not all translatable GUI items have been assigned TagIDs, meaning they must be found (if at all) by very fragile code. There is also an embedded text field in these items, which currently contains only the English text. Fortunately, these items support a self-describing LocalizationPath which automatically informs the Plasma engine's LocalizationManager which string to use, allowing localization to be handled cleanly and consistently. All of these items are a part of the data and without a license to modify and distribute the PRPs, we cannot continue the efforts to localize Uru outside of using hacks and shims to the existing elegant but under-utilized engine.

As an additional benefit to Cyan: the changes made under the proposed licensing could be relatively easy for Cyan to integrate back into their own assets without affecting current functionality. This would be impossible if only binary changes are allowed to the exported PRPs rather than the .max sources, and it allows Cyan to take advantage of the localization code changes in the engine once it reaches maturity in the community testing with very little friction.

An extra note about the alternative suggestion in (2) which only allows modification of PRPs -- The reason this is inferior, aside from the obvious, is that while it would allow the immediate goal of activating the built-in localization, I anticipate minor bugs such as text flow and sizing in the UI when displaying languages other than the one for which they were designed. These will be extremely difficult to fix under the limited alternative solution and should be far simpler with access to the original 3D Studio Max source files.

=== License Suggestions ===
I was going to wrap up by suggesting licenses in order to simplify the burden on Cyan, but as the OU Content Licensing thread proves there are many viable options and they all address different needs. Unfortunately, in order to find where that spot of compromise is we'll need feedback from Cyan on this point. I implore Cyan, should they wish to consider this request, to respond with their concerns and needs first. At that point tangible suggestions can be made regarding the specifics and the proposal can move forward should they be agreeable.

At any rate, for the .loc files I'd suggest terms which preserves Cyan's ownership of the text (some of which, being canon from the Myst universe, has inherent value to them), while allowing edits and distribution by the community. A disclaimer stating that Cyan is only responsible for the original English text may also be desirable.

=== Links ===
Forum link: [http://forums.openuru.org/viewtopic.php?f=91&t=635 Content Licensing]

Foundry Certificate Installation

2011-10-20T02:33:40Z

Rarified: /* Opera */

{{draft}}
The OpenUru.org Foundry tools such as JIRA bugtracking use SSL (Secure Sockets Layer) to encrypt transactions and to give confidence that you are connected to the correct server. Currently, this is a "self-signed" certificate and not one that has been validated by the main certificate authorities, so most browsers will display a warning when you navigate to one of the Foundry pages.

You can avoid these warnings by installing the certificate in your browser's certificate store. This can be done when you first visit the foundry, but the methods vary greatly across browsers. It is perhaps easier to manually install the certificate before visting the Foundry. The certificate will also need to be installed in repository tools (Mercurial or Subversion) if you intend using SSL to access the Foundry repositories.

The instructions given here relate to the Windows versions of the applications.

== Obtaining the Certificate ==

(For manual installation into applications not listed below)

Download a copy of the certificate using this link: [http://foundry.openuru.org/assets/Foundry/foundry.crt Foundry Certificate]

== Browser Installation ==

Please read the instructions so you know what to do '''before''' clicking on the link to the certificate, or right click the link and open it in a new tab or window.

=== Firefox ===
Click on the following link: [http://foundry.openuru.org/assets/Foundry/foundry.crt Foundry Certificate]
A popup will appear titled "Downloading Certificate". Mark the check box for "Trust this CA to identify web sites" then click "OK" (you may wish to click "View" to check the certificate details first). The certificate is now installed, and when visiting the Foundry you should see the padlock symbol at the bottom right of your browser: hovering the mouse pointer over this should show "Authenticated by OpenUru.org"

'''Note:''' Firefox 3.6.0 contains a bug which may cause loss of data when using JIRA - users should upgrade their Firefox installation to 3.6.2 or later.

=== Internet Explorer ===

Click on the following link: [http://foundry.openuru.org/assets/Foundry/foundry.crt Foundry Certificate]
A popup will appear titled "File Download - Security Warning". Click "Open" and the certificate details will be displayed in a new popup wher you can inspect them. On the "General" tab, click "Install Certificate...". When the Certificate Import Wizard appears click "Next>", then on the Certificate Store page select "Automatically select the certificate store based on the type of certificate" and click "Next>" and then "Finish". Another popup will appear titled "Security Warning" and asking "Do you want to install this certificate?" - Click "Yes". You should get a message telling you that the import was successful. Click "OK" on any remaining dialog boxes. The certificate is now installed, and when visiting the Foundry you should see the padlock symbol to the right of the URL bar with a blue background.

'''Note:''' If you install the certificate using Internet Explorer as described above, then you should find that the certificate will automatically be trusted by Safari and Chrome browsers on the same machine, since both of these use the Windows Internet Settings.

=== Google Chrome ===
Chrome (under Microsoft Windows) uses the same certificate store as Internet Explorer, so the process is very similar: Click on the following link: [http://foundry.openuru.org/assets/Foundry/foundry.crt Foundry Certificate]
The "Downloads" popup will appear along with another window asking if you want to open or save the file "foundry.crt". Click "Open" and a new popup will appear titled "File Download - Security Warning". Click "Open" and the certificate details will be displayed in a new popup wher you can inspect them. On the "General" tab, click "Install Certificate...". When the Certificate Import Wizard appears click "Next>", then on the Certificate Store page select "Automatically select the certificate store based on the type of certificate" and click "Next>" and then "Finish". Another popup will appear titled "Security Warning" and asking "Do you want to install this certificate?" - Click "Yes". You should get a message telling you that the import was successful. Click "OK" on any remaining dialog boxes. The certificate is now installed, and when visiting the Foundry you should see the padlock symbol to the right of the URL bar.

=== Apple Safari ===
On Microsoft Windows, Safari uses the same certificate store as Internet Explorer, so the process is very similar: Click on the following link: [http://foundry.openuru.org/assets/Foundry/foundry.crt Foundry Certificate]
The "Downloads" popup will appear along with another window asking if you want to open or save the file "foundry.crt". Click "Open" and a new popup will appear titled "File Download - Security Warning". Click "Open" and the certificate details will be displayed in a new popup wher you can inspect them. On the "General" tab, click "Install Certificate...". When the Certificate Import Wizard appears click "Next>", then on the Certificate Store page select "Automatically select the certificate store based on the type of certificate" and click "Next>" and then "Finish". Another popup will appear titled "Security Warning" and asking "Do you want to install this certificate?" - Click "Yes". You should get a message telling you that the import was successful. Click "OK" on any remaining dialog boxes. The certificate is now installed, and when visiting the Foundry you should see the padlock symbol to the right of the URL bar.

=== Opera ===
Using the Opera browser to access an SSL page on the Foundry will cause the browser to raise a "Security Issue" popup box. The text in this box says ''The server's certificate chain is incomplete, and the signer(s) are not registered. Accept?'' You can examine the description of the certificate with the "Security" tab on this popup. If you are satisfied with the information and wish to use the certificate, click the ''Approve'' button, and the certificate will be stored in Opera's trusted certificate list, and you will be able to browse secured pages from the Foundry.

If you wish to manually install the certificate in Opera, click on the certificate link: [http://foundry.openuru.org/assets/Foundry/foundry.crt Foundry Certificate]. A "Install Certificate" popup window will appear, showing the certificate from '''foundry.openuru.org''' You can click the "View" button to display information about the certificate. You can then click the "Install" button to install the certificate or "Cancel" to ignore the certificate and not change Opera's certificate list.

== Repository Installation ==

=== TortoiseHg 2.0.x (Mercurial) ===
If you have tried to use the "Clone Repository" command to create the Mercurial repository and found that it came back with an error like "SSL: Server certificate verify failed" then try the steps below.
# Open TortoiseHg Workbench
# Click on New Repository in the File Menu
# Browse to the folder that you want to save the source to. This folder must be empty.
# Now the buttons on the toolbar close to the top of the window should be lit up.
# Select the green recycle-like icon that will bring up the synchronize settings in the lower part of the screen under '''Remote Repository'''
# In the drop down box select: '''https'''
# In the first box put '''foundry.openuru.org/hg'''
# In the last box on that line put the project name (e.g CWE) see the [http://www.openuru.org/pages/Development.php Development] page under Foundry Repositories
# Now click on the '''Padlock Button''' next to the drop down box
# Choose the second option '''Verify with stored host fingerprint (good)''' under Secure HTTPS Connection and Click '''Query'''. The fingerprint is (as of this writing): <code>32:1b:b2:1c:9a:fe:d9:17:b0:78:76:ea:87:68:ad:1a:34:ab:a8:8e</code>
# Put your Username (all lowercase) and Password for your JIRA Account in the appropriate boxes and click '''Save'''
# On the right hand side of the screen is a '''Save''' button click it and the Save on the window that pops up
# On the same toolbar used in step 5. Click on the button with the two yellow cylinders and the green arrow pointing towards you. This is the '''Pull incoming changes''' button.
# After the download is complete you must update the local repository before being able to use it. Open the Output Log either by using Ctrl + L or in the View menu as '''Show Output Log'''
# After the % sign on the last line of the Output Log type: <code>hg update</code>
# You should get a command completed successfully line.
# You are now ready to work on/view the code.

=== TortoiseSVN (Subversion) ===
There is no requirement to install the certificate for TortoiseSVN.

=== MacHg (Mercurial) ===
# Append the certificate to the end of your ~/Library/Application Support/MacHg/TrustedCertificates.pem file.

Foundry Certificate Installation

2011-10-20T02:28:43Z

Rarified: /* Opera */

{{draft}}
The OpenUru.org Foundry tools such as JIRA bugtracking use SSL (Secure Sockets Layer) to encrypt transactions and to give confidence that you are connected to the correct server. Currently, this is a "self-signed" certificate and not one that has been validated by the main certificate authorities, so most browsers will display a warning when you navigate to one of the Foundry pages.

You can avoid these warnings by installing the certificate in your browser's certificate store. This can be done when you first visit the foundry, but the methods vary greatly across browsers. It is perhaps easier to manually install the certificate before visting the Foundry. The certificate will also need to be installed in repository tools (Mercurial or Subversion) if you intend using SSL to access the Foundry repositories.

The instructions given here relate to the Windows versions of the applications.

== Obtaining the Certificate ==

(For manual installation into applications not listed below)

Download a copy of the certificate using this link: [http://foundry.openuru.org/assets/Foundry/foundry.crt Foundry Certificate]

== Browser Installation ==

Please read the instructions so you know what to do '''before''' clicking on the link to the certificate, or right click the link and open it in a new tab or window.

=== Firefox ===
Click on the following link: [http://foundry.openuru.org/assets/Foundry/foundry.crt Foundry Certificate]
A popup will appear titled "Downloading Certificate". Mark the check box for "Trust this CA to identify web sites" then click "OK" (you may wish to click "View" to check the certificate details first). The certificate is now installed, and when visiting the Foundry you should see the padlock symbol at the bottom right of your browser: hovering the mouse pointer over this should show "Authenticated by OpenUru.org"

'''Note:''' Firefox 3.6.0 contains a bug which may cause loss of data when using JIRA - users should upgrade their Firefox installation to 3.6.2 or later.

=== Internet Explorer ===

Click on the following link: [http://foundry.openuru.org/assets/Foundry/foundry.crt Foundry Certificate]
A popup will appear titled "File Download - Security Warning". Click "Open" and the certificate details will be displayed in a new popup wher you can inspect them. On the "General" tab, click "Install Certificate...". When the Certificate Import Wizard appears click "Next>", then on the Certificate Store page select "Automatically select the certificate store based on the type of certificate" and click "Next>" and then "Finish". Another popup will appear titled "Security Warning" and asking "Do you want to install this certificate?" - Click "Yes". You should get a message telling you that the import was successful. Click "OK" on any remaining dialog boxes. The certificate is now installed, and when visiting the Foundry you should see the padlock symbol to the right of the URL bar with a blue background.

'''Note:''' If you install the certificate using Internet Explorer as described above, then you should find that the certificate will automatically be trusted by Safari and Chrome browsers on the same machine, since both of these use the Windows Internet Settings.

=== Google Chrome ===
Chrome (under Microsoft Windows) uses the same certificate store as Internet Explorer, so the process is very similar: Click on the following link: [http://foundry.openuru.org/assets/Foundry/foundry.crt Foundry Certificate]
The "Downloads" popup will appear along with another window asking if you want to open or save the file "foundry.crt". Click "Open" and a new popup will appear titled "File Download - Security Warning". Click "Open" and the certificate details will be displayed in a new popup wher you can inspect them. On the "General" tab, click "Install Certificate...". When the Certificate Import Wizard appears click "Next>", then on the Certificate Store page select "Automatically select the certificate store based on the type of certificate" and click "Next>" and then "Finish". Another popup will appear titled "Security Warning" and asking "Do you want to install this certificate?" - Click "Yes". You should get a message telling you that the import was successful. Click "OK" on any remaining dialog boxes. The certificate is now installed, and when visiting the Foundry you should see the padlock symbol to the right of the URL bar.

=== Apple Safari ===
On Microsoft Windows, Safari uses the same certificate store as Internet Explorer, so the process is very similar: Click on the following link: [http://foundry.openuru.org/assets/Foundry/foundry.crt Foundry Certificate]
The "Downloads" popup will appear along with another window asking if you want to open or save the file "foundry.crt". Click "Open" and a new popup will appear titled "File Download - Security Warning". Click "Open" and the certificate details will be displayed in a new popup wher you can inspect them. On the "General" tab, click "Install Certificate...". When the Certificate Import Wizard appears click "Next>", then on the Certificate Store page select "Automatically select the certificate store based on the type of certificate" and click "Next>" and then "Finish". Another popup will appear titled "Security Warning" and asking "Do you want to install this certificate?" - Click "Yes". You should get a message telling you that the import was successful. Click "OK" on any remaining dialog boxes. The certificate is now installed, and when visiting the Foundry you should see the padlock symbol to the right of the URL bar.

=== Opera ===
Using the Opera browser to access an SSL page on the Foundry will cause the browser to raise a "Security Issue" popup box. The text in this box says ''The server's certificate chain is incomplete, and the signer(s) are not registered. Accept?'' You can examine the description of the certificate with the "Security" tab on this popup. If you are satisfied with the information and wish to use the certificate, click the ''Approve'' button, and the certificate will be stored in Opera's trusted certificate list, and you will be able to browse secured pages from the Foundry.

== Repository Installation ==

=== TortoiseHg 2.0.x (Mercurial) ===
If you have tried to use the "Clone Repository" command to create the Mercurial repository and found that it came back with an error like "SSL: Server certificate verify failed" then try the steps below.
# Open TortoiseHg Workbench
# Click on New Repository in the File Menu
# Browse to the folder that you want to save the source to. This folder must be empty.
# Now the buttons on the toolbar close to the top of the window should be lit up.
# Select the green recycle-like icon that will bring up the synchronize settings in the lower part of the screen under '''Remote Repository'''
# In the drop down box select: '''https'''
# In the first box put '''foundry.openuru.org/hg'''
# In the last box on that line put the project name (e.g CWE) see the [http://www.openuru.org/pages/Development.php Development] page under Foundry Repositories
# Now click on the '''Padlock Button''' next to the drop down box
# Choose the second option '''Verify with stored host fingerprint (good)''' under Secure HTTPS Connection and Click '''Query'''. The fingerprint is (as of this writing): <code>32:1b:b2:1c:9a:fe:d9:17:b0:78:76:ea:87:68:ad:1a:34:ab:a8:8e</code>
# Put your Username (all lowercase) and Password for your JIRA Account in the appropriate boxes and click '''Save'''
# On the right hand side of the screen is a '''Save''' button click it and the Save on the window that pops up
# On the same toolbar used in step 5. Click on the button with the two yellow cylinders and the green arrow pointing towards you. This is the '''Pull incoming changes''' button.
# After the download is complete you must update the local repository before being able to use it. Open the Output Log either by using Ctrl + L or in the View menu as '''Show Output Log'''
# After the % sign on the last line of the Output Log type: <code>hg update</code>
# You should get a command completed successfully line.
# You are now ready to work on/view the code.

=== TortoiseSVN (Subversion) ===
There is no requirement to install the certificate for TortoiseSVN.

=== MacHg (Mercurial) ===
# Append the certificate to the end of your ~/Library/Application Support/MacHg/TrustedCertificates.pem file.

Craftwork

2011-04-21T03:04:37Z

Rarified:

{{UruDocProj}}
{{tech-stub}}
== [[Game Overview]] ==

== [[Technical Architecture]] ==
=== [[Modelling]] ===
=== [[Communication]] ===
=== [[Physics]] ===
=== [[Game Client]] ===
=== [[Game Servers]] ===

== [[Tools and Processes]] ==
=== [[Using the OpenUru Repositories]] ===
=== [[Building URU from code]] ===
=== [[URU Runtime Environments]] ===
==== [[CyanWorlds.com Engine‎|Client]] ====
* [[Build the client with MSVC 2003‎]]

==== [[Server]] ====
==== [[Network and Communication]] ====
* [[Wireshark Plugin]]

=== [[Modelling Tools]] ===
==== [[Physics]] ====
===== [[Plasma]] =====
==== [[3D Model Construction and Integration]] ====
==== [[Video Integration]] ====
==== [[Sound Integration]] ====

== [[Open Source Materials from Cyan]] ==
=== [[Conditions of Use]] ===
=== [[Location of Materials]] ===
=== [[How to gain access]] ===


[[Category:Documentation]]

Craftwork

2009-01-10T23:14:17Z

Rarified: New page: == Game Overview == == Technical Architecture == === Modelling === === Communication === === Physics === === Game Client === === Game Servers === == [[Tools ...

== [[Game Overview]] ==

== [[Technical Architecture]] ==
=== [[Modelling]] ===
=== [[Communication]] ===
=== [[Physics]] ===
=== [[Game Client]] ===
=== [[Game Servers]] ===

== [[Tools and Processes]] ==
=== [[Building URU from code]] ===
=== [[URU Runtime Environments]] ===
==== [[Client]] ====
==== [[Server]] ====
==== [[Network and Communication]] ====
=== [[Modelling Tools]] ===
==== [[Physics]] ====
===== [[Plasma]] =====
==== [[3D Model Construction and Integration]] ====
==== [[Video Integration]] ====
==== [[Sound Integration]] ====

== [[Open Source Materials from Cyan]] ==
=== [[Conditions of Use]] ===
=== [[Location of Materials]] ===
=== [[How to gain access]] ===

Artwork

2009-01-10T23:02:47Z

Rarified: New page: == Images == == Music == == Worlds == == Challenges ==

== [[Images]] ==

== [[Music]] ==

== [[Worlds]] ==

== [[Challenges]] ==

URUDoc - Main

2009-01-10T23:00:48Z

Rarified: New page: {| cellspacing="0" border="1" cellpadding="15" style="background-color:#ffffcc;" |''Ed note: This is a work-in-progress. Feel free to add to it'' |} == The Art == A section to...

{| cellspacing="0" border="1" cellpadding="15" style="background-color:#ffffcc;"
|''Ed note: This is a work-in-progress. Feel free to add to it''
|}
== [[Artwork|The Art]] ==
A section to document how to produce, encode and integrate various art forms (graphics, scripting, music, puzzles) into the Uru virtual worlds.

== [[Craftwork|The Craft]] ==
A section on the underlying mechanics of the Uru game environment. Server and client code, architectural documentation or analysis.

== [[Canon|The Canon]] ==
So important to Uru is the underlying storyline. Use this area to document (or reference) what has been provided to describe the history and known motivations and behaviors of the D'ni. Also apropriate are discussions about how D'ni ''(in character)'' technology and art worked.

Main Page

2009-01-10T22:36:31Z

Rarified:

== Welcome to OpenURU.org==

OpenURU.org provides a venue with resources for a diverse community of projects to encourage a cooperative environment for the exploration, development and exchange of ideas in Cyan Worlds' Myst universe and Open Source URU.

This wiki contains information of interest to ongoing projects at OpenURU.org.

Use 'search' on the left to find information you wish to know.

'''All logged in members''' are able to edit the wiki unless the page is protected. '''Edit responsibly'''.

'''Proper spelling and grammar are taken seriously.''' Writing well with good grammar is appreciated.

Visit our home page at:
* [http://OpenURU.org OpenURU.org]

Visit our forums at:
* [http://forums.OpenURU.org forums.OpenURU.org]

== [[URUDoc:Main|The Open URU Documentation Project]] ==

As we gain knowledge about how URU works, there should be a place to contain or index that knowledge. This area is proposed as a repository and a place to organize that information. Right now I've just started filling out a taxonomy. Let's see where it goes.