Topics

[Update:]

Update:

• Since version 6.0 the Hosting Edition of the JTS3ServerMod needs a licence key. You can find more information at the download link.
• Seit der Version 6.0 benötigt die Hosting Edition vom JTS3ServerMod einen Lizenzschlüssel. Weitere Informationen sind beim Download Link zu finden.

*** English ***
Today I got the information and a proof, that the current JTS3ServerMod Hosting Edition from 27. December 2015 was released in an illegal underground board. Everyone knows that this is not allowed!

Now there are two possibilities:

• The person who did this, write a private message or e-mail to me. Nothing will happen to other users.
• If no one sends me a message in the next 7 days, I remove the access to the Hosting Edition (and forum) from all persons who downloaded the Hosting Editions since the 27. December 2015 and 7. January 2016. All affected persons can request a personal Hosting Edition version, which is trackable for me!

I don't like this, but I hate to get pranked!



*** Deutsch ***
Heute habe ich Informationen und einen Beweis erhalten, dass die JTS3ServerMod Hosting Edition vom 27. Dezember 2015 in einem illegalen Untergrund Board herunterladbar ist. Jeder hier weiß, dass dies nicht erlaubt ist.

Nun gibt es zwei Möglichkeiten:

• Die Person, die dafür verantwortlich ist, meldet sich bei mir (Privatnachricht oder E-Mail). Dann passiert mit allen anderen Anwendern nichts.
• Wenn ich keine Rückmeldung hierzu in den nächsten 7 Tagen erhalte, werde ich allen Personen den Zugriff zum Forum und der Hosting Edition sperren, die diesen zwischen dem 27. Dezember 2015 und dem 7. Januar 2016 heruntergeladen haben. Alle betroffene Personen können dann eine personalisierte Hosting Edition bei mir anfordern, die für mich zurück verfolgbar ist.

I mag diesen Schritt nicht, aber ich hasse es verarscht zu werden!

Meine Webseite nutzt nun seit 30 Stunden eine mit HTTPS gesicherte Verbindung. Beim Besuch des Forums wird die HTTPS Verbindung sogar vom Webserver erzwungen. Ungesicherte HTTP Forum Links werden nun umgeleitet auf das gesicherte HTTPS Forum. Alle Links zu meiner Webseite in bereits bestehenden Forum Beiträgen wurden aktualisiert mit den HTTPS Links. Dies gibt allen Forum Accounts mehr Sicherheit, insbesondere wenn meine Webseite in einem öffentlichen Netzwerk besucht wird.

Da es nur ein Klasse 1 Zertifikat ist, zeigen nicht alle Browser ein geschlossenes Schloss in der Adressleiste an. Klickt man aber auf die Verbindungsinformationen der Webseite, sollte eine gültige verschlüsselte Verbindung angezeigt werden. Dies habe ich getestet mit Chrome, Edge und Internet Explorer.

Links zu den ZIP, Bild und Readme Dateien funktionieren mit beiden Methoden, HTTP und HTTPS.

My website use an encrypted connection using HTTPS since 30 hours now. If you visit my forum, the HTTPS connection is enforced by the web server. Unsecured HTTP forum links will be redirected to the secured HTTPS forum. All links to my web site in existing forum posts was updated with the HTTPS link. This adds more security to your forum account, especially if you visit my website on a public network.

Since it is just a class 1 certificate, some browsers don't show a closed lock at the address bar. But if you click on the details of the web site connection in the browser, it should display a valid encrypted connection! Tested this with Chrome, Edge and Internet Explorer.

Links to the zip, image and readme files will work with both methods, HTTP and HTTPS.

[jts3servermodwebui_translation]

All messages are stored in the MySQL database.

First start with this line (correct the values at the end) to add another language (example for Italian):

Code Select Expand

INSERT INTO `jts3servermodwebui_language` (`id`, `name`, `image`, `showLanguage`, `dateCountry`, `dateFormat`) VALUES(3, 'Italiano', 'IT.png', 1, 'it_IT', '%d.%m.%Y %H:%M:%S');

After you did this, every translation in the table jts3servermodwebui_translation needs the language_id = 3 (same id as in the table jts3servermodwebui_language).

