Forum

Page 66 of 140 FirstFirst ... 1656646566676876116 ... LastLast
Results 976 to 990 of 2089
  1. #976
    Join Date
    December 2009
    Location
    Germany
    Posts
    2,354
    Quote Originally Posted by Ar2rJke View Post
    Here I would like to know specifically what you want to replace that overwrite that change that correct, edit, etc. Or, you can easily replace .jar and all?
    If there are any changes needed, they will be always written in the changelog file. In most cases it is enough just to replace the JTS3ServerMod.jar file.

  2. #977
    Join Date
    October 2010
    Location
    Poland
    Posts
    1
    Hi Stefan1200. Could you add to "Added Server Group Notify function. If clients from a specified server group joins the server or specified channel, all members of selected server groups get an information by chat or poke message"?

  3. #978
    Join Date
    June 2012
    Posts
    29
    hi stefan
    I m having difficulties with idle mover function. It doesnt move idle clients. picture and settings. might help

    can u help me?
    http://img580.imageshack.us/img580/1...1206102227.png
    Code:
    # Config file of the JTS3ServerMod
    # http://www.stefan1200.de
    # This file must be saved with the encoding ISO-8859-1!
    
    # Teamspeak 3 server address
    ts3_server_address = localhost
    # Teamspeak 3 server query port, default is 10011
    ts3_server_query_port = 10011
    # Teamspeak 3 server query admin account name
    ts3_server_query_login = asd
    # Teamspeak 3 server query admin password
    ts3_server_query_password = asd
    # 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.
    # Don't set the default channel here, because the bot is already in the default channel after connecting.
    bot_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 client auto move, bad channel name check, server group notify, 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. Values between 1 and 30 are allowed.
    # If slow mode is activated, 3 is the lowest possible value.
    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, 0 = Disable
    bot_clientdblist_cache = 1
    # Server Query name, this will be displayed as name of the connection.
    bot_server_query_name = Shootem Up Koruma Botu !
    # 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 = Shootem Up Koruma Bot2 !
    # 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: 
    bot_admin_list = 
    
    # Allow !lastseen command for all clients? 1 = Yes, 0 = No
    command_lastseen = 0
    
    # 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 = 2
    # 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 = 13
    # 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 = 2
    # 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 = 13
    # 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 = only
    # 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 = only
    # 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 = 1
    # 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 = 2
    # 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 = 1
    # 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 = 2
    # Channel id to move away clients into it
    away_move_channel_id = 2
    # Idle time in seconds after the client with away status will be moved to the channel.
    # Has between 0 and 1000 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 = only
    # 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!
    away_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.
    away_group_list_mode = only
    # Select the message mode, how the client should get the message.
    # poke, chat or none are valid values!
    away_message_mode = none
    # Path to file which contains the away mover message
    away_file = config/awaymessages.cfg
    
    # 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 = 1
    # 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
    # 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!
    badnickname_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.
    badnickname_group_list_mode = ignore
    # 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
    # A comma seperated list (without spaces) of channel ids.
    # This channels will be ignored!
    badchannelname_channel_list = 
    # 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 = 2
    # Enable move if headphone is muted, 0 = disable, 1 = enable
    mute_move_headphone = 1
    # 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 = 1
    # 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 = 1
    # Channel id to move muted clients into it
    mute_move_channel_id = 13
    # 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
    # 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!
    mute_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.
    mute_group_list_mode = ignore
    # Select the message mode, how the client should get the message.
    # poke, chat or none are valid values!
    mute_message_mode = chat
    # Path to file which contains the mute mover message
    mute_file = config/mutemessages.cfg
    
    # Enable server group notify, 0 = disable, 1 = enable
    # If enabled, this function will notify specified server groups about joining clients in a specified server group.
    servergroupnotify_enable = 0
    # Select the message mode, how the clients should get the message.
    # poke or chat are valid values!
    servergroupnotify_message_mode = chat
    # A comma seperated list (without spaces) of server group ids, which should be watched on joining.
    servergroupnotify_groups = 
    # A comma seperated list (without spaces) of server group ids, which should be notified about joining clients.
    servergroupnotify_grouptargets = 
    # A comma seperated list (without spaces) of channel ids.
    # Depends on the given mode, target clients in this channels can be ignored or only clients in this channels receive the notify message!
    servergroupnotify_channel_list = 
    # Select one of the two modes for the channel list.
    # ignore = Clients in the selected channels will be ignored.
    # only = Only clients in the selected channels receive the notify message.
    servergroupnotify_channel_list_mode = ignore
    # Path to file which contains the server group notify message
    servergroupnotify_file = config/servergroupnotifymessages.cfg
    
    # Enable auto move, 0 = disable, 1 = enable
    # If enabled, this function will move connecting clients of a specified server group to a specified channel.
    # This function ignores clients with an own default channel set.
    automove_enable = 0
    # Select the message mode, how the clients should get the message.
    # poke, chat or none are valid values!
    automove_message_mode = none
    # Path to file which contains the auto move configuration and message.
    automove_file = config/automove.cfg

  4. #979
    Join Date
    December 2009
    Location
    Germany
    Posts
    2,354
    @ fuyaka: Please post the logfile.

    @ Pluciak: Maybe, but not soon.

  5. #980
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204
    hello Stefan1200 You do not tell me whether it is possible to make so that the message that comes from your JTSServerMod it was impossible to close!?

    It would be too convenient.

    If, however, is responsible for this TS developers themselves, you can try to address this to them, and posmtret what they say, because they offer access not only your pronramme, ServerQuery which has an id 1.

    because it gives your program a signal to say ServerQuery and it is a default, and it would not be bad - so that the messages that came from it was impossible to close, the principle of "the default channel" in which the user is - he can not close.

  6. #981
    Join Date
    December 2009
    Location
    Germany
    Posts
    2,354
    @ Ar2rJke: I am not able to understand everything you wrote. But it is not possible to say the client that a message cannot be closed. You can close every message, don't matter the source of the message.

  7. #982
    Join Date
    December 2009
    Location
    Hungary
    Posts
    404
    Hi Stefan,

    We've made a "safe-upgrade" on our Ubuntu 10.04 VPS (we do this every 2-3 weeks), updated TS server to 3.0.6 and now whenever I start the bot (3.6.3) %CPU goes up to 100-150% (both TS server, BOT and other processes). The entire server slows down. If I stop the bot everything runs normal. Very strange and frustrating since I'm running this bot from the first version and I've never experienced such issue. Very strange.

    Can you please assist me to solve this problem? Thank you.

  8. #983
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204
    at me certainly too resources he eats much, well not on so many... always was 0.3% - 0.5% now jump to 10%

  9. #984
    Join Date
    December 2009
    Location
    Germany
    Posts
    2,354
    Are you sure not to run into this:
    http://www.golem.de/news/zeitsprung-...207-92890.html German
    Maybe someone has an english article about that?

  10. #985
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204
    for my part a problem obviously not in it!

  11. #986
    Join Date
    December 2009
    Location
    Hungary
    Posts
    404
    Unfortunately I can't use your bot since new server release. It kills my server.

  12. #987
    Join Date
    December 2009
    Location
    Germany
    Posts
    2,354
    Quote Originally Posted by Slater View Post
    Unfortunately I can't use your bot since new server release. It kills my server.
    What happens?
    Maybe this problem?: http://www.itworld.com/hardware/2846...mbled-internet

    Maybe you will find here something that helps:
    https://access.redhat.com/knowledge/articles/15145

  13. #988
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204
    hello Stefan1200, You did not tell me, if you can follow any responses to edit a parameter
    Code:
    %CLIENT_VERSION%
    %SERVER_VERSION%
    These options work, but it gives build version
    Code:
    3.0.7 Build: [1340260499]
    3.0.6.1 Build: [1340956745]
    Is it possible to fix on this one:
    Code:
    3.0.7 (21.06.2012 10:34:59) on Windows
    3.0.6.1 (29.06.2012 11:59:05) on Linux

  14. #989
    Join Date
    December 2009
    Location
    Germany
    Posts
    2,354
    @ Ar2rJke: Maybe, I look into this someday.

  15. #990
    Join Date
    June 2011
    Location
    Russian Federation
    Posts
    204
    Stefan1200, thanks!

Thread Information

Users Browsing this Thread

There are currently 1 users browsing this thread. (0 members and 1 guests)

Similar Threads

  1. [No Bug] Idle Time even thou people are not idle.
    By brewek in forum Bug Reports [EN/DE]
    Replies: 3
    Last Post: November 10th, 2011, 04:27 PM
  2. [Resolved] JTS3ServerMod server query permission help
    By n406c in forum Permission System
    Replies: 2
    Last Post: April 1st, 2011, 11:08 PM
  3. Replies: 4
    Last Post: January 9th, 2011, 03:58 AM

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •