RunningOnWindows - Trench-Wars/twcore GitHub Wiki

TracNav(Index) TOC

Prior warning: I must admit that the bots that come with TWCore aren't the best to be applied to any zone, most of them are quite specific for Trench Wars. However, the TWCore Core is a good basis for hosting and creating new bots on.

'''This guide describes and helps you to setup TWCore to run in your zone. If you want to develop bots for TWCore, see the [wiki:Programming Programming] guide.'''

The following steps are described:

  1. [#Prerequisites Prerequisites]
  2. [#DownloadingTwcore Downloading TWCore]
  3. [#BuildingTWCore Building TWCore]
  4. [#Configuration Configuration]
  5. [#Readytorun Ready to run]

Directory structure The following directory structure is recommended and used throughout this guide:

| C:\Subspace | | | C:\Subspace\bin | | | C:\Subspace\bin\ant | Ant installation | | C:\Subspace\bin\svnkit | SVNKit installation | | C:\Subspace\bin\twcore | TWCore main directory | | C:\Subspace\bin\twcore\bin | TWCore binary and configuration files | | C:\Subspace\bin\twcore\src | TWCore source export from repository |

Problems while following this guide? Ask your question at the [/discussion forum]!

Prerequisites

There are some things you need to have for running TWCore:

  1. Java Development Kit (JDK) Install to a directory of your choice.

  2. Ant (Download Current Release of Ant, .zip archive) Extract to a directory of your choice. However, it's recommended to extract to a subdirectory close your twcore directory. For example, C:\subspace\bin\ant . Make sure you don't extract a new directory apache-ant-1.7.0 inside the binant directory but directly into the \bin\ant directory.

  3. SVNKit (Download the Latest Stable Version'', ''Standalone Version) Extract to a directory of your choice. However, it's recommended to extract to a subdirectory close your twcore directory. For example, C:\subspace\bin\svnkit . Make sure you don't extract a new directory svnkit-1.1.4 inside the binsvnkit directory but directly into the \bin\svnkit directory.

  4. (Access to) a Subspace zone

Optional:

  1. (Access to) a MySQL database

Java check
Once you have java installed, make sure you can run java from the command prompt. To test/setup, follow these steps:

  1. Click Start
  2. Click Run...
  3. Type 'cmd' in the text field and press Enter or click OK.
  4. Type 'java -version' [ENTER]
  5. If you see
    'java' is not recognized as an internal or external command, operable program or batch file.
    then you need to set the PATH to the location of your installed Java version. a. Find where you've installed Java and copy the complete path of the bin directory a. Go to your System Properties (via Control Panel) a. Go to the Advanced tab a. Click on the 'Environment Variables' button a. Find the 'Path' variable in the 'System variables' section a. Click on 'Edit' a. In the 'Variable value' text field append an ';' and paste the path of your Java\bin location. For example; C:\Program Files\Java\jdk1.6.0_03\bin a. Click the OK button 3 times and try the above again.
  6. Type ECHO %JAVA_HOME%
  7. If you see
    %JAVA_HOME% then you need to setup this variable aswell: a. Find where you've installed Java and copy the complete path of the directory a. Go to your System Properties (via Control Panel) a. Go to the Advanced tab a. Click on the 'Environment Variables' button a. Click the Create button in the 'System variables' section Name: JAVA_HOME Value: Complete path to the Java installation directory. For example; C:\Program Files\Java\jdk1.6.0_03 a. Click the OK button 3 times and try the above again.

Downloading TWCore

In this step you will export the most recent TWCore version from the repository of twcore.org .

  1. [attachment:update.bat?format=raw Download update.bat] and save it in the directory C:\subspace with the name update.bat.
  2. Execute this batch file by double clicking it When asked for an username/password, use the TWCore.org username and password. Note that this username and password is saved.
  3. If all goes well you should see the following output when the execution has finished: Image(update.gif)

You can always update TWCore safely as it doesn't affect any running / binary files nor your configuration files.

Building TWCore

Before you can use and configure TWCore, it needs to be built.

  1. [attachment:build.bat?format=raw Download build.bat] and save it in the directory C:\subspace with the name build.bat.
  2. Execute this batch file by double clicking it
  3. If all goes well you should see the following output when the execution has finished: Image(build.gif)

Note for building TWCore, TWCore must be turned off completely! Your configuration files will not be touched during the build process.

Configuration

Go into the C:\subspace\twcore\bin folder with explorer and configure the configuration files:

  1. Rename setup.example.cfg to setup.cfg
  2. Open setup.cfg and fill in the settings:
  • [Server]
  • Server should be set to the IP of the Subspace server you are connecting to
  • Port should be set to the port of the Subspace server you are connecting to
  • [Login Information]
  • Main Login the name of the Continuum account for the TWCore Hubbot.
  • Main Password the password of the Continuum account for the TWCore Hubbot.
  • Sysop Password the sysop password for the zone you are connecting to.
  • [Chat Names]
  • Chat Name the default chat name of any bots that require it. Usually this is used to set to a chat used by the TWCore developers.
  • Staff Chat the chat name of the staff chat.
  • Smod Chat the chat of the smod/upper staff chat.
  • [Debugging]
  • DebugOutput Set DebugOutput to 0 to turn stack traces off, 1 to turn them on. Stack traces are useful for debugging bots.
  • [Directories]
  • Core Location Set this to the exact location where this setup.cfg is located. Do not end this with a slash. For example: C:\Subspace\TWCore (Windows) or /home/bots/twcore (Linux).
  • [Logging]
  • Exception Log Set the file and path of the exception log. This log will contain any exceptions the bot runs into. For example: C:\Subspace\TWCore\exception.log or /home/bots/twcore/exception.log
  • LogPrivateMessages Set LogPrivateMessages to 1 to have each bot record private messages in the /logs folder.
  1. Rename all the files in the corecfg directory to .cfg. For example: autoload.cfg and sql.cfg. Small description of each configuration file:
  • autoload.cfg All the bots in this file will be automatically spawned when TWCore is started and connected to the Subspace server.
  • operators.cfg This file provides startup permissions for specified users and defines how the bot auto-assigns privileges.
  • racism.cfg This file is a list of fragments that will be flagged by racism detection.
  • sql.cfg This file contains the settings for working with a database. If you do not (want to) use a database, set ConnectionCount to 0. For more information, see below.
  1. [Optional] Configure sql.cfg:
  • [General]
  • RetryCount Amount of retries a connection is tried before it will be given up
  • ConnectionCount Number of connections defined in this file and/or number of connections that are used.
  • [Connection X] (Replace X for a number starting with 1, also with settings below)
  • NameX Name of the connection. This same name is also used by the bots. The connection names used by the bots that come with TWCore are local, website and server.
  • DriverX Name of the sql driver. This is usually set to com.mysql.jdbc.Driver which you don't need to change unless you want to work with a different type database then MySQL.
  • LoginX The username used for connecting to the database server.
  • PasswordX The password used for connecting to the database server.
  • DataBaseX The database name that should be used. Make sure this database already exist on the server.
  • ServerX
    The IP or the address of the database server. If the database is on the same machine, set it to localhost. If the database is not on this machine, make sure you have the database server configured that it allows external connections.
  • PortX
    The port used to communicating with the database server. If you are using a MySQL server then you can leave it set to 3306.
  • MinPoolSizeX
    The minimum number of connections required to be in the pool. You can leave the default set to 1.
  • MaxPoolSizeX The maximum number of connections of the connection pool. You can leave the default set to 10.
  • WaitIfBusyX Wait if the connection is busy. Can be set to 0 or 1.
    You can create several connections in this file, you only need to change the X in each setting to the respective connection number.

Ready to run

If you have configured everything then you should be all set!

  1. [attachment:run.bat?format=raw Download run.bat] and save it in the C:\subspace folder.
  2. Double click run.bat to start TWCore
  3. The bot with the name you configured in setup.cfg will now enter your zone. This is the HubBot, it can spawn other bots on your command.

Spawning bots

In TWCore we have two names for a specific bot; the bot type and the bot name.
The bot type is the name of the directory. The main .java and .cfg file within this directory both have the same name as the bot type. You use this bot type to specify which bot to spawn. The bot name is the name you configure inside the .cfg file.

To spawn a bot follow the following steps:

  1. The first time you spawn a bot you have to rename its .example.cfg file to .cfg. For example, multibot.example.cfg to multibot.cfg.
  2. Open the .cfg file (with notepad for example) and set the correct values. This usually consists of configuring the name, password and initial arena.
  3. Start up TWCore if you haven't already
  4. PM !spawn <bottype> to your HubBot.
  5. If the bot doesn't spawn into your zone, check the TWCore console for error messages.

Problems while following this guide? Ask your question at the [/discussion forum]!

⚠️ **GitHub.com Fallback** ⚠️