In the table jts3servermodwebui_language you can also change the date format for a language (column dateFormat), or just hide this language from the language chooser at the top header of the web interface (column showLanguage).

In the far future I plan to implement a web interface to create a translation for the web interface. But currently this is the only way.
If you want, you can provide an SQL export of the new language for other users in this forum, post it in this board: https://www.stefan1200.de/forum/index.php?board=11.0

[Enable Admin Server Query at Server Group Protection]

Some of you might not know, that the JTS3ServerMod also allows to protect the Admin Server Query group using the function Server Group Protection. The only exception: add_missing_groups is not working for query groups (because of security reasons). But the Web Interface is not displaying the query groups, because in most cases it is not useful to display that groups to a customer.

But if you want to allow Web Interface users to select this query server groups, you can enable it by changing one PHP file and fire one SQL command.

Enable Admin Server Query at Server Group Protection

Execute MySQL command

Code Select Expand

UPDATE `jts3servermodwebui_functionpage` SET `options` = 'multiple,showquerytype' WHERE `botfunction_id` = 12 AND `configkey` = '_groups'

Open file include/functions/servergroupprotection.php and find both lines with getServerGroupComboBoxDef and change the last argument from false to true.

include/functions/servergroupprotection.php - Line 33

Code Select Expand

$groupprotInput .= "<tr><td>".getServerGroupComboBoxDef($botid, $class_db, $prefix."_group".$row[0], $row[1], false, true)."</td><td>";

include/functions/servergroupprotection.php - Line 37

Code Select Expand

$groupprotInput .= "<tr><td>".getServerGroupComboBoxDef($botid, $class_db, $prefix."_group_new", $row[1], false, true)."</td><td>";




Disable Admin Server Query at Server Group Protection (default)

Execute MySQL command

Code Select Expand

UPDATE `jts3servermodwebui_functionpage` SET `options` = 'multiple' WHERE `botfunction_id` = 12 AND `configkey` = '_groups'

Open file include/functions/servergroupprotection.php and find both lines with getServerGroupComboBoxDef and change the last argument from true to false.

include/functions/servergroupprotection.php - Line 33

Code Select Expand

$groupprotInput .= "<tr><td>".getServerGroupComboBoxDef($botid, $class_db, $prefix."_group".$row[0], $row[1], false, false)."</td><td>";

include/functions/servergroupprotection.php - Line 37

Code Select Expand

$groupprotInput .= "<tr><td>".getServerGroupComboBoxDef($botid, $class_db, $prefix."_group_new", $row[1], false, false)."</td><td>";


Last updated for Web Interface 3.0 build 3010! On newer or older versions the line numbers may not match.

Please give me feedback, do you like the dark theme from web interface build 3010 (included in JTS3ServerMod 5.5.4 release).

Bitte gibt mir Rückmeldung wie euch das dunkle Theme im Web Interface Build 3010 gefällt (ist beim JTS3ServerMod 5.5.4 enthalten).

Bot Settings / Manager - Desktop - Dark Theme
Bot Settings - Away Mover - Desktop - Dark Theme
Settings - Desktop - Dark Theme

Important notice: This change have affect to all users of the web interface. Everyone will (not) be able to select the Query Server Groups at the Server Group Protection configuration page!

Execute the following SQL command to the database to allow selection of Query Server Groups at the Server Group Protection configuration page:

Code Select Expand

UPDATE jts3servermodwebui_functionpage SET options = 'multiple,showquerytype' WHERE botfunction_id = 12 AND configkey = '_groups'

To remove this ability just execute the following SQL command:

Code Select Expand

UPDATE jts3servermodwebui_functionpage SET options = 'multiple' WHERE botfunction_id = 12 AND configkey = '_groups'

[Password Reset]

In general you should be able to use the Password Reset function of the web interface. So you should check, why the PHP mail function is not working. In most cases your sendmail service is not running or configured right, or you made wrong settings in the php.ini file. If there is another web interface admin, you can ask the other web interface admin to change your password using the User Manager.

If you don't have another web interface admin or you need to solve this password issue faster, you can just change the encrypted password directly in the MySQL database.

