JTS3ServerMod_3.4.0 funktioniert nicht

[froesch]

die installationsanleitung ist kürzer als kurz gehalten...

kommandos wie !lastseen funktionieren nicht auf meinem ts server, daher denke ich dass der bot nicht läuft. zu sehen ist er ja auch nirgendwo.

ich habe mir eine batch geschrieben um den bot zu starten

Code Select Expand


cd C:\Program Files (x86)\Java\jre6\bin\
java -jar C:\JTS3ServerMod_Legacy\JTS3ServerMod.jar -config config/JTS3ServerMod_InstanceManager.cfg -log log/instance.log


es treten keine fehler beim start auf aber ich habe niemals etwas in der log datei? keine ahnung warum.

mein system ist ein win7 mit localserver zum testen (TS 3.0.0-beta30 [Build: 12998]). ich habe folgende dateien mit notepad bearbeitet JTS3ServerMod_server1.cfg und JTS3ServerMod_InstanceManager.cfg und als utf-8 abgespeichert.

Code Select Expand


# Config file of the JTS3ServerMod
# https://www.stefan1200.de
# This file must be saved with the encoding ISO-8859-1!

# Teamspeak 3 server address
ts3_server_address = 127.0.0.1
# Teamspeak 3 server query port, default is 10011
ts3_server_query_port = 10011
# Teamspeak 3 server admin account name
ts3_server_login = john
# Teamspeak 3 server admin password
# ts3_server_password = KCf4rgZtwN3jT/supbQ9ygFqOe4YXRE/QTz9caBP
# Teamspeak 3 virtual server ID or -1 to use ts3_virtualserver_port
ts3_virtualserver_id = -1
# Teamspeak 3 virtual server port, only needed if ts3_virtualserver_id is set to -1
ts3_virtualserver_port = 9987
# Channel id, the bot will join into it after connecting. If not wanted, use a negative number like -1.
ts3_channel_id = 1

# Activate the slow mode of the bot, 0 = disable, 1 = enable.
# If slow mode is activated, the bot connects slower to the server
# and disables some bot features to reduce the amount of needed commands.
# This feature may allow you to use the bot without whitelist the bot IP address.
# Slow mode disables the bad channel name check, welcome message, client database cache
# and do not allow the bot check interval to be lower than 3 seconds.
bot_slowmode = 0
# Check every X seconds, default is 1.
bot_check_interval = 1
# A different encoding of the messages config files.
# Default is UTF-8 which should be good for all EU and US languages.
# Change this only if you know what you are doing!
# For english or german language you can also use the encoding ISO-8859-1
# A list of all valid ones: http://java.sun.com/j2se/1.5.0/docs/guide/intl/encoding.doc.html
bot_messages_encoding = UTF-8
# This enables the client database list cache. This cache is needed for commands like !lastseen. 1 = Enable, 1 = Disable
bot_clientdblist_cache = 1
# Server Query name, this will be displayed as name of the connection.
bot_server_query_name = TS3 Server bot
# Second Server Query name, this will be displayed as name of the connection.
# This name will be used, if the first name is already in use.
bot_server_query_name_2 = TS Server
# Change the date pattern, which will be used to format a date in chat functions and welcome message.
# To get help how to make such a pattern, look here: http://java.sun.com/j2se/1.5.0/docs/api/java/text/SimpleDateFormat.html
bot_date_pattern = yyyy-MM-dd HH:mm:ss
# Should the bot try to connect forever if the Teamspeak server or the bot is offline? 0 = disable, 1 = enable
bot_connect_forever = 0
# A comma seperated list (without spaces) of unique user ids, which should be able to use bot admin commands.
# The unique user ids looks like this: mBbHRXwDAG7R19Rv3PorhMwbZW4=
bot_admin_list = dRt9fHiElAujBwIWaTjHe8YvE6o=

# Allow !lastseen command for all clients? 1 = Yes, 0 = No
command_lastseen = 1

