Guild of Writers Wiki - Recent changes [en]

Talk:Uru:CC Installation

2012-05-17T19:38:40Z

Remove redirect:

Uru:CC Sequence Prefixes

2012-05-17T17:40:12Z

clarify which games this is about

Talk:Uru:CC Installation

2012-05-17T17:39:14Z

Remove redirect:

TPOTS Sequence Prefixes

2012-05-17T17:39:08Z

moved [[TPOTS Sequence Prefixes]] to [[Uru:CC Sequence Prefixes]] use the actual game name, not the expansion pack

Talk:Uru:CC Installation

2012-05-17T11:16:34Z

Remove redirect:

TPOTS Installation

2012-05-17T11:13:55Z

deleted "[[TPOTS Installation]]" Useless redirect.

Talk:Setting Up a Shard

2012-05-17T11:13:09Z

Main Page

2012-05-17T09:39:57Z

typo

Alcugs

2012-05-17T09:38:31Z

make clear that the alcugs wiki is outdated

Talk:Uru:CC Installation

2012-05-17T09:36:48Z

Remove redirect

New page

== Remove redirect ==

Could someone remove the redirect from "TPOTS Installation" please? Also, I was unsure whether "CC Installation" or "Uru:CC Installation" would be more in line with the wording of the rest of the wiki... but then, it doesn't matter that much anyway ;-)

[[User:Diafero|Diafero]] 05:36, 17 May 2012 (EDT)

Talk:Setting Up a Shard

2012-05-17T09:34:16Z

Archive:Blender Beginner's Classroom Index

2012-05-16T22:16:33Z

Superfluous Archive category.

FNI Settings

2012-05-16T22:13:38Z

Polish. Separate Blender instructions from general information.

Floor Textures for the Community Nexus

2012-05-16T22:01:30Z

moved [[Floor Textures for the Community Nexus]] to [[Archive:Floor Textures for the Community Nexus]] [redirect suppressed]

Community Nexus

2012-05-16T22:01:05Z

moved [[Community Nexus]] to [[Archive:Community Nexus]] [redirect suppressed]

Talk:Setting Up a Shard

2012-05-16T21:22:01Z

Playing Fan Ages

2012-05-16T16:25:43Z

What do I need to play Fan Ages?: fix link

TPOTS Installation

2012-05-16T16:25:10Z

moved [[TPOTS Installation]] to [[Uru:CC Installation]] We shouldn't confuse people by using the wrong name here, this is actually about CC

Talk:Setting Up a Shard

2012-05-16T16:23:52Z

server.ini:

TPOTS Sequence Prefixes

2012-05-16T05:42:51Z

Full list of all known Sequence Prefixes:

Open Source Task List

2012-05-16T02:18:23Z

Actualize.

DIRTSAND:Getting Started

2012-05-16T02:03:40Z

Add credit to Hoikas too.

Development

2012-05-16T01:15:55Z

Added a bit more information.

File:DIRTSAND.png

2012-05-15T23:19:50Z