Open the MySQL database of the web interface with your MySQL Administration Tool (like PHPMyAdmin) and open the jts3servermodwebui_users table. Now search for your own user account. At your own user account you set the following encrypted string in the table column password: 7ed8838a3a18b33ca2d7028bd057f5a8

Now you can login with the password: HelloWorld2015

If the account was blocked / banned already, follow the unblock / unban instructions.

[-= English =-]

-= English =-
Important: As always: Do a database backup every time before you update! If you made own modifications to the web interface, you have to do them again after updating the web interface!

Since Web Interface 3.0 / Build 3000 it is very easy to update the web interface. Just replace all files of the web interface, open the web interface in your Browser and login as administrator. If you are already logged in, make sure that you visit the bot list page first! You may have to accept a message, that an automatic database update is needed, done. No more steps to do!

I try to write down every changed and added files of the update in the changelog_webinterface.txt. But this is only important for you, if you made changes to the files. If all files are still original, just replace them all.


-= German =-
Wichtig: Wie immer: Erstelle eine Datenbank Sicherung jedes Mal vor dem Update! Falls eigene Modifikationen am Web Interface vorgenommen wurden, müssen diese nach dem Update erneut vorgenommen werden!

Seit Web Interface 3.0 / Build 3000 ist das Updaten sehr einfach. Ersetze einfach alle Dateien vom Web Interface, öffne das Web Interface im Browser und melde dich als Administrator an. Falls man bereits eingeloggt war, gehe unbedingt als erstes auf die Seite Bot Liste! Bestätige gegebenenfalls die Meldung, das ein automatisches Datenbank Update notwendig ist, fertig. Es sind keine weiteren Schritte notwendig!

Ich versuche immer alle geänderten und hinzugefügten Dateien vom Update in die changelog_webinterface.txt zu schreiben. Dies ist aber nur dann wichtig, wenn eigene Modifikationen am Web Interface vorgenommen wurden. Wenn alle Dateien noch original sind, dann ersetze einfach alle Dateien.

[Screenshots taken on 2nd February 2015]

Currently I work on some improvements of the web interface design. My goal is to make it more usable on mobile devices and a little bit more modern.

First I have to say: I'm still only a programmer, not a designer. But the included web interface stays my work, because I like to know where I have to do changes if I add new features to the bot.

But of course I understand everyone writing to me, that the web interface is not perfect in every case. That is one of the reasons why I started today to improve the web interface design.

I have some screenshots of the new Bot General Settings page for you. One screenshot was created on a normal Windows PC with the Internet Explorer 11 (looks the same in Chrome 40). The other four screenshots are taken on my HTC One M7 Smartphone using the Android Chrome browser. You may realize that the screenshot size is not the same than the viewport size of the browser, in portrait mode the viewport is just 360 x 615 pixel and in landscape mode just 640 x 335 pixel. That's the way how Smartphones zoom the pages to make it readable on a approx 5 inch screen.

Screenshots taken on 2nd February 2015
Firefox 35 on a PC - Bot Log
Firefox 35 on a PC - Login Log

Screenshots taken on 1rd February 2015 (Smartphone screenshots scaled down to 33%)
Smartphone Android Chrome - Portrait Mode - Bot List
Smartphone Android Chrome - Portrait Mode - Function List
Smartphone Android Chrome - Landscape Mode - Bot List
Smartphone Android Chrome - Landscape Mode - Function List

Screenshots taken on 31th January 2015 (Smartphone screenshots scaled down to 25%)
Smartphone Android Chrome - Portrait Mode - Reduced Buttons
Smartphone Android Chrome - Portrait Mode - All Buttons
Smartphone Android Chrome - Landscape Mode - Reduced Buttons
Smartphone Android Chrome - Landscape Mode - All Buttons
Tablet Android Chrome - Portrait Mode
Tablet Android Chrome - Landscape Mode

Screenshots taken on 26th January 2015 (Smartphone screenshots scaled down to 50%)
Chrome 40 on a PC
Smartphone Android Chrome - Portrait Mode - Screenshot 1
Smartphone Android Chrome - Portrait Mode - Screenshot 2
Smartphone Android Chrome - Landscape Mode - Screenshot 1
Smartphone Android Chrome - Landscape Mode - Screenshot 2