# Choose record check mode, 0 = disable, 1 = kick, 2 = move
# This feature will move or kick a recording client (of course only the record function of the Teamspeak client is detected).
record_check_enable = 0
# Path to file which contains the record messages
record_file = config/recordmessages.cfg
# If mode 2 selected, set channel id to move recording clients into it
record_move_channel_id = 1
# A comma seperated list (without spaces) of channel ids.
# Depends on the given mode, this channels can be ignored or only this channels will be checked!
record_channel_list =
# Select one of the two modes for the channel list.
# ignore = The selected channels will be ignored.
# only = Only the selected channels will be checked.
record_channel_list_mode = ignore
# A comma seperated list (without spaces) of server group ids.
# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
record_group_list =
# Select one of the two modes for the server group list.
# ignore = The selected server groups will be ignored.
# only = Only the selected server groups will be checked.
record_group_list_mode = ignore
# Add complain entry to the user, 0 = No, 1 = Yes
record_add_complain = 0
# Select the message mode, how the client should get the message (useless if kick is enabled).
# poke, chat or none are valid values!
record_message_mode = poke

# Enable idle check, 0 = disable, 1 = kick, 2 = move
# This feature will move or kick an idle client.
idle_check_enable = 0
# Path to file which contains the idle messages
idle_file = config/idlemessages.cfg
# If mode 2 selected, set channel id to move idle clients into it
idle_move_channel_id = 1
# A comma seperated list (without spaces) of channel ids.
# Depends on the given mode, this channels can be ignored or only this channels will be checked!
idle_channel_list =
# Select one of the two modes for the channel list.
# ignore = The selected channels will be ignored.
# only = Only the selected channels will be checked.
idle_channel_list_mode = ignore
# A comma seperated list (without spaces) of server group ids.
# Depends on the given mode, this server groups can be ignored or only this server groups will be checked!
idle_group_list =
# Select one of the two modes for the server group list.
# ignore = The selected server groups will be ignored.
# only = Only the selected server groups will be checked.
idle_group_list_mode = ignore
# Set the max idle time in minutes.
# If mode 1 selected, the client will be kicked after being idle for this time.
# If mode 2 selected, the client will be moved to idle_move_channel_id after being idle for this time!
idle_max_time = 60
# If mode 2 selected, set the max idle time in minutes to kick someone.
# Has to be greater than idle_max_time or -1 to disable this feature!
idle_second_max_time = -1
# Set the idle warn time in minutes or set -1 to disable this feature.
# The idle warn time has to be smaller than the max idle time
idle_warn_time = -1
# A minimum client count to activate idle check (telnet and TS3 clients counted together).
# If less clients online, idle check does nothing.
idle_min_clients = 0
# Select the message mode, how the client should get the message (useless if kick is enabled).
# poke, chat or none are valid values!
idle_message_mode = chat
# Select the message mode, how the client should get the message.
# poke or chat are valid values!
idle_warn_message_mode = chat

# Enable away mover, 0 = disable, 1 = enable, 2 = enable with move back
# This feature will move the client as soon as away status is set for longer than X seconds, specified below.
away_check_enable = 0
# Channel id to move away clients into it
away_move_channel_id = 1
# Idle time in seconds after the client with away status will be moved to the channel.
# Has between 0 and 100 seconds!
away_move_delay = 5
# A comma seperated list (without spaces) of channel ids.
# Depends on the given mode, this channels can be ignored or only this channels will be checked!
away_channel_list =
# Select one of the two modes for the channel list.
# ignore = The selected channels will be ignored.
# only = Only the selected channels will be checked.
away_channel_list_mode = ignore

# Enable advertising, 0 = disable, 1 = send to virtual server, 2 = send to channel
advertising_enable = 0
# If mode 2 selected, set channel id to write advertising message into it
advertising_channel_id = 1
# Advertise every X minutes
advertising_repeat_time = 30
# Path to file which contains the advertising messages
advertising_file = config/advertising.cfg

# Enable default welcome message, 0 = disable, 1 = enable
# This welcome message, if enabled, will be used for all other groups than specified for welcomemessage_groups.
# If welcomemessage_enable is disabled, then this will be used for all clients in all groups.
default_welcomemessage_enable = 0
# Select the message mode, how the client should get the message.
# poke or chat are valid values!
default_welcomemessage_message_mode = chat
# You can set another welcome message for specified server groups, 0 = disable, 1 = enable
welcomemessage_enable = 0
# A comma seperated list (without spaces) of server group ids, which should get this welcome message.
welcomemessage_groups =
# Select the message mode, how the client should get the message.
# poke or chat are valid values!
welcomemessage_message_mode = chat
# Path to file which contains the welcome messages.
welcomemessage_file = config/welcomemessages.cfg

# Enable bad nickname check, 0 = disable, 1 = enable
# This feature will kick every client which match one of the bad nickname rules.
badnickname_check_enable = 0
# Add complain entry to the user, 0 = No, 1 = Yes
badnickname_add_complain = 0
# Path to file which contains the bad nickname kick message and check rules.
badnickname_file = config/badnickname.cfg

# Enable bad channel name check, 0 = disable, 1 = enable
# This feature will force delete every channel which match one of the bad channel name rules.
badchannelname_check_enable = 0
# Path to file which contains the bad channel name check rules.
badchannelname_file = config/badchannelname.cfg

# Enable server group protection, 0 = disable, 1 = enable
# If enabled, this function will check all server groups from clients on the server, which are currently online.
# If a client use a protected server group and is not on the list of the bot, it will be removed from the server group.
servergroupprotection_enable = 0
# A comma seperated list (without spaces) of server group ids, which should be protected.
servergroupprotection_groups = 2,6
# Enable this to kick every client which using a protected server group and are not on the list of the bot, 0 = disable, 1 = enable
servergroupprotection_kick = 0
# Add complain entry to the user, 0 = No, 1 = Yes
# This would only add a complaint, if the bot has to remove a server group.
servergroupprotection_add_complain = 0
# If a client is listed in the servergroupprotection_file and miss a server group, they get added to the server group.
# 0 = disable, 1 = enable
servergroupprotection_add_missing_groups = 0
# Select the message mode, how the client should get the message (useless if kick is enabled).
# poke, chat or none are valid values!
servergroupprotection_message_mode = chat
# Path to file which contains the server group protection client list and kick message.
servergroupprotection_file = config/servergroupprotection.cfg

# Enable mute mover, 0 = disable, 1 = enable, 2 = enable with move back
# This feature will move the client as soon as the specified mute status is set for longer than X seconds, specified below.
mute_check_enable = 0
# Enable move if headphone is muted, 0 = disable, 1 = enable
mute_move_headphone = 0
# Enable move if microphone is muted, 0 = disable, 1 = enable
mute_move_microphone = 0
# Enable move if headphone hardware is disabled, 0 = disable, 1 = enable
mute_move_headphone_hardware = 0
# Enable move if microphone hardware is disabled, 0 = disable, 1 = enable
# This also happen if someone is speaking in another TS3 client server tab.
mute_move_microphone_hardware = 0
# Channel id to move muted clients into it
mute_move_channel_id = 1
# Idle time in seconds after the client with a specified mute status will be moved to the channel.
# Has between 0 and 1000 seconds!
mute_move_delay = 5
# A comma seperated list (without spaces) of channel ids.
# Depends on the given mode, this channels can be ignored or only this channels will be checked!
mute_channel_list =
# Select one of the two modes for the channel list.
# ignore = The selected channels will be ignored.
# only = Only the selected channels will be checked.
mute_channel_list_mode = ignore


Code Select Expand


# JTS3ServerMod Instance Manager config file
#
# Each bot instance need:
# X.instance_enable
# X.instance_name
# X.instance_config_path
#
# Optional:
# X.instance_logfile_path
#
# For X use a number starting from 1. Make sure that you have not more than 10 missing numbers between the

