XelaG Quality Bots

The xelagot bot family has the ability to log into a xelagot server, allowing bots to communicate remotely with each other and with their owners using their built-in clients. Each xelagot application has, besides this client software, a built-in xelagot server unit.

The Xelagot Server on this page is a stand-alone version of the built-in server. It is faster and does not interfere with or slow down bot activity. It comes in two editions: a GUI (graphic user interface) application, and a Windows NT4 or 2000 Service application.

To maintain the server remotely, this package includes a Xelagot Administrator Client application. An administrator can log into the server and add, delete or change the data of the Server's client database. It also enables the Administrator to request the clients to log off or to log back in, and to expel clients. The Administrator must be registered in the Server's database as ADMINISTRATOR to be able to use this application.

A feature requested by bot-hosting instances: the Xelagot User Client. This application allows bot owners, who's bots are hosted elsewhere, to communicate remotely with their xelagots, using the bot's verbal command set. The bot owner must be registered in the Server's database as USER to be able to use this application.

Installation. (GUI edition) Unzip xlgserver.zip into a new folder and run XlgServer.exe. You will see on the Clients tab an entry - Client: Number One, Protocol: Administrator. Right-click on that entry, and select 'edit client'. Enter a password (don't use spaces or punctuation marks in the password) to make sure no-one else uses this name to login, and click 'accept'. You may now use this login name to access the server remotely as Administrator (see the section on The Xelagot Administrator Client). Turn to the Settings tab, select a port number and enter it in it's box. Some port numbers are reserved for special services, try using a higher number: I use myself numbers in the 9000 range. You can then test the connection: return to the Clients tab to see any error messages, and hit 'connect'. If everything goes right, you will see in the status bar (bottom of the screen): Listening on port xxxxx, connection(s) 0, logged in 0. You do not need to change the other values, except for 'Connect on start': checkmark this box if you want the server to always connect when the program starts.

Installation. (NT Service edition) Unzip srvcxlgserver.zip into a new folder. To install the service, open a dos console (on NT, hit Start > Run, and type 'cmd' (without quotes). Using dos commands, go to the folder where SrvcXlgServer.exe resides, and type: SrvcXlgServer.exe /install. Close the dos console, then go to the Control panel: Start > Settings > Control Panel. (NT4) Double-click on the Services icon. (Widows 2000) Double-click on the Administrative Tools icon, and then on the Services icon. Check that the Xelagot Server has been installed. Start the service (Windows 2000: right click on Xelagot Server, chose Start): this creates the necessary ini file. Now stop the service, to be able to adjust the settings in the ini file that has just been created. Close the Services screen. Go to the server's folder, and open the file XlgServer.ini with Notepad (NOT Wordpad) or another ascii text-processor, enter the appropriate port number (Replace the 0 in Port=0 by the port number of your choice), make sure ConnectOnStart=1, and close the ini file. You now need to start the service as noted above but, before doing so, you have to install the Xelagot Administrator Client (see below) to edit the Server database and secure that no one can use the default Adminitrator login 'Administrator' (no password when you first log in).
Note for the NT Service edition: If you wish to start the service automatically when Windows starts up, adjust the settings (Windows 2000: in the Services screen, right-click on Xelagot Server, chose Properties, put the Start-up type to automatic). To uninstall the service, make sure it is not running (Services screen as above, check there and if necessary, stop the service of the Xelagot Server, then close the Services screen - this is important). Next, open the dos console, go to the application's directory and type: SrvcXlgServer.exe /uninstall

Read the next section on the Xelagot Administrator Client to learn how to remotly manage the Server's client database.

The Server's client database. This database, part of which is visible on the Clients tab as a list, manages two issues: (1) who is allowed to log into the server and (2) what they are allowed to do (the protocol). Clients log in (if they know the server's ip or host name, and it's port) using a Login name and a password. You can add names, passwords and protocols to the database (and for bot owners with a 'user' protocol, you can specify their bots as 'user bots'): right-click on the list, chose 'add client', fill in the data and click 'accept'. Passwords may not contain spaces, all entries must contain only letters, numbers or some other symbols, except quotes, double quotes, commas, colons, semi-colons, slashes and other punctuation marks. Protocols are of 4 kinds:

• bot
  used by xelagot bots with limited functions: these may only communicate through the scripts, they have no access to the 'writetobot' functions nor to verbal commands to manipulate other bots (they can answer freely to verbal commands, but may not issue them).
• master
  used by xelagot bots with extended access function: they have access to all functions of fellow bots.
• administrator
  for people authorised to administrate the server.
• user
  used by bot owners who wish to talk to their bots: their bot's login names must be filled into the appropriate box (user bots) for a user to have access to them. These bot owners may use the Xelagot User Client to talk to their bots using verbal commands or commands understood by scripts.

For a typical example, check this link.

Bots have 2 protocols they can chose from (or better said, the Server Administrators chose them): bot and master.

Bot protocol gives bots access to each other through the server if they are runing scripts, but they may not issue any WriteToBot commands nor chat using Verbal commands. This means that both bots communicating through the server must be running compatible scripts. They may, however, answer to a Chat command from another bot or person. See for more details the Action Script section in the Xelagot help pages.

Master protocol enables a bot to use all available commands to communicate with all other bots logged into the Xelagot Server. Normally, these commands will be issued by a Master bot running a script, but they can be faked by a person (legally) using the bot application's Central Client, if the Central Client logs into the server using a Master account (i.e. and account that has Master protocol). Note: previous versions require a double protocol: bot,master. This has now been changed to a single protocol: master.

How do bots log in? There are various methods a bot can use, you can find an overview following this link.

See the Xelagot help pages for more details :)

I, XelaG (Alex Grigny de Castro), have done my best to insure that original versions of my software are of good quality. Nevertheless, I accept no responsibility for any damages the use of my software could inflict. If you object to this attitude, do not download or use my software.

All the software on this page is freeware and remains my intellectual property. You are free to distribute it and use it, provided no alterations are made to the program code or copyright notices. You may not de-compile or reverse-engineer this software.

This software was written using Delphi 5 Object Pascal (copyright Inprise Corporation), and runs on Windows 98, Windows NT4 and Windows 2000. It should also run on Windows ME, but has not been tested. The clients may not run properly on Windows 95.

November 14th, 2000 - XlgServer.exe and SrvcXlgServer.exe 1.2: memory leak bug fixed.

November 12th, 2000 - ClientU version 1.2 accepts messages from bot scripts (written with Reply or CLWrite).

November 1st, 2000 - Version 1.1 has a few enhancements and bug-fixes. The NT service server was maxing the CPU: fixed. When the Administration Client modifies data of a client while the client is online, the client is now requested to log back in (automatically): updates are propagated to all clients in this way. Please note that if changes are made to the server directly using the server's GUI, updates may not be propagated properly to clients.

End October, 2000 - Version 1.0 available of XlgServer, SrvcXlgServer, XlgClientA and XlgClientU.