Old screenshots taken on 25th January 2015
Internet Explorer 11 on a PC
Smartphone Android Chrome - Screenshot 1
Smartphone Android Chrome - Screenshot 2

Please give me feedback. How you like it? Better than the current released version? Whats good, whats bad?

Edit 26.01.2015: Updated screenshots to show the progress.
Edit 31.01.2015: Updated screenshots to show the reduced display mode.
Edit 01.02.2015: Updated screenshots to show the new tables on small viewports (like Smartphones in portrait mode).
Edit 02.02.2015: Updated screenshots to show the new bot log / login log.

Der Roboter als SVG Datei: JTS3ServerMod_robot.svg

100 x 100 px


120 x 120 px


150 x 150 px


200 x 200 px


200 x 75 px


200 x 100 px


230 x 85 px


250 x 100 px


468 x 60 px


Mehr auf Anfrage später.

The robot as SVG file: JTS3ServerMod_robot.svg

100 x 100 px


120 x 120 px


150 x 150 px


200 x 200 px


200 x 75 px


200 x 100 px


230 x 85 px


250 x 100 px


468 x 60 px


More on request later.

[Since Web Interface 3.0 Build 3010 (10.07.2015) this colors are taken from the css file.]

You like to change the color of the green highlighted keywords in the helptext of the web interface, like shown in this screenshot?

Since Web Interface 3.0 Build 3010 (10.07.2015) this colors are taken from the css file.
Just look into the css file in the data/css directory at the class:

Code Select Expand

.bbcode_message_keyword
{
color:#008000;
}


In older Web Interface versions you have to change the colors in the database:
Example: Change the color from #008000 to #800080

Code Select Expand

UPDATE jts3servermodwebui_translation SET `textmessage` = REPLACE (`textmessage`, '[color=#008000]', '[color=#800080]') WHERE `textmessage` LIKE '%[color=#008000]%'

Just list all messages with BBCode color:

Code Select Expand

SELECT * FROM `jts3servermodwebui_translation` WHERE `textmessage` LIKE '%[color=%'

Just execute this SQL commands using PHPMyAdmin or a MySQL client of your choice.

[The following versions have this bug:]

Last week I found a critical bug in the web interface: Saving bot connection settings the second time after getting an error message overwrites the settings of another bot!
Maybe you read about this already in the download thread.

The following versions have this bug:
Web Interface 2.0.4 Final (20.09.2014)
Web Interface 2.1 RC 1 (17.10.2014)
Web Interface 2.1 RC 2 (20.10.2014)

I fixed this bug in the web interface 2.1 RC3 from 23.10.2014. Of course in newer versions this is fixed too. Please update to the latest version as soon as possible.

If you can't or won't update, please write me an e-mail with your include/botcreate.php attached for a quick fix.

[-= Informationen =-]

(If you want to read this text in English: English version)

-= Informationen =-
Dieses Web Interface erlaubt es virtuelle Bot Instanzen zu erstellen, konfigurieren und zu steuern. Es können neue Benutzer für das Web Interface registriert werden, um ihnen das Erstellen, Konfigurieren und Steuern der eigenen Bots zu erlauben. Es ist möglich die eigene Registrierung durch Gäste und die Bot Erstellung für normale Nutzer zu erlauben oder verbieten. Aktuell stehen im Web Interface die Sprachen Deutsch und Englisch zur Verfügung.

-= Systemanforderungen für das Web Interface =-

• Hosting Edition vom JTS3ServerMod mit aktiviertem MySQL Modus und Query Interface. Die Systemanforderungen vom JTS3ServerMod sind vergleichbar zur öffentlichen Version. Zusätzlich zur Öffentlichen Version, benötigt die Hosting Edition aber eine online Verbindung zu www.stefan1200.de, wodurch mindestens Java 7 notwendig ist (aufgrund der starken TLS Verschlüsselung).
  
• Webspace mit PHP 5.4 (oder höher) Unterstützung, mit aktivierter und konfigurierter Session, Socket (fsockopen), mbstring, Mail und MySQLi Erweiterung.
  
• Wenn der Apache Webserver verwendet wird, aktiviere bitte das Modul mod_access_compat (Apache 2.4) oder mod_authz_host (Apache 2.2).
  