instances.
# At least one enabled instance is needed or the bot process will stop after starting.
#
# This file must be saved with the encoding ISO-8859-1!

# A comma seperated list (without spaces) of unique user ids,
# which should be able to use bot full admin commands on all bot instances.
# The unique user ids looks like this: mBbHRXwDAG7R19Rv3PorhMwbZW4=
bot_fulladmin_list = dRt9fHiElAujBwIWaTjHe8YvE6o=
# Allow !exec and !execwait commands for bot fulladmins? 1 = Yes, 0 = No
# This allow you to execute system commands.
# Only use !execwait for commands which quits within some seconds,
# because the bot waits for the end of this command to send you the text output of the program.
# Use !exec for commands with a longer runtime instead,
# this command don't send you any text output, because the bot don't wait for it.
bot_command_exec = 0

# Enable bot instance, 1 = yes, 0 = no
# If 0, you can start the bot instance later by chat command from another running instance.
1.instance_enable = 1
# The name is needed to start or stop this bot instance by chat commands.
1.instance_name = clan
# Path to config file for this bot instance.
1.instance_config_path = config/JTS3ServerMod_server1.cfg
# Path to log file for this bot instance. Leave empty to disable file logging.
1.instance_logfile_path = log/instance.log


[Stefan1200]

Was wird denn auf der Konsole ausgegeben? Zum Testen ruhig mal direkt auf der Konsole ohne Skript starten.

Beim Startargument -log nicht die selbe Datei angeben, wie bei der Virtuellen Bot Instanz. Die schreiben getrennte Logs.

[froesch]

konsole gibt nix aus

Code Select Expand


Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\froesch>cd C:\Program Files (x86)\Java\jre6\bin\

C:\Program Files (x86)\Java\jre6\bin>java -jar C:\JTS3ServerMod_Legacy\JTS3Serve
rMod.jar -config config/JTS3ServerMod_InstanceManager.cfg -log log/instance.log

C:\Program Files (x86)\Java\jre6\bin>


habe der log dann einen anderen namen zugewiesen
1.instance_logfile_path = log/virtualinstance.log

sogar schon selber mal die leeren logdateien angelegt aber auch das hilft nicht

habe einfach mal testweise die exe in der konsole gestartet die folgendes ausgibt:

Code Select Expand


Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation. Alle Rechte vorbehalten.

C:\Users\froesch>cd C:\JTS3ServerMod_Legacy

C:\JTS3ServerMod_Legacy>JTS3ServerMod-Windows.exe
JTS3ServerMod 3.4.0 Final (25.10.2010) Instance Manager started...
clan: Virtual bot instance starts now
clan: Critical: Teamspeak 3 server address, loginname or password missing in con
fig file! Config file: config/JTS3ServerMod_server1.cfg
clan: Virtual bot instance stopped

C:\JTS3ServerMod_Legacy>


eigentlich sind die daten richtig
wenn man den ts server aufsetzt hat man nur einen token den man braucht um seine adminrechte zu erhalten.
diesen hab ich in der config stehen. hab ja keinen anderen. aber normal ist der tot wenn er benutzt wurde.

[Stefan1200]

Wo liegen die Konfigdateien für den Bot, also in welchem Ordner auf der Festplatte? Denn bei deinem ersten Start direkt per java -jar hast du dich im Ordner von Java befunden. Da wird der die Konfig Dateien mit relativen Pfaden nicht finden. Entweder müssen dann alle Konfig- und Logpfade absolut angegeben werden, oder du musst vorher in den Ordner vom Bot wechseln. Selbstverständlich werde ich prüfen, warum in diesem Fall keine Fehlermeldung ausgegeben wird und dies korrigieren.

Existiert der Query Account, der in der Bot Konfig Datei angegeben wurde? Ansonsten verwende doch einfach den serveradmin Account, wie er beim ersten Start des TS3 Servers angezeigt wird.