uploaded "[[File:DIRTSAND.png]]" Unofficial logo (remove this, developers of DIRTSAND, if you don't like it!).

Development:DIRTSAND

2012-05-15T23:18:29Z

Removed duplicated content and added new content.

Category:DIRTSAND

2012-05-15T23:17:22Z

Created page with "Articles relating to DIRTSAND, a server software for open-source shards."

New page

Articles relating to [[DIRTSAND]], a server software for open-source shards.

DIRTSAND

2012-05-15T23:16:59Z

Added DIRTSAND page.

New page

{{InfoTool
|Name=DIRTSAND
|Image=DIRTSAND.png
|Category=Server
|Licence=LGPL
}}The D'ni in Real Time Server and Network Daemon (DIRTSAND) is a server software created by [[User:Zrax|Zrax]] and developed by H'uru to run open-source [[MO:UL]] [[Shard|Shards]]. It is built for integration with the H'uru fork of the [[CyanWorlds.com Engine]].

The source code for DIRTSAND is available on Github: [https://github.com/H-uru/dirtsand H-uru/dirtsand]. For more information about its development, read the [[Development:DIRTSAND|development article]].

== Features ==
DIRTSAND as it stands today possesses the following features:
* Compatibility with CWE-ou (partial), H'uru CWE and PlasmaClient (partial) clients.
* Fully-functional auth server, file server (optional) and gatekeeper.
* Interactive operating terminal.
* Support for Linux and potentially other *nix systems.
* Facilitated setup process.
* Absence of game manager (feature, not bug): this means that various game functions such as Heek won't work unless used with the H'uru client or another appropriately modified client.

== Setting Up ==
DIRTSAND has been designed to be easily-deployable on Linux systems. It might work on other *nix OSes, but it hasn't been tested. The [[DIRTSAND:Getting Started|getting started]] guide will help you set up your Shard using DIRTSAND.

DIRTSAND consists of an interactive terminal run on a terminal session. It is recommended that you use screen or some other such program to be able to run DIRTSAND in the background. It accepts the following commands for operation:
* <code>addacct <user> <password></code>: adds a new user account into the database.
* <code>clients</code>: lists all connected clients.
* <code>commdebug <on|off></code>: available only for debug builds; used to debug.
* <code>keygen new</code>: generates new keys for your <code>dirtsand.ini</code> and <code>server.ini</code> files.
* <code>keygen show</code>: shows the <code>server.ini</code> keys.
* <code>welcome <message></code>: changes the welcome message for your server.
* <code>help</code>: displays information about the available commands.
* <code>restart <auth|lobby|status> [...]</code>: restart the specified server process.
* <code>quit</code>: shuts down DIRTSAND.

[[Category:DIRTSAND]]

DIRTSAND:Getting Started

2012-05-15T23:09:33Z

Added build ID info.

Talk:Setting Up a Shard

2012-05-15T22:39:55Z

Talk:Setting Up a Shard

2012-05-15T17:46:35Z

server.ini

New page

== server.ini ==

Is it really necessary to put both of these lines into the server.ini?
Server.Gate.Host "123.45.67.89"
Server.Auth.Host "123.45.67.89"
If yes, this is a bug - the client should query the auth server from the gateway. Dirtsand always supported this, and I patched the client months ago to perform this query if there is no auth server specified in server.ini. Cyan's gateway does not support such a query, but that's okay since the server.ini for MOULa contains the auth server IP.

[[User:Diafero|Diafero]] 13:46, 15 May 2012 (EDT)

Forming An Age Project Team

2012-05-15T11:43:46Z

Stylize table.

3ds Max

2012-05-15T11:29:40Z

Remove stub template.

Template:InfoTool

2012-05-15T11:24:32Z

Change image size.

File:3dsMaxLogo.png

2012-05-15T11:23:29Z

uploaded "[[File:3dsMaxLogo.png]]"

Template:InfoTool

2012-05-15T11:23:10Z

Created page with "<includeonly>{|class="infobox" |- |colspan="2"|<h2>{{{Name}}}</h2> |- |colspan="2"|[[File:{{{Image}}}|200px]] |- |'''Category''' |{{{Category}}} |- |'''Licence''' |{{{Licence}..."

New page

<includeonly>{|class="infobox"
|-
|colspan="2"|<h2>{{{Name}}}</h2>
|-
|colspan="2"|[[File:{{{Image}}}|200px]]
|-
|'''Category'''
|{{{Category}}}
|-
|'''Licence'''
|{{{Licence}}}
|-
|colspan="2"|__TOC__
|}
[[Category:Tools]]</includeonly>
<noinclude>A template for software tools.</noinclude>

Minimalistic Development Shard

2012-05-15T11:19:23Z

moved [[Minimalistic Development Shard]] to [[Setting Up a Shard]] [redirect suppressed]

Max:Details

2012-05-15T02:46:40Z

Add Max Tutorials category.

DIRTSAND:Getting Started

2012-05-15T02:37:53Z

Switched to <source> tag.

CWE:Getting Started

2012-05-15T02:30:01Z

Added server.ini instructions.

Development:DirtSand

2012-05-15T02:15:19Z

moved [[Development:DirtSand]] to [[Development:DIRTSAND]] [redirect suppressed]

DIRTSAND:Getting Started

2012-05-15T02:14:25Z

Created page with "This tutorial will help you set up your own fully-functional shard using DIRTSAND, a server software for MO:UL clients by H'uru. == Prerequisites == You'll need a..."

New page

This tutorial will help you set up your own fully-functional [[shard]] using [[DIRTSAND]], a server software for [[MO:UL]] clients by H'uru.

== Prerequisites ==
You'll need a few tools to compile and set up DIRTSAND. Most of these consist of development libraries (frequently suffixed with -dev in repositories):
* '''GCC 4.6+''' (other C++11-compliant compilers might work, but haven't been tested),
* '''PostgreSQL''': you will need both the libraries (for compiling) and the database server (for the vault),
* '''OpenSSL''' (libssl),
* '''libreadline''',
* '''zlib''',
* '''git''': used to acquire the source code for DIRTSAND,
* '''cmake''': used to create the makefiles for GCC 4.6+.
Additionally, a client to test the working status would be useful. See the [[CWE:Getting Started|getting started guide]] for help on this subject. Your client will need to be able to connect to port 14617, so you might have to open it up on your firewall.

Finally, it is recommended that you create a UNIX user to run DIRTSAND with an associated home directory containing DIRTSAND:
sudo useradd dirtsand -d /opt/dirtsand -m -p <password> -s /bin/bash

== Compiling ==
The first step is to download and compile DIRTSAND for your system; make sure you have all the appropriate libraries installed. First, clone the H'uru repository:
git clone git://github.com/H-uru/dirtsand.git dirtsand
cd dirtsand
Once you have the sources, you'll need to run CMake and G++ to compile the code:
mkdir build && cd build
cmake -DCMAKE_INSTALL_PREFIX=/opt/dirtsand ..
make && sudo make install
cd ..
If your system complains about missing libraries but you have installed them, you can use the CMake GUI to point to the libraries' location.

== Database Setup ==
You will need a PostgreSQL server which DIRTSAND can access with a user capable of adding schemas, tables, etc. into. For the proposed installation here, a <code>dirtsand</code> database with ownership set to a <code>dirtsand</code> user (such as the one created beforehand in this tutorial).
sudo -u postgres psql -d template1
template1=# CREATE USER dirtsand WITH PASSWORD '<password>';
template1=# CREATE DATABASE dirtsand WITH TEMPLATE = template0 ENCODING = 'UTF8';
template1=# ALTER DATABASE dirtsand OWNER TO dirtsand;
template1=# \q
The next step is to enable UUID functionnality for PostgreSQL. The technique for this varies depending on PostgreSQL's version. Until PostgreSQL 9.1, the extension had to be manually loaded into PostgreSQL:
sudo -u postgres psql -d dirtsand < /path/to/uuid-ossp.sql
In Ubuntu with PostgreSQL 8.4, for example, the path is <code>/usr/share/postgresql/8.4/contrib/uuid-ossp.sql</code>.

From 9.1 and onwards, you need to make sure the <code>postgresql-contrib</code> package is installed (the name will vary depending on your distribution) then load the extension:
psql
CREATE EXTENSION "uuid-ossp";
Now you need to load the initial structure for your DB, the SQL files being available in DIRTSAND's source code:
sudo -u postgres psql -d dirtsand < db/dbinit.sql
sudo -u postgres psql -d dirtsand < db/functions.sql
Your database should now be ready.

== Configuring ==
DIRTSAND is configured from a <code>dirtsand.ini</code> file placed in the execution directory for DIRTSAND. It needs to be adjusted to connect to your database, to have all the appropriate RC4 keys, which DIRTSAND can automatically generate for you:
bin/dirtsand
ds-902> keygen new
ds-902> quit
After running for a bit, this will output six keys to be copied into your <code>dirtsand.ini</code> file and six others into your client's <code>server.ini</code> (this requires either PlasmaClient or the H'uru fork of [[CWE]]). You can safely ignore all startup errors. A sample file for <code>dirtsand.ini</code> has been placed in the source directory; you need to fill it in with your keys and database details (and any other configuration details you need to fill in):
sudo cp dirtsand.sample.ini /opt/dirtsand/dirtsand.ini
sudo chown dirtsand /opt/dirtsand/dirtsand.ini
su - dirtsand
nano dirtsand.ini
Replace the dummy values with the output under "Server keys".

You'll also have to specify the external host addresses for your DIRTSAND server (it can either be an IP number of a domain name).

== Files Setup ==
Your server now needs to be provided with files to distribute to clients. These include SDL files, Python scripts, data files, client files, and so on.

You will need the files available from the [https://github.com/H-uru/moul-scripts moul-scripts] repository.

'''WARNING:''' the current moul-scripts appear to be broken in some aspect which prevents GUM (see below) from generating the manifests. Until such a time as the issue is tracked down and fixed, it is recommended that you use the [https://github.com/GehnShard/moul-scripts Gehn Shard scripts] instead.

'''DISCLAIMER:''' it is currently forbidden to distribute Cyan-created content (age models, sound effects). Therefore, your clients must already have all the required data files (excluding fan content you are allowed to distribute).

=== Ages and SDL ===
You will first need to create two folders for the <code>.age</code> and <code>.sdl</code> files, as specified in your <code>dirtsand.ini</code> configuration. Into these folders you must copy only the <code>.age</code> and <code>.sdl</code> files, in unencrypted form (available from the moul-scripts repo).

=== File Server ===
The file server is optional if you are using only Internal clients, but is required by External clients and to update automatically all client connecting to your server. This consists of a series of manifest files (<code>.mfs</code>) of the following format:
remote_filename.ext,local_filename.ext.gz,decompressed_hash,compressed_hash,decompressed_size,compressed_size,flags
Make sure the path to the local file is specified using Windows folder separators (backslahes: "\"). The <code>bin/dsData.sh</code> script can automatically generate a manifest line for a specified file. The lines must reflect the details for the encrypted versions of the files.

There is currently no official manifest generator for DIRTSAND. However, Lyrositor has provided a script for this purpose heavily based on branan's (a.k.a PaladinOfKaos) [https://github.com/branan/moulbuild-scripts script]. It is available for download here: [https://github.com/Lyros/GUM Generator of Uru Manifests]. You will need a reference installation containing the unencrypted <code>.pak</code file and <code>.sdl</code> files in <code>Python</code> and <code>SDL</code>, along with all the files from the <code>dat</code> and <code>sfx</code> folders from MO:ULa. On top of the <code>dat<code> folder, you should then copy the <code>dat</code> folder from moul-scripts to get the unencrypted versions. It requires Python 2.7 and [[libHSPlasma#Python|libHSPlasma for Python]].

'''Note on Python:''' the Python scripts need to be compressed into a <code>Python.pak</code> file. This can be achieved using the <code>plPythonPack.exe</code> tool obtained from compiling CWE (the tool only uses relative paths).

== Running ==
If all went well, you can now start your server:
bin/dirtsand dirtsand.ini
And that's it. You will obtain an interactive terminal to operate DIRTSAND which will output log messages as they are printed. You might find it useful however to start DIRTSAND in a GNU screen/Byobu or X session.

=== Adding Accounts ===
You might find it difficult to connect without an account. To add one in DIRTSAND, type the following command into DIRTSAND's terminal:
addacct <username> <password>
Accounts can also be manually inserted into the DB.

== Customizing ==
DIRTSAND allows for a certain degree of flexibility. Here are a few things you can do:
* '''Changing default Neighborhood names:''' the prefixes for Hood names is set in the DB under "game->PublicAges", in the "AgeFilename" row and in the "AgeUserName"/"AgeDesc" fields; simply edit it to change the value.

== Developing ==
If you are interested in lending a hand to DIRTSAND's development, visit the [[Development:DIRTSAND|appropriate page]].

[[Category:DIRTSAND]]

MediaWiki:Writers.css

2012-05-15T02:13:51Z

Fix styling for redirects.

MO:UL

2012-05-15T02:12:40Z

Redirected page to Uru#Current Version: MO:UL

New page

#REDIRECT [[Uru#Current Version: MO:UL]]

CWE

2012-05-15T02:12:04Z

Fix redirect.

CWE

2012-05-15T02:11:50Z

Add redirect.

New page

#REDIRECT [[CWE]]

KI: New Feature Log

2012-05-14T18:30:01Z

Polish.

3ds Max

2012-05-14T18:24:36Z

Polish.

Tutorials

2012-05-14T18:16:39Z

3ds Max

← Older revision		Revision as of 19:38, 17 May 2012
Line 8:		Line 8:

	::Good catch. However, we should probably keep the redirect there since there is a whole bunch of external links to it, and the page is rather important. And it definitely is only about CC/TPOTS/UU ("old" Uru versions), the prefix space in MOUL is independent. For that reason, I renamed it to using "Uru:CC" as well (since almost nobody cares about UU anymore). -- [[User:Diafero\|Diafero]] 13:39, 17 May 2012 (EDT)		::Good catch. However, we should probably keep the redirect there since there is a whole bunch of external links to it, and the page is rather important. And it definitely is only about CC/TPOTS/UU ("old" Uru versions), the prefix space in MOUL is independent. For that reason, I renamed it to using "Uru:CC" as well (since almost nobody cares about UU anymore). -- [[User:Diafero\|Diafero]] 13:39, 17 May 2012 (EDT)
		+
		+	::I agree. Let's keep the redirect. A job well done! :) --[[User:Lyrositor\|Lyrositor]] 15:38, 17 May 2012 (EDT)

← Older revision		Revision as of 17:40, 17 May 2012
Line 1:		Line 1:
−	This page manages the sequence prefixes for [[Uru#Old Versions\|~~The Path of the Shell~~]] and [[Uru#Old Versions\|Uru~~: Complete Chronicles~~]]. Sequence prefixes uniquely identify ages, and it is important to keep a global list to prevent collisions. Two ages with the same sequence prefix can not be installed at the same time. The same is of course also true for the age filename, so this list also serves to reserve those.	+	This page manages the sequence prefixes for [[Uru#Old Versions\|Uru: Complete Chronicles]] and other [[Uru#Old Versions\|old Uru versions]]. Sequence prefixes uniquely identify ages, and it is important to keep a global list to prevent collisions. Two ages with the same sequence prefix can not be installed at the same time. The same is of course also true for the age filename, so this list also serves to reserve those.

	== Rules ==		== Rules ==

← Older revision		Revision as of 17:39, 17 May 2012
Line 6:		Line 6:

	:KABOOM! :D Also, I think the current title is fine. It specifies clearly what it is talking about. However, it does conflict with the "TPOTS Sequence Prefixes" nomenclature (even though this is a minor point). Could that page be renamed to "Uru Sequence Prefixes", or is it really just for TPOTS?--[[User:Lyrositor\|Lyrositor]] 07:16, 17 May 2012 (EDT)		:KABOOM! :D Also, I think the current title is fine. It specifies clearly what it is talking about. However, it does conflict with the "TPOTS Sequence Prefixes" nomenclature (even though this is a minor point). Could that page be renamed to "Uru Sequence Prefixes", or is it really just for TPOTS?--[[User:Lyrositor\|Lyrositor]] 07:16, 17 May 2012 (EDT)
		+
		+	::Good catch. However, we should probably keep the redirect there since there is a whole bunch of external links to it, and the page is rather important. And it definitely is only about CC/TPOTS/UU ("old" Uru versions), the prefix space in MOUL is independent. For that reason, I renamed it to using "Uru:CC" as well (since almost nobody cares about UU anymore). -- [[User:Diafero\|Diafero]] 13:39, 17 May 2012 (EDT)

← Older revision		Revision as of 11:16, 17 May 2012
Line 4:		Line 4:

	[[User:Diafero\|Diafero]] 05:36, 17 May 2012 (EDT)		[[User:Diafero\|Diafero]] 05:36, 17 May 2012 (EDT)
		+
		+	:KABOOM! :D Also, I think the current title is fine. It specifies clearly what it is talking about. However, it does conflict with the "TPOTS Sequence Prefixes" nomenclature (even though this is a minor point). Could that page be renamed to "Uru Sequence Prefixes", or is it really just for TPOTS?--[[User:Lyrositor\|Lyrositor]] 07:16, 17 May 2012 (EDT)

← Older revision		Revision as of 11:13, 17 May 2012
Line 15:		Line 15:

	::::That sounds approximately like what I had in mind. Maybe "Setting up a minimal Shard" would be a more appropriate name. Then all it has to contain is "Look here and here, and make sure to use the setup without keys and fileserver". -- [[User:Diafero\|Diafero]] 05:34, 17 May 2012 (EDT)		::::That sounds approximately like what I had in mind. Maybe "Setting up a minimal Shard" would be a more appropriate name. Then all it has to contain is "Look here and here, and make sure to use the setup without keys and fileserver". -- [[User:Diafero\|Diafero]] 05:34, 17 May 2012 (EDT)
		+
		+	:::::Could that be a subsection under this article? You'd have "Minimal Shard Setup" and "Full Shard Setup". I'm trying to compact information to make it more accessible, and since the two subjects are extremely linked to each other... --[[User:Lyrositor\|Lyrositor]] 07:13, 17 May 2012 (EDT)

@@ Line 6: / Line 6: @@
 |colspan="2" style="font-style: italic; padding: 10px; text-indent: 10px;"|The [[Guild of Writers Wiki:About|Guild of Writers]] is a community of artists and programmers working to create or learn to use existing assets and [[:Category:Tools|tools]] for the open-source [[CyanWorlds.com Engine]]. It is a [[Guild of Writers Wiki:Contributions|collaborative community]], working toward the common goal of building new and exciting [[:Category:Ages|Ages]]. The Guild was formed on the basis of collaboration. We take great pride in our accomplishments and strive each day to create great things and outdo ourselves.
-The Guild as it stands today has evolved from a previous modding and Age creation groups. It is as diverse as the Uru community, and that diversity is one of its strengths.
+The Guild as it stands today has evolved from previous modding and Age creation groups. It is as diverse as the Uru community, and that diversity is one of its strengths.
 [[File:MainPageVothol.png|400px|center]]

@@ Line 3: / Line 3: @@
 Alcugs is one of the many possibilities how to run an Uru [[Shard]].
-The Alcugs source code is available at http://gitorious.org/alcugs/alcugs, it also contains all required documentation. The project had it's own wiki at http://alcugs.almlys.org/, today it serves as archive of Alcugs development.
+The Alcugs source code is available at http://gitorious.org/alcugs/alcugs, it also contains all required documentation. The project had it's own wiki at http://alcugs.almlys.org/ which today serves as archive of Alcugs development. The information there is outdated, please refer to the project repository instead.
 == Authors ==

← Older revision		Revision as of 09:34, 17 May 2012
Line 13:		Line 13:

	:::OK, I see your point. So here are my plans: 1. Specify '''clearly''' on [[DIRTSAND:Getting Started]] that the full File Server step is optional. 2. Add a subsection in File Server telling how to get your desired minimal setup (using <code>touch</code> and so on). 3. Specify that keygen isn't required in that section. 4. Specify that the server.ini encryption keys are optional. 5. Make "Setting Up a Shard" point to those two articles whilst specifying that some steps are optional beforehand. I think this should cover everything. What do you think? --[[User:Lyrositor\|Lyrositor]] 17:22, 16 May 2012 (EDT)		:::OK, I see your point. So here are my plans: 1. Specify '''clearly''' on [[DIRTSAND:Getting Started]] that the full File Server step is optional. 2. Add a subsection in File Server telling how to get your desired minimal setup (using <code>touch</code> and so on). 3. Specify that keygen isn't required in that section. 4. Specify that the server.ini encryption keys are optional. 5. Make "Setting Up a Shard" point to those two articles whilst specifying that some steps are optional beforehand. I think this should cover everything. What do you think? --[[User:Lyrositor\|Lyrositor]] 17:22, 16 May 2012 (EDT)
		+
		+	::::That sounds approximately like what I had in mind. Maybe "Setting up a minimal Shard" would be a more appropriate name. Then all it has to contain is "Look here and here, and make sure to use the setup without keys and fileserver". -- [[User:Diafero\|Diafero]] 05:34, 17 May 2012 (EDT)

← Older revision		Revision as of 22:16, 16 May 2012
Line 20:		Line 20:
	* [http://forum.guildofwriters.com/viewtopic.php?p=19778#p19778 Lesson 10: UV Mapping Part 1 - Basics]		* [http://forum.guildofwriters.com/viewtopic.php?p=19778#p19778 Lesson 10: UV Mapping Part 1 - Basics]
	* [http://forum.guildofwriters.com/viewtopic.php?p=20342#p20342 Lesson 11: UV Mapping Part 2 - Projections]		* [http://forum.guildofwriters.com/viewtopic.php?p=20342#p20342 Lesson 11: UV Mapping Part 2 - Projections]
−
−
−	~~[[Category:Archive]]~~

@@ Line 1: / Line 1: @@
-.fni files are files that go along with every Age that control its fog settings. They are placed in the /dat/ directory and are xTEA encrypted WhatDoYouSee files. Pretty much everything but the actual setting lines should be commented (with a #), but I believe the structure of them is pretty open.
+<code>.fni</code> files are files that go along with every Age. They control its fog settings. They are placed in the <code>dat</code> directory and are xTEA encrypted files. Pretty much everything but the actual setting lines should be commented (with a #), but otherwise the structure of them seems pretty open.
-==In Blender==
-Just as AlcScript settings are stored in the "AlcScript" text file in Blender, FNI settings are stored in the "init" text file. If you haven't already done so, open up a "Text Editor" panel in Blender (just as you would open another "3D View" or a "Buttons Window"). The traditional FNI settings are as follows.
+== Settings ==
-===Graphics.Renderer.SetYon===
+The traditional FNI settings are as follows.
-  Graphics.Renderer.SetYon ''Distance''
-This is the maximum distance that URU will render. Leaving it at the default value is usually fine.
+=== Rendering distance ===
-===Graphics.Renderer.Fog.SetDefLinear and Graphics.Renderer.Fog.SetDefExp2===
+  Graphics.Renderer.SetYon ''[distance]''
-  Graphics.Renderer.Fog.SetDef''(Linear or Exp2)'' ''Start End Density''
+This is the maximum distance that Uru will render. Leaving it at the default value is usually fine.
 These are the two types of fog. You must use one or the other, and not both. Exp2 only uses the "end" value, however, and is only used in Er'cana. It is not recommended for use anywhere else.
-===Graphics.Renderer.Fog.SetDefColor===
-  Graphics.Renderer.Fog.SetDefColor ''red green blue''
+=== Fog Color ===
 This sets the fog color with a traditional 0-1 RGB color.
-===Graphics.Renderer.SetClearColor===
-  Graphics.Renderer.SetClearColor ''red green blue''
+=== Clear Color ===
 This sets the onscreen color when there is nothing to display (which should never happen, but does when there's an error). A standard 0-1 RGB color.
 [[Category:Plasma]]

← Older revision		Revision as of 21:22, 16 May 2012
Line 11:		Line 11:

	::The emphasis of this article was the minimal amount of configuration needed to get a Shard running - without any dataserver or encryption. I don't see this on [[DIRTSAND:Getting Started]]. Parts of this tutorial I found in [[CWE:Getting Started]], so the section on setting up the CWE probably can be shortened, and the part about adding the Dirtsand user. However, the CWE guide also says you need to set up encryption in the server.ini, which is overkill for a local development Shard. I'm not touching anything for now since I am unsure which plans you have, or if you decide that nobody will be interested in such a minimal setup guide. --[[User:Diafero\|Diafero]] 12:23, 16 May 2012 (EDT)		::The emphasis of this article was the minimal amount of configuration needed to get a Shard running - without any dataserver or encryption. I don't see this on [[DIRTSAND:Getting Started]]. Parts of this tutorial I found in [[CWE:Getting Started]], so the section on setting up the CWE probably can be shortened, and the part about adding the Dirtsand user. However, the CWE guide also says you need to set up encryption in the server.ini, which is overkill for a local development Shard. I'm not touching anything for now since I am unsure which plans you have, or if you decide that nobody will be interested in such a minimal setup guide. --[[User:Diafero\|Diafero]] 12:23, 16 May 2012 (EDT)
		+
		+	:::OK, I see your point. So here are my plans: 1. Specify '''clearly''' on [[DIRTSAND:Getting Started]] that the full File Server step is optional. 2. Add a subsection in File Server telling how to get your desired minimal setup (using <code>touch</code> and so on). 3. Specify that keygen isn't required in that section. 4. Specify that the server.ini encryption keys are optional. 5. Make "Setting Up a Shard" point to those two articles whilst specifying that some steps are optional beforehand. I think this should cover everything. What do you think? --[[User:Lyrositor\|Lyrositor]] 17:22, 16 May 2012 (EDT)

@@ Line 5: / Line 5: @@
 *Windows 2000 or newer (also known to work in Linux using [http://www.winehq.org/ Wine])
 *[[Uru#Old Versions|Uru: Complete Chronicles]]
-**For Windows Vista and newer, please read the [[TPOTS_Installation|installation instructions]] carefully as incorrect installations quickly cause hard-to-find problems
+**For Windows Vista and newer, please read the [[Uru:CC Installation|installation instructions]] carefully as incorrect installations quickly cause hard-to-find problems
 *[[Offline KI]]
 *The ages

← Older revision		Revision as of 16:23, 16 May 2012
Line 9:		Line 9:

	:I can confirm this works for DIRTSAND at least. I'll be removing it from my CWE:Getting Started guide then (well, adding an optional statement). By the way, you don't mind if I delete this article? Its content has been replaced and updated by DIRTSAND:Getting Started, which also replaces Development:DIRTSAND. --[[User:Lyrositor\|Lyrositor]] 18:39, 15 May 2012 (EDT)		:I can confirm this works for DIRTSAND at least. I'll be removing it from my CWE:Getting Started guide then (well, adding an optional statement). By the way, you don't mind if I delete this article? Its content has been replaced and updated by DIRTSAND:Getting Started, which also replaces Development:DIRTSAND. --[[User:Lyrositor\|Lyrositor]] 18:39, 15 May 2012 (EDT)
		+
		+	::The emphasis of this article was the minimal amount of configuration needed to get a Shard running - without any dataserver or encryption. I don't see this on [[DIRTSAND:Getting Started]]. Parts of this tutorial I found in [[CWE:Getting Started]], so the section on setting up the CWE probably can be shortened, and the part about adding the Dirtsand user. However, the CWE guide also says you need to set up encryption in the server.ini, which is overkill for a local development Shard. I'm not touching anything for now since I am unsure which plans you have, or if you decide that nobody will be interested in such a minimal setup guide. --[[User:Diafero\|Diafero]] 12:23, 16 May 2012 (EDT)

@@ Line 1,161: / Line 1,161: @@
 |-
 |10583||???||ULM pre-registered||Corvus
 |-
 |10604||Mamert||Private Prison age for the D'ni Writer's of Illumination group.||GPNMilano
@@ Line 1,325: / Line 1,327: @@
 |-
 |13513||Venue|| ||pojibonzai
 |-
 |14314||???||Hello Relto...||Isle

@@ Line 1: / Line 1: @@
-=Software=
+This is a general task list for the various open-source projects currently underway at the GoW.
-==Client==
-* Branan's PlasmaClient is very WIP.
-** Currently supports linking though StartUp to Relto.
-** Has basic rendering and physics interactions.
-==Server==
-* Zrax has DirtSand, which is functioning at a basic (but very impressive) level at this point.
-* Dustin has one, which I haven't tested and can't comment on yet.
-==PyPRP2==
+== Software ==
-* Theoretically supports MOUL format. Should be verified and expanded on.
+These are the plans for the various software aspects of Uru (client, server, etc.).
-** What about the PhysX binary blob? Ignore because Branan's client won't read it anyway?
-*** That depends entirely on whether supporting Cyan's MOUL client is a design goal... which will probably depend on how communicative cyan becomes in the future.
-* What else does this need on top of current PyPRP to be a solid tool?
-** GUI access to all, or at last the most often used, features? Seems to be the PyPRP2 path anyway
-==File Server==
+=== Client ===
-* Where will we store age files? How will the server distribute them?
+* The [[Development:CyanWorlds.com Engine|H'uru fork]] of the [[CyanWorlds.com Engine]] is currently undergoing major development. Big projects include:
-=Assets=
+** Enabling cross-platform compatibility. This entails, among other things:
-It should be possible to create enough fan content to not have to include many Cyan assets. The big issue will be the global data. See below.
+*** Replacing DirectX with OpenGL support,
-* The KI is special. It's deeply integrated into the game, so we have to do *something* with it. Re-implementing the old Choru ki has been floated.
+=== Server ===
-==Global Data==
+* [[DIRTSAND]] is the server currently used by the GoW for deploying open-source Shards by the GoW (an alternative is MOSS by OpenUru).
-* CustomAvatars wouldn't be necessary on an all-fan-asset shard (except for any of our own, of course)
+* [[Wondruss]] is a work-in-progress server with additional functionality, set to replace DIRTSAND at some point.
 * GlobalAnimations has some things referenced in source code, much of it is only in assets (but those anims are useful for common things)
-* GlobalAvatars we're probably stuck with, unless we want to re-do all the necessary global anims in addition to creating new avatars
+=== PyPRP2 ===
 * GlobalClothing the only thing that should be required here is the default items. Everything else could likely be replaced.
 * GlobalMarkers is used for marker hunts. We could change the sounds and pictures stored here to customize markers. It's a small thing, though.
-=Documentation=
+=== Special Ages ===
-==Python Files==
+'''<code>Startup</code>''': Tweek once designed a [http://www.guildofwriters.org/tweek/uru-concepts-login-gui/ new Startup GUI]. Perhaps it should be implemented for this?
 * There are lots of x*.py files to implement common features. They should be doc'd with the correct parameters in a way artists can easily understand.
-* On the note of x*.py, it may be worth it to replace some of them with versions that do cleaner things (like vault SDL instead of gameserver)
+* On the note of x*.py, it may be worth it to replace some of them with versions that do cleaner things (like vault SDL instead of gameserver).
-==PyPRP2==
-=Community and Sustainability=
+=== Wiki ===
-==Donations==
+* All the tools need to be documented as new features are introduced. Work is currently underway to actualize the wiki.
 * Might be warranted/needed at some point
-==Information Sharing==
+== Community and Sustainability ==
-* Should be much more open than Cyan. This seems to be our general nature anyway, so shouldn't be hard ;)
+This is what needs to be done for the community and for the Guild.

← Older revision		Revision as of 02:46, 15 May 2012
Line 1:		Line 1:
−	{{Tutorial\|Details}}	+	{{Tutorial\|Details\|Max}}
	Details allow you to maintain a consistent quality of textures no matter the distance between an avatar and the object with this feature enabled.		Details allow you to maintain a consistent quality of textures no matter the distance between an avatar and the object with this feature enabled.

@@ Line 79: / Line 79: @@
 Make sure the path to the local file is specified using Windows folder separators (backslahes: "\"). The <code>bin/dsData.sh</code> script can automatically generate a manifest line for a specified file. The lines must reflect the details for the encrypted versions of the files.
-There is currently no official manifest generator for DIRTSAND. However, Lyrositor has provided a script for this purpose heavily based on branan's (a.k.a PaladinOfKaos) [https://github.com/branan/moulbuild-scripts script]. It is available for download here: [https://github.com/Lyros/GUM Generator of Uru Manifests]. You will need a reference installation containing the unencrypted <code>.pak</code file and <code>.sdl</code> files in <code>Python</code> and <code>SDL</code>, along with all the files from the <code>dat</code> and <code>sfx</code> folders from MO:ULa. On top of the <code>dat<code> folder, you should then copy the <code>dat</code> folder from moul-scripts to get the unencrypted versions. It requires Python 2.7 and [[libHSPlasma#Python|libHSPlasma for Python]].
+There is currently no official manifest generator for DIRTSAND. However, Lyrositor has provided a script for this purpose heavily based on branan's (a.k.a PaladinOfKaos) and Hoikas' [https://github.com/branan/moulbuild-scripts script]. It is available for download here: [https://github.com/Lyros/GUM Generator of Uru Manifests]. You will need a reference installation containing the unencrypted <code>.pak</code file and <code>.sdl</code> files in <code>Python</code> and <code>SDL</code>, along with all the files from the <code>dat</code> and <code>sfx</code> folders from MO:ULa. On top of the <code>dat<code> folder, you should then copy the <code>dat</code> folder from moul-scripts to get the unencrypted versions. It requires Python 2.7 and [[libHSPlasma#Python|libHSPlasma for Python]].
 '''Note on Python:''' the Python scripts need to be compressed into a <code>Python.pak</code> file. This can be achieved using the <code>plPythonPack.exe</code> tool obtained from compiling CWE (the tool only uses relative paths).

@@ Line 1: / Line 1: @@
-{{Stub}}
+The Guild of Writers maintains a number of software programs for use by Writers and Explorers. Development of such programs is one of two of the Guild's main branches of work (the other being [[Creating Ages|Age writing]]). This list of projects is by no means exhaustive, and any developer is free to start a new project under the Guild of Writers umbrella as long as it relates to the goals of the guild and its members:
-The Guild of Writers maintains a number of software programs for use by Writers and Explorers. This list is by no means exhaustive, and any developer is free to start a new project under the Guild of Writers umbrella as long as it relates to the goals of the guild and its members.
+# [[Development:CyanWorlds.com Engine|CyanWorlds.com Engine]]: the [[CyanWorlds.com Engine]] is the open-source version of [[Plasma]], released through [http://www.openuru.org OpenUru] and forked by the GoW.
+# [[Development:DIRTSAND|DIRTSAND]]: the D'ni in Real Time Server and Network Daemon is a server software for open-source MO:UL shards. It was created by [[User:Zrax|Zrax]].
-# [[Development:CyanWorlds.com Engine | CyanWorlds.com Engine]]
+# [[Development:PyPRP|PyPRP]]: the [[PyPRP]] plugin is an add-on for the [[Blender]] program used to create and publish Ages for [[Uru#Old Versions|old versions of Uru]].
-# [[Development:DirtSand | DirtSand]]
+# [[Development:Offline KI|Offline KI]]: the [[Offline KI]] brings new commands and various other additions to old versions of Uru.
-# [[Development:PyPRP | PyPRP]]
+The Guild of Writers uses Github for most of its projects; visit [[H'uru's repository list]] for more projects. Currently, efforts are mostly concentrated on the development of [https://github.com/H-uru/Plasma Plasma] and of the associated [https://github.com/H-uru/moul-scripts moul-scripts].
 # [[Development:Offline KI | Offline KI]]
-−
 [[Category:Projects]]

@@ Line 1: / Line 1: @@
-This page contains information about how to set up DirtSand, the "D'ni in Real-Time Server and Network Dæmon" by [[User:Zrax|Zrax]]. It is a server compatible with the [[CyanWorlds.com Engine]]. CWE needs a server to run at all, which makes setting up DirtSand (or a compatible server) a necessary part of any CWE setup. DirtSand currently works only on Linux operating systems.
+[[DIRTSAND]] is developed by H'uru on [https://github.com/H-uru/dirtsand Github]. If you wish to contribute, you can fork the repository and submit pull requests with your modifications. DIRTSAND is currently quite feature complete; unavailable features such as Heek are due to intentional design decisions.
-This tutorial assumes that you run the DirtSand server and the database it uses on the same machine, which will usually be the case. If you plan to use a dedicated database server, you probably know enough about Postgres and Linux do change the setup accordingly.
+'''Note:''' development of DIRTSAND is currently on indefinite hold as [[Development:Wondruss|development]] of [[Wondruss]] is underway, the latter being set to eventually replace DIRTSAND.
-==Git==
+== Building ==
-[https://github.com/H-uru/dirtsand DirtSand] uses [http://git-scm.com git] for its source control needs. If you're already familiar with git, some of these instructions may seem obvious to you. If you're not familiar with git, it is recommended that you read through some of the excellent articles in the [http://help.github.com/ GitHub help area].
+DIRTSAND can be built from source for Linux (and possibly other *nix) OSes. Follow the [[DIRTSAND:Getting Started|getting started guide]] to build DIRTSAND for your system. You'll need Git to fetch the sources.
-==Dependencies==
+== Contributing ==
-You will need to install some applications and libraries before you can build DirtSand. The package names in brackets are tested on Debian, they should be called similar on other distributions.
+== Roadmap ==
-* GCC 4.6+ (might work with other C++11 compliant compilers, but untested) [g++]
+[[Category:Development]][[Category:DIRTSAND]]
-* cmake [cmake]
-* Postgres, server and development libraries [postgresql, libpq-dev]
-* OpenSSL [libssl-dev]
-* libreadline [libreadline6-dev]
-* zlib [zlib1g-dev]
-* git (to get the sources) [git]
-−
-==Building the code==
-−
-This tutorial assumes you are setting up a small server to run on your main box, for testing. It installs DirtSand into a folder called "dirtsand" in your home directory. If you plan to run DirtSand on a public server, you should create a dedicated user for the Shard, so that it is properly isolated from the rest of your system, for example with the following commands run as root:
-<source lang="bash">adduser dirtsand # create user
-su dirtsand # and switch to it</source>
-−
-−
-Run the following commands to download, compile and install dirtsand:
-<source lang="bash">cd ~ # change to home directory (you can use any other folder as base directory, of course)
-mkdir dirtsand && cd dirtsand
-git clone git://github.com/H-uru/dirtsand.git src # download DirtSand into the src directory
-cd src
-mkdir build && cd build
-cmake .. -DCMAKE_INSTALL_PREFIX=$HOME/dirtsand # check for installed libraries etc.
-make # compile the server
-make install # copies the files to $HOME/dirtsand/bin etc.</source>
-−
-If you run into any errors about finding libraries or headers, make sure you have the *development* versions of all of the required libraries, and that they are in your path.  You can also use the cmake-gui to help cmake locate the missing paths and files.
-−
-You should not continue beyond this step before completing above commands without error messages!
-−
-==Setting up the server==
-−
-Now the database server needs to be set up and DirtSand needs to be configure to work with it. The subsections work on the database, so you need to run them as a user that can use the "sudo" command to switch to the postgres user. If you set up DirtSand on your home machine, your main user will usually be able to do that. On a server, you probably created a "dirtsand" user (see above) which should not have that power. Open a second terminal and log in as root for the following commands.
-−
-=== Set up the postgres user ===
-−
-<source lang="bash">sudo -u postgres psql</source>
-will open a postgres shell that you can type commands into. The following commands will create a user to be used by DirtSand (replace "<password>" by some random series of characters, and note it down - you will need it later):
- CREATE USER dirtsand WITH PASSWORD '<password>';
- CREATE DATABASE dirtsand WITH TEMPLATE = template0 ENCODING = 'UTF8';
- ALTER DATABASE dirtsand OWNER TO dirtsand;
- \q
-−
-=== Install the UUID functionality ===
-−
-This may be provided by your OS distribution.  In Ubuntu or Debian, simply install the postgresql-contrib package to provide the necessary libraries and installation scripts. Once the package is installed, you can import the functionality into the database (you may have to adapt the version number to your distribution):
-<source lang="bash">sudo -u postgres psql -d dirtsand < /usr/share/postgresql/8.4/contrib/uuid-ossp.sql</source>
-−
-−
-If your distribution does not provide a contrib or uuid-ossp bundle, you can get it and build it yourself from the sources provided at:  http://www.ossp.org/pkg/lib/uuid/. You can then add it to the dirtsand database by running:
-<source lang="bash">sudo -u postgres psql -d dirtsand < /path/to/uuid-ossp.sql</source>
-−
-=== Set up the dirtsand database ===
-−
-<source lang="bash">cd ~/dirtsand/src # if you switched the user, you may have to change this to the correct path
-sudo -u postgres psql -d dirtsand < db/dbinit.sql
-sudo -u postgres psql -d dirtsand < db/functions.sql</source>
-−
-If there were no other errors, your database should be ready for DirtSand. If you had to log in as root to run "sudo", exit that shell now, it is no longer necessary.
-−
-=== Configure dirtsand ===
-−
-A sample dirtsand.ini has been provided in the root of the dirtsand sources.  We can copy this to our install directory and then edit the fields we need. If you have dirtsand installed to somewhere other than /opt/dirtsand, you will also need to point the configuration to the right paths too.
-−
-<source lang="bash">cd ~/dirtsand
-sudo cp src/dirtsand.sample.ini dirtsand.ini
-<your-favorite-editor> dirtsand.ini</source>
-−
-First change the database settings - usually, the line containing "Db.Password" should be the only one you need to change. It must be set to the same random series of characters that you used when creating the user in postgres.
-−
-DirtSand also needs to know which ages it is going to host. To do that, look for the "Paths" section, and change the age and SDL paths (replace <user> by the name of the user you are working with):
- Sdl.Path = /home/<user>/dirtsand/SDL
- Age.Path = /home/<user>/dirtsand/ages
-Of course, the files also have to be put their. The complete set of age and SDL files for Uru is available [https://github.com/H-uru/moul-scripts/ in the moul-scripts repository], just download and extract them. You can remove the Python folder, and you have to rename "dat" to "ages" before moving it into the dirtsand directory.
-−
-To test if it all worked, you can now launch DirtSand with your settings file:
-<source lang="bash">bin/dirtsand dirtsand.ini # start the server
-ds-902> quit # and stop it again</source>
-If there is only a message saying something like "[Lobby] Running on 0.0.0.0/14617", followed by a bunch of warnings about the guild pubs, the database connection was successfully established and the vault initialized. Congratulations!
-−
-== Done! ==
-−
-That's it for the actual server setup. To complete this installation to a working Shard, check the [[Minimalistic Development Shard]] tutorial.

@@ Line 20: / Line 20: @@
 <source lang="bash">git clone git://github.com/H-uru/dirtsand.git dirtsand
 cd dirtsand</source>
-Once you have the sources, you'll need to run CMake and G++ to compile the code:
+You should now edit the <code>settings.h</code> file to change the build ID as follows, where ''BUILD_ID'' is the build ID of your client (by default this is the MO:ULa ID):
 <source lang="bash">mkdir build && cd build
 cmake -DCMAKE_INSTALL_PREFIX=/opt/dirtsand ..

← Older revision		Revision as of 22:39, 15 May 2012
Line 7:		Line 7:

	[[User:Diafero\|Diafero]] 13:46, 15 May 2012 (EDT)		[[User:Diafero\|Diafero]] 13:46, 15 May 2012 (EDT)
		+
		+	:I can confirm this works for DIRTSAND at least. I'll be removing it from my CWE:Getting Started guide then (well, adding an optional statement). By the way, you don't mind if I delete this article? Its content has been replaced and updated by DIRTSAND:Getting Started, which also replaces Development:DIRTSAND. --[[User:Lyrositor\|Lyrositor]] 18:39, 15 May 2012 (EDT)

@@ Line 18: / Line 18: @@
 * Once you've found someone, send them a PM asking if they're interested in joining your team.
 * Use the links provided to their Wiki page to learn more about them.
 {|class="wikitable sortable" style="margin-left:.6em;" border="1"
-! style="background: #CCCCCC; color:#000000;" |Name
+! Name
-! style="background: #CCCCCC; color:#000000;" |Concept Artist?
+! Concept Artist?
-! style="background: #CCCCCC; color:#000000;" |Layout Designer?
+! Layout Designer?
-! style="background: #CCCCCC; color:#000000;" |Story Writer?
+! Story Writer?
-! style="background: #CCCCCC; color:#000000;" |Coder?
+! Coder?
-! style="background: #CCCCCC; color:#000000;" |Modeler?
+! Modeler?
-! style="background: #CCCCCC; color:#000000;" |Texture Artist?
+! Texture Artist?
-! style="background: #CCCCCC; color:#000000;" |Sound Effects Artist?
+! Sound Effects Artist?
-! style="background: #CCCCCC; color:#000000;" |Musician?
+! Musician?
-! style="background: #CCCCCC; color:#000000;" |Available?
+! Available?
 |-
 |[[User:Paradox|Paradox]]||No||No||No||Yes||Yes||No||No||No||No
@@ Line 217: / Line 216: @@
 |-
 |[[User:pojibonzai|pojibonzai]]||No||No||No||No||No||No||Yes||Yes||Yes
+|}
 [[Category:Age Projects]]

@@ Line 1: / Line 1: @@
-{{Stub}}{{InfoTool
+{{InfoTool
 |Name=3ds Max
 |Image=3dsMaxLogo.png
@@ Line 15: / Line 15: @@
 == Max Plugin ==
-After installing 3ds Max, you should be ready to [[Max:Introduction|get started with the 3ds Max plugin]], an open-source plugin created by Cyan to develop Ages for [[Uru#Current Version: MO:UL|MO:UL]].
+After installing 3ds Max, you should be ready to [[Max Plugin|get started with the 3ds Max plugin]], an open-source plugin created by Cyan to develop Ages for [[Uru#Current Version: MO:UL|MO:UL]]. Current, the Max Plugin is the only way to publish Ages for MO:UL, as [[PyPRP:Changelog#PyPRP2|PyPRP2]] is still quite incomplete. To install it on top of your Max installation, talke a look at the [[Max:Installing|installation instructions]].
 === Tutorials ===

@@ Line 3: / Line 3: @@
 |colspan="2"|<h2>{{{Name}}}</h2>
 |-
-|colspan="2"|[[File:{{{Image}}}|200px]]
+|colspan="2"|[[File:{{{Image}}}|120px]]
 |-
 |'''Category'''

@@ Line 1: / Line 1: @@
 This tutorial will help you set up your own fully-functional [[shard]] using [[DIRTSAND]], a server software for [[MO:UL]] clients by H'uru.
@@ Line 13: / Line 14: @@
 Finally, it is recommended that you create a UNIX user to run DIRTSAND with an associated home directory containing DIRTSAND:
- sudo useradd dirtsand -d /opt/dirtsand -m -p <password> -s /bin/bash
+<source lang="bash">sudo useradd dirtsand -d /opt/dirtsand -m -p <password> -s /bin/bash</source>
 == Compiling ==
 The first step is to download and compile DIRTSAND for your system; make sure you have all the appropriate libraries installed. First, clone the H'uru repository:
- git clone git://github.com/H-uru/dirtsand.git dirtsand
+<source lang="bash">git clone git://github.com/H-uru/dirtsand.git dirtsand
- cd dirtsand
+cd dirtsand</source>
 Once you have the sources, you'll need to run CMake and G++ to compile the code:
- mkdir build && cd build
+<source lang="bash">mkdir build && cd build
- cmake -DCMAKE_INSTALL_PREFIX=/opt/dirtsand ..
+cmake -DCMAKE_INSTALL_PREFIX=/opt/dirtsand ..
- make && sudo make install
+make && sudo make install
- cd ..
+cd ..</source>
 If your system complains about missing libraries but you have installed them, you can use the CMake GUI to point to the libraries' location.
 == Database Setup ==
 You will need a PostgreSQL server which DIRTSAND can access with a user capable of adding schemas, tables, etc. into. For the proposed installation here, a <code>dirtsand</code> database with ownership set to a <code>dirtsand</code> user (such as the one created beforehand in this tutorial).
- sudo -u postgres psql -d template1
+<source lang="bash">sudo -u postgres psql -d template1</source>
   template1=# CREATE USER dirtsand WITH PASSWORD '<password>';
   template1=# CREATE DATABASE dirtsand WITH TEMPLATE = template0 ENCODING = 'UTF8';
@@ Line 34: / Line 36: @@
   template1=# \q
 The next step is to enable UUID functionnality for PostgreSQL. The technique for this varies depending on PostgreSQL's version. Until PostgreSQL 9.1, the extension had to be manually loaded into PostgreSQL:
- sudo -u postgres psql -d dirtsand < /path/to/uuid-ossp.sql
+<source lang="bash">sudo -u postgres psql -d dirtsand < /path/to/uuid-ossp.sql</source>
 In Ubuntu with PostgreSQL 8.4, for example, the path is <code>/usr/share/postgresql/8.4/contrib/uuid-ossp.sql</code>.
-From 9.1 and onwards, you need to make sure the <code>postgresql-contrib</code> package is installed (the name will vary depending on your distribution) then load the extension:
+From 9.1 and onwards, you need to make sure the <code>postgresql-contrib</code> package is installed (the name will vary depending on your distribution) then load the extension from within psql:
- psql
   CREATE EXTENSION "uuid-ossp";
 Now you need to load the initial structure for your DB, the SQL files being available in DIRTSAND's source code:
- sudo -u postgres psql -d dirtsand < db/dbinit.sql
+<source lang="bash">sudo -u postgres psql -d dirtsand < db/dbinit.sql
- sudo -u postgres psql -d dirtsand < db/functions.sql
+sudo -u postgres psql -d dirtsand < db/functions.sql</source>
 Your database should now be ready.
 == Configuring ==
 DIRTSAND is configured from a <code>dirtsand.ini</code> file placed in the execution directory for DIRTSAND. It needs to be adjusted to connect to your database, to have all the appropriate RC4 keys, which DIRTSAND can automatically generate for you:
- bin/dirtsand
+<source lang="bash">bin/dirtsand
- ds-902> keygen new
+ds-902> keygen new
- ds-902> quit
+ds-902> quit</source>
 After running for a bit, this will output six keys to be copied into your <code>dirtsand.ini</code> file and six others into your client's <code>server.ini</code> (this requires either PlasmaClient or the H'uru fork of [[CWE]]). You can safely ignore all startup errors. A sample file for <code>dirtsand.ini</code> has been placed in the source directory; you need to fill it in with your keys and database details (and any other configuration details you need to fill in):
- sudo cp dirtsand.sample.ini /opt/dirtsand/dirtsand.ini
+<source lang="bash">sudo cp dirtsand.sample.ini /opt/dirtsand/dirtsand.ini
- sudo chown dirtsand /opt/dirtsand/dirtsand.ini
+sudo chown dirtsand /opt/dirtsand/dirtsand.ini
- su - dirtsand
+su - dirtsand
- nano dirtsand.ini
+nano dirtsand.ini</source>
 Replace the dummy values with the output under "Server keys".
@@ Line 82: / Line 83: @@
 == Running ==
 If all went well, you can now start your server:
- bin/dirtsand dirtsand.ini
+<source lang="bash">bin/dirtsand dirtsand.ini</source>
 And that's it. You will obtain an interactive terminal to operate DIRTSAND which will output log messages as they are printed. You might find it useful however to start DIRTSAND in a GNU screen/Byobu or X session.

@@ Line 63: / Line 63: @@
 === Setting Up ===
 The process for setting up your External client is the same as for an Internal client. The only difference is in the execution: you cannot run an External client in "-LocalData" mode, and starting <code>UruExplorer.exe</code> (<code>plClient.exe</code>'s equivalent) will force you to use <code>UruLauncher.exe</code>. The External client will thus always use the latest files as provided by the server.
 [[Category:CWE]]

← Older revision		Revision as of 02:12, 15 May 2012
Line 1:		Line 1:
−	#REDIRECT [[~~CWE~~]]	+	#REDIRECT [[CyanWorlds.com Engine]]

@@ Line 1: / Line 1: @@
-This is an article detailing new KI features being discussed on the GoW and MOULa forums. All suggested commands can be disabled by reentering the command again unless otherwise specified.
+This is an article detailing new KI features being discussed on the GoW and MO:ULa forums. All suggested commands can be disabled by reentering the command again unless otherwise specified.
 {|class="wikitable" border="1"
-! style="background: #CCCCCC; color:#000000; width:300px" |Command Name
+! style="width:300px" |Command Name
-! style="background: #CCCCCC; color:#000000; width:100px" |Suggested By
+! style="width:100px" |Suggested By
-! style="background: #CCCCCC; color:#000000; width:100px" |Development Status
+! style="width:100px" |Development Status
-! style="background: #CCCCCC; color:#000000; width:500px" |Proposed Usage
+! style="width:500px" |Proposed Usage
 |-
 | /ignore + /shun || Gahlen and Adam (Hoikas) [http://mystonline.com/forums/viewtopic.php?t=25268][http://forum.guildofwriters.org/viewtopic.php?f=114&t=5469] || Complete; Waiting for testing [http://forum.guildofwriters.org/viewtopic.php?p=56145#p56145] || The original ignore function for the KI, created by Cyan Worlds; with the new added functionality of one way invisibility and a KI toggle (/shun) for "mutual invisibility." (Two way invisibility)
@@ Line 16: / Line 18: @@
 |}
-== http://mystonline.com/forums/viewtopic.php?t=25268 ==
+Discussion about ignore function: http://mystonline.com/forums/viewtopic.php?t=25268
 '''Common Annoyances and Bugs'''
 {|class="wikitable" border="1"
-! style="background: #CCCCCC; color:#000000; width:300px" |Name
+! style="width:300px" |Name
-! style="background: #CCCCCC; color:#000000; width:100px" |Reported by
+! style="width:100px" |Reported by
-! style="background: #CCCCCC; color:#000000; width:100px" |Status
+! style="width:100px" |Status
-! style="background: #CCCCCC; color:#000000; width:500px" |Description
+! style="width:500px" |Description
 |-
+|
 |}
-Note: A copy of this page can be found on the OpenUru wiki here: [http://wiki.openuru.org/index.php?title=KI_-_New_Feature_Log]
+Note: A copy of this page can be found on the OpenUru wiki [http://wiki.openuru.org/index.php?title=KI_-_New_Feature_Log here].

@@ Line 1: / Line 1: @@
-{{Stub}}
+{{Stub}}{{InfoTool
-== 3ds Max ==
+== Obtaining Max ==
-[http://usa.autodesk.com/3ds-max/ '''3ds Max'''] is a commercial, closed source 3D modelling utility developed by [http://www.autodesk.com Autodesk]. It is used by game development studios worldwide, including [[Cyan Worlds]].
+Max is a high-priced commercial product produced by Autodesk.
-== Getting 3ds Max ==
+'''Students:''' Autodesk offers free academic versions of 3ds Max and a variety of other software for [http://students.autodesk.com/ students and educators].
-ds Max is [http://usa.autodesk.com/3ds-max/trial/ free to try for 30 days], after which you must [http://usa.autodesk.com/3ds-max/how-to-buy/ purchase a license] in order to continue using the program. Autodesk offers free academic versions of 3ds Max and a variety of other software for [http://students.autodesk.com/ students and educators].
-== Getting Started with 3ds Max ==
+'''Everyone else:''' 3ds Max is [http://usa.autodesk.com/3ds-max/trial/ free to try for 30 days], after which you must [http://usa.autodesk.com/3ds-max/how-to-buy/ purchase a license] in order to continue using the program.
-After installing 3ds Max, you should be ready to [[Max:Introduction|get started with the 3ds Max plugin]], after which you can check the list of available [[:Category:3ds Max Tutorials|3ds Max Tutorials]]. For general assistance, [http://www.google.com/search?q=3ds+Max+Tutorials Google is your friend].
 [[Category:3ds Max]]

@@ Line 1: / Line 1: @@
 What follows is a complete list of all the available tutorials on this wiki.
-== 3DS Max ==
+== 3ds Max ==
 These tutorials cover the use of Cyan Worlds Plasma Plugin for 3D Studio Max. It is assumed you are familiar with 3DS Max before using these.