• Aus Sicherheitsgründen sollte die PHP Einstellung allow_url_include deaktiviert werden.
  
• MySQL Datenbank Version 5.5.3 oder höher. Ebenfalls erfolgreich getestet mit MariaDB 10.1.3.
  
• Wenn der JTS3ServerMod und das PHP Web Interface nicht auf der selben Maschine laufen, muss die MySQL Datenbank Remote Zugriff erlauben.

Die meisten Voraussetzungen können mit der PHP Funktion phpinfo(); überprüft werden.

-= Screenshots =-
Bot Erstellung - Desktop
Bot Erstellung - Smartphone
Bot List - Desktop
Bot List - Desktop - Dark Theme
Bot List - Smartphone
Bot Log - Desktop
Bot Log - Desktop - Dark Theme
Bot Einstellungen / Manager - Desktop
Bot Einstellungen / Manager - Desktop - Dark Theme
Bot Einstellungen / Manager - Smartphone
Bot Einstellungen - Away Mover - Desktop
Bot Einstellungen - Away Mover - Desktop - Dark Theme
Bot Einstellungen - Away Mover - Smartphone
Bot Benutzer Manager - Desktop
Vollständiger Header - Smartphone
Einstellungen - Desktop
Einstellungen - Desktop - Dark Theme
Benutzerliste / Manager
Benutzerliste / Manager - Dark Theme
Benutzerliste / Manager - Smartphone
Benutzerliste / Manager - Smartphone (Querformat)

JTS3ServerMod Hosting Edition mit MySQL Support und PHP Web Interface ist verfügbar hier.

This topic has been moved to General Discussions.

https://www.stefan1200.de/forum/index.php?topic=85.0

[************* Adding a new user account *************]

Situation: You have an own website and like to create bots and user accounts for the bot web interface with your own website. This document should help you.

************* Adding a new user account *************
You want to create web interface user accounts on your own? No problem, you just have to fill the table jts3servermodwebui_users.
To add a simple user account without any admin permissions, just do (password has to be hashed, see below):

Code Select Expand

INSERT INTO `jts3servermodwebui_users` (`name`, `password`, `salt`, `email`) VALUES ('abc', 'Password123', 'ThisIsARandomSalt', 'my@mail.net');

*** Table jts3servermodwebui_users ***
Required table columns of jts3servermodwebui_users:
name = loginname of the user account, has to be unique.
password = hashed password using hash("sha512", "ThisIsARandomSalt"."Password123", false), example in PHP.
salt = the used salt for the password.
email = E-Mail address of the user, used of the "Reset Password" function (and some more pages), has to be unique.

Optional table columns of jts3servermodwebui_users:
registertime = Unix timestamp of the time when this user account was created.
maxbotcount = Amount of maximum allowed bots (for this user) or -1 for no limit. Will be checked only while the user create a new bot.
adminlevel = 0 - Normal user account without any admin permissions
                    1 - Restricted Administrator, limited admin functions
                    2 - Full Administrator, all admin functions