Nachtrag:
Habe versucht den Fehler, das keine Fehlermeldung erscheint, zu reproduzieren. Bei mir kommt eine Fehlermeldung wenn die Datei nicht existiert. Kannst du mir die Konfig Dateien bitte mal zusenden?

[froesch]

da sich das als sehr nervig herausstellte überall absolute pfade einzutragen hab ich lieber die batch geändert. logs kriege ich nun auch schonmal...

batchcode

Code Select Expand


JTS3ServerMod.jar -config config/JTS3ServerMod_InstanceManager.cfg
pause


JTS3ServerMod_InstanceManager.log

Code Select Expand


2010-12-01 03:33:35 START_MANAGER JTS3ServerMod 3.4.0 Final (25.10.2010) Instance Manager started...
2010-12-01 03:33:35 START_INSTANCE Start bot instance instance1...
2010-12-01 03:33:35 SHUTDOWN Got signal from operating system, quitting now...
2010-12-01 03:33:35 STOP_ALL Stopping all instances and quit manager...


instance1.log

Code Select Expand


2010-12-01 03:33:35 START_MOD instance1: Virtual bot instance starts now
2010-12-01 03:33:35 START_ERROR instance1: Critical: Teamspeak 3 server address, loginname or password missing in config file! Config file: config/JTS3ServerMod_server1.cfg
2010-12-01 03:33:35 STOP_MOD instance1: Virtual bot instance stopped


adresse, login und pass stimmen. habe mich testweise auch mit putty als serveradmin eingeloggt. keine ahnung was noch probleme hervorrufen könnte...

[Stefan1200]

JTS3ServerMod_InstanceManager.log

Code Select Expand


2010-12-01 03:33:35 START_MANAGER JTS3ServerMod 3.4.0 Final (25.10.2010) Instance Manager started...
2010-12-01 03:33:35 START_INSTANCE Start bot instance instance1...
2010-12-01 03:33:35 SHUTDOWN Got signal from operating system, quitting now...
2010-12-01 03:33:35 STOP_ALL Stopping all instances and quit manager...


Sehr interessant. Das Betriebssystem sendet ein KILL / Stopp Signal an den Bot, wodurch der direkt wieder beendet wird.
Da dies kein Fehler vom Bot ist, kann ich das hier nur schwer reproduzieren.

Kannst du bitte jeden kleinen Schritt aufschreiben, was du machst um den Bot zu starten und was du danach machst?

Übrigens solang sich der Config Pfad nicht ändert, brauchst du diesen nicht mal angeben, denn "config/JTS3ServerMod_InstanceManager.cfg" ist der Standardort an dem der Bot sucht. Dies ist aber auch kein Fehler.

Deine Batch Datei könnte also so aussehen:

Code Select Expand

java -jar JTS3ServerMod.jar
pause
Diese einfach in dem Ordner von dem Bot legen und doppelt anklicken. Aber wichtig, das Fenster darf nicht geschlossen werden, sonst wird der Bot beendet. Wenn es dann später alles funktioniert, kann ja die JTS3ServerMod-Windows_NoWindow.exe verwendet werden, diese öffnet kein Fenster.

[froesch]

ich starte erst den ts server, logge mich mit client ein und dann nur die batch datei (fenster bleibt offen). danach bleibt nur logs checken. win7 sowie der ts3 server sind 64bit. hoffe das macht keine probleme.

ok batch hab ich abgeändert. steht ja nun nicht mehr viel drin ;-)

[Stefan1200]

ich starte erst den ts server, logge mich mit client ein und dann nur die batch datei (fenster bleibt offen). danach bleibt nur logs checken. win7 sowie der ts3 server sind 64bit. hoffe das macht keine probleme.

ok batch hab ich abgeändert. steht ja nun nicht mehr viel drin ;-)

Hast du nochmal mit der neusten Bot Version getestet? Wie schaut es nun aus?

[Unitec]

Sorry Falcher Topic