Server.txt - Revision history

Batlin: Protected "Server.txt" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

2009-06-23T18:48:05Z

Protected "Server.txt" ([edit=autoconfirmed] (indefinite) [move=autoconfirmed] (indefinite))

Batlin at 12:35, 22 May 2009

2009-05-22T12:35:37Z

Batlin: Created page with ''''Server.txt''' is an important file and resides in the uogolddemo directory. It's the very first file the demo open and parses. It is a text file and each line should hav...'

2009-05-22T12:23:19Z

Created page with ''''Server.txt''' is an important file and resides in the uogolddemo directory. It's the very first file the demo open and parses. It is a text file and each line should hav...'

New page

'''Server.txt''' is an important file and resides in the [[uogolddemo]] directory. It's the very first file the demo open and parses.

It is a text file and each line should have the following structure :
<VARIABLE VALUE>

This is a list of supported string variables : name.
This is a list of supported integer variables : id, port, width, height, x, y, startx, starty, spawnclient.
This is a list of supported R/W variables : statics, terrain, art, tiledata, hues, animdata, resources, templates

R/W variables are checked to be either "w" or "W", any other value defaults to non-W, this most probably indicates they allow for enabling of disabling the writing of certain data.

The value of some variables seem to be unused and they could be indication of how the official OSI server worked internally, for example : name, id and port.

The variable "spawnclient" is mysterious one, if this variable is not in '''server.txt''' it will default to value "1". If its value is non-zero, then the uodemo will create a thread to run the client in. If its value is zero the server code keeps running but this has no effect at all since the actual client is not running. In this case the only way to terminate the uodemo is by closing it with the Windows Task Manager [http://en.wikipedia.org/wiki/Windows_Task_Manager]. This variable was probably used by OSI during the development of the UO Gold Demo.

← Older revision	Revision as of 18:48, 23 June 2009
(No difference)

@@ Line 2: / Line 2: @@
 It is a text file and each line should have the following structure :
-<VARIABLE VALUE>
+<VARIABLE VALUE>.
-This is a list of supported string variables : name.
+This is a list of supported ''string'' variables : '''name'''.<br>
-This is a list of supported integer variables : id, port, width, height, x, y, startx, starty, spawnclient.
+This is a list of supported ''integer'' variables : '''id''', '''port''', '''width''', '''height''', '''x''', '''y''', '''startx''', '''starty''', '''spawnclient'''.<br>
-This is a list of supported R/W variables : statics, terrain, art, tiledata, hues, animdata, resources, templates
+This is a list of supported ''R/W'' variables : '''animdata''', '''art''', '''hues''', '''statics''', '''templates''', '''terrain''', '''resources''', '''tiledata'''
 R/W variables are checked to be either "w" or "W", any other value defaults to non-W, this most probably indicates they allow for enabling of disabling the writing of certain data.
-The value of some variables seem to be unused and they could be indication of how the official OSI server worked internally, for example : name, id and port.
+Some variables seem to be unsued in the demo and they could be indication of how the official OSI server worked internally, for example : name, id and port.
 The variable "spawnclient" is mysterious one, if this variable is not in '''server.txt''' it will default to value "1".  If its value is non-zero, then the uodemo will create a thread to run the client in.  If its value is zero the server code keeps running but this has no effect at all since the actual client is not running.  In this case the only way to terminate the uodemo is by closing it with the Windows Task Manager [http://en.wikipedia.org/wiki/Windows_Task_Manager].  This variable was probably used by OSI during the development of the UO Gold Demo.