userstatus =  0 - Active user account
                   -1 - Disabled user account (can't login)
Other columns are only used by the web interface to track last login time or password fail count.


**************** Adding a new bot ****************
You can also add a bot directly to the MySQL table, but this is a little bit more complex. Two tables have to be touched. After you added the bot to the database, you have to send the telnet command instancelistreload to the bot (more details below).

Code Select Expand

INSERT INTO `jts3servermod_instances` (`name`, `ts3serverip`, `ts3portid`) VALUES ('abc', '192.168.1.100', '9987');
INSERT INTO `jts3servermod_instanceconfig` (`instance_id`, `configkey`, `configvalue`) VALUES(1, 'ts3_server_address', '192.168.1.100');
INSERT INTO `jts3servermod_instanceconfig` (`instance_id`, `configkey`, `configvalue`) VALUES(1, 'ts3_server_query_port', '10011');
INSERT INTO `jts3servermod_instanceconfig` (`instance_id`, `configkey`, `configvalue`) VALUES(1, 'ts3_server_query_login', 'serveradmin');
INSERT INTO `jts3servermod_instanceconfig` (`instance_id`, `configkey`, `configvalue`) VALUES(1, 'ts3_server_query_password', 'abc123');
INSERT INTO `jts3servermod_instanceconfig` (`instance_id`, `configkey`, `configvalue`) VALUES(1, 'ts3_virtualserver_id', '-1');
INSERT INTO `jts3servermod_instanceconfig` (`instance_id`, `configkey`, `configvalue`) VALUES(1, 'ts3_virtualserver_port', '9987');
INSERT INTO `jts3servermod_instanceconfig` (`instance_id`, `configkey`, `configvalue`) VALUES(1, 'bot_slowmode', '0');


*** Table jts3servermod_instances ***
Required table columns of jts3servermod_instances:
name = The bot name, has to be unique. Don't use spaces in the bot name, only use letters, numbers, minus and underscore!
ts3serverip = Just the TS3 server address which the bot is using, should be the config value of ts3_server_address.
ts3portid = The TS3 server port or virtual server id, or more exactly: ts3_virtualserver_id == -1 ? ts3_virtualserver_port : ts3_virtualserver_id

Optional table columns of jts3servermod_instances:
enabled = Auto start bot, 1 or 0. Should be 0 to allow bot being configured first. Will be changed to 1 from bot web interface on first start.
logmode = 0 - No log for this bot will be created.
                1 - Log file will be created to file system, table column logpath is required only in this case.
                2 - Write log into the MySQL database, table jts3servermod_log will be used as target (recommended).
csvlogmode = This logs connecting clients, including time, name, ip address. Possible values like at logmode, if set to 1, table column csvlogpath is required.
debug = Special debug mode, 1 or 0. Should be 0. Creates a full communication log file into the bot directory. Don't use this for a long time, some hours could create very big log files already.
Other columns are only for internal web interface timestamp stuff (last start time, etc.).


*** Table jts3servermod_instanceconfig ***
Required table columns of jts3servermod_instanceconfig:
instance_id = The id of the table jts3servermod_instances (so request last insert id from database after inserting a new bot to jts3servermod_instances).
configkey = A config key for the bot, they are the same like from the file based configuration.
                  Required are: ts3_server_address, ts3_server_query_port, ts3_server_query_login, ts3_server_query_password, ts3_virtualserver_id, ts3_virtualserver_port and bot_slowmode
                  For a full list of config keys, just look into the normal bot configuration help file.
configvalue = The value for the config key, they are the same like from the file based configuration.
                     For a more detailed explanation, just look into the normal bot configuration help file.



************ Make bots visible for a user ************
You have to connect a user account to a bot. This allows that one user can manage many bots. But it is also possible that many users can manage one bot. For every user or every bot you have to insert the bot / user connection to the database.

Code Select Expand

INSERT INTO `jts3servermodwebui_usersinstances` (`user_id`, `instance_id`, `fullaccess`) VALUES(1, 1, true);


*** Table jts3servermodwebui_usersinstances ***
Required table columns of jts3servermodwebui_usersinstances:
users_id = The user id of the table jts3servermodwebui_users.
instance_id = The bot id of the table jts3servermod_instances.

Optional table columns of jts3servermodwebui_usersinstances:
fullaccess = TRUE or 1 if the user should have full bot management permissions, FALSE or 0 if just the normal permissions.



************** Remove a user account **************
Just delete the user id from the tables jts3servermodwebui_users and jts3servermodwebui_usersinstances.

Code Select Expand

DELETE FROM `jts3servermodwebui_users` WHERE id = 1;
DELETE FROM `jts3servermodwebui_usersinstances` WHERE users_id = 1;



****************** Remove a bot ******************
To remove a bot, just delete the bot id from the tables jts3servermod_instances, jts3servermod_instanceconfig, jts3servermodwebui_usersinstances and jts3servermod_log. After you removed the bot from the database, you have to send the telnet command instancelistreload to the bot (more details below). Important: Make sure that you stopped the bot BEFORE you remove the bot from the database! Use the telnet command stop <instance name> for this.

Code Select Expand

DELETE FROM `jts3servermod_instances` WHERE id = 1;
DELETE FROM `jts3servermod_instanceconfig` WHERE instance_id = 1;
DELETE FROM `jts3servermodwebui_usersinstances` WHERE instance_id = 1;
DELETE FROM `jts3servermod_log` WHERE instance_id = 1;



******** Bot telnet command instancelistreload ********
If you added or removed a bot in the MySQL database, you have to trigger an instance list reload at the bot. To do this, you can connect to the bot telnet port (default: 5873), login with your telnet password and send the command instancelistreload. If you work with the class/dbconnect.php and class/BotTelnet.php of the official web interface, you can just use the official $botTelnet->instancelistReload(); function.

Important: If you want to remove a bot, make sure that you stopped the bot BEFORE you remove the bot from the database! Use the telnet command stop <instance name> for this.

A list of all bot telnet commands: TelnetCommandHelp.html



**************** Important Settings ****************
If you create user accounts and bots on your own, don't forget to disable both functions for normal web interface users, look at the screenshot below.

[-= Information =-]

-= Information =-
Dies ist eine TSDNS Alternative welches MySQL als Datenbank verwendet. Zusätzlich wird in der Datenbank abgespeichert, wie oft ein Hostname verwendet worden ist, und wann diese zuletzt abgefragt worden ist. Einfach die jtsdns.sql in die MySQL Datenbank importieren, anschließend kann noch eine eigene Webseite erstellt werden, die die Einträge in der JTSDNS Tabelle verwaltet / hinzufügt. Die Namen der Spalten sind selbst erklärend. Wie bei der richtigen TSDNS Anwendung sind auch Wildcards bei den Hostnamen möglich.

Dieser Dienst kann Fehler haben, aber bei einem Anwender läuft dies bereits ohne Probleme. Für weitere Informationen zur Benutzung bitte die readme.txt Datei lesen.


-= Systemanforderungen =-
Dieses Programm läuft unter Windows und Linux (auch ohne X Server). Auf Mac OS X 10.4+ sollte es ebenfalls laufen, allerdings ungetestet.
Alles was benötigt wird ist die Java SE Laufzeitumgebung Version 5 oder neuer.
Die neuste Version ist auf www.java.com oder http://www.oracle.com/technetwork/java/javase/downloads/index.html zu bekommen.
Anwender von Mac OS X 10.4 oder neuer haben es wohlmöglich bereits installiert.
FreeBSD Anwender können sich auf http://www.freebsd.org/de/java/ über Java auf FreeBSD informieren.
Linux Anwender sollten das Paket openjdk-8-jre-headless / java-1.8.0-openjdk-headless installieren.
Auf älteren Linux Versionen funktioniert auch sun-java5-jre, sun-java6-jre, openjdk-7-jre oder java-1.7.0-openjdk.
Ein Beispiel für Debian oder Ubuntu: apt-get install openjdk-8-jre-headless
Ein Beispiel für CentOS oder Fedora -21: yum install java-1.8.0-openjdk-headless
Ein Beispiel für Fedora 22+: dnf install java-1.8.0-openjdk-headless
Ein Beispiel für OpenSUSE: zypper install java-1_8_0-openjdk-headless
Das Paket gcj-jre (GNU Java) wird nicht funktionieren!


-= Dokumentation =-
Englische Readme Datei and Änderungshistorie - readme.txt


-= Download =-
Neuste Version: download

[-= Information =-]

-= Information =-
This is an TSDNS alternative using MySQL as database. In addition to this it also saves to database how often a hostname was requested and the last requested time. Just import the jtsdns.sql to your MySQL database and, if you want, create your own website that adds or edit the entries in that JTSDNS table. The names of the columns are quite self explaining. Like the real TSDNS application wildcards at hostnames are supported.

It can still have bugs, but one user use it already on a server without problems. For more information about the usage, just look in the readme.txt.


-= System requirements =-
This program runs on Windows and Linux (even without X server). On Mac OS X 10.4+ it should run too, but it is not tested.
Please send me a message if this bot runs on Mac OS X without problems.
All you need is a Java SE runtime environment version 5 or newer.
You can get the latest version from www.java.com or http://www.oracle.com/technetwork/java/javase/downloads/index.html
Mac OS X 10.4 or newer users should have it already installed.
FreeBSD Users should look at http://www.freebsd.org/java/ to learn more about Java on FreeBSD.
Linux users should install the package openjdk-8-jre-headless / java-1.8.0-openjdk-headless.
On older linux you can also use sun-java5-jre, sun-java6-jre, openjdk-7-jre or java-1.7.0-openjdk.
An example on Debian or Ubuntu: apt-get install openjdk-8-jre-headless
An example on CentOS or Fedora -21: yum install java-1.8.0-openjdk-headless
An example on Fedora 22+: dnf install java-1.8.0-openjdk-headless
An example on OpenSUSE: zypper install java-1_8_0-openjdk-headless
The package gcj-jre (GNU Java) will not work!

Maybe you want to limit the maximum ram that this program use. This can be useful on a virtual server.
You can do this by using java command line arguments for the java virtual machine.
If you want to use 30 MB ram as maximum, you can start JTSDNS like this:
java -mx30M -jar JTSDNS.jar
Notice: If you choose a to low value, JTSDNS may not run or is not stable. I did no long time tests on this.


-= Documentation =-
Readme file and changelog - readme.txt


-= Download =-
Latest final version: download

[Important:]

As you might know, the public edition of the bot made a huge progress in the last weeks. Also the next version of the special edition is almost done, all changes to the public edition are already included in the developer version on my computer, see current changelog at the bottom of this post. But the new modular design of all functions have a big impact to the web interface. I have to recreate big parts of the web interface, which I work on it currently. But as soon as I am done with all changes, you will be able to use all features and benefits of the new public version with the special edition and the web interface. I hope to release the special edition including the new web interface end of February 2014.

Important:
Not all bot settings can be imported to the new web interface. To much stuff changed.
But it should be possible to import the user accounts and bots with main settings (everything from the first two settings pages).
If you don't want to lose that, you have to stay at the current version! But read now what you don't get, if you don't update:

Version 5.0 Hosting Edition RC 1 (XX.02.2014)
+ Complete redesign of the bot, now all bot functions are modular and most of them can be used multiple times.
  This functions will be set in the bot config file at bot_functions.
  Use chat command !botfunctionlist to get a list of loaded functions.
  Some examples:
  You want to use different welcome messages for some server groups? Do it now!
  You have different AFK channels for different server groups? You can set this now for Idle Check, Away Mover and Mute Mover!
  Some server groups should be kicked after using a bad nickname, some should only get a message? It's now possible!
+ Fully recreated the Bad Channel Name Check and got a lot of new features!
  Now the Bad Channel Name Check knows who created or renamed the channel and can punish him (just a message or kick).
  Much more features here to choose what should happen.
  The config file has changed and expects the message first like the Bad Nickname Check config file.
+ Bad Nickname Check allows now not to kick that client, just send a message if you want.
+ Auto Move now allows to add the target channel name to the message, see Auto Move config file.
+ Added !setchannelgroup chat command, this allows you to set a channel group for a client in many channels, even if the client is offline.
+ New chat command !setchannelname, this allows you to change a channel name.
+ New chat command "check" for the Bad Channel Name Check function.
  The Bad Channel Name Check since version 5.0 RC1 don't recognise changed channel names while the bot is offline.
  Bot Admins can now check all channel names manually using this chat command, if the bot was offline for a longer time
  and rename channels using the !setchannelname command.
+ Changed !botcfgreload command, now it's possible to reload the whole bot configuration without reconnecting the bot with !botreload.
  Only some of the internal bot settings (like the TS3 connection details) can still only reloaded using the !botreload command.
+ Command !clientsearch is now able to detect that someone is currently online (displays also the current client ID),
  and if there are more than 5 search results, it shows the client names of up to 20 search results to refine the search.
+ LastSeen is able to display up to 10 search results now.
+ Channel Notify as two more options to limit which server groups should be watched.
o Mute Mover change: If you now enable headphone and microphone mute within one function prefix,
                both have now happen at the same time to move the client!
                Create a second Mute Mover prefix, if you still need that to trigger for each mute state.
o Server Group Protection now only adds missing server groups (if enabled in config), if server group type is equals to 1 (which is a normal server group).
  This change allows now limited bot admins to change configuration of Server Group Protection. This was forbidden because of security reasons.
o Changed the Client Database Cache to increase the bot performance.
o Updated documentation, completed German translation.