1. Рады видеть Вас на русскоязычном форуме TeamSpeak!

    У нас Вы можете скачать последнюю версию:

    Перед регистрацией рекомендуем ознакомиться

    с Правилами форума.

    Присоединяйтесь! Учите и обучайтесь!

    Скрыть объявление
  2. Новая группа "Новичок" на нашем форуме!

    Новые пользователи будут попадать в группу "Новичок".

    Это сделано для того чтобы "Новички" ознакомились с форумом, так как в большинстве случаев проблема с которой вы хотите обратиться уже обсуждалась.

    Перейти в тему обсуждения
    Быстрый переход в группу Пользователь
  3. VPS/VDS и дедикейт сервера в аренду с DDoS защитой

    • Низкий пинг
    • Действующий SLA
    • Рублевые цены без привязки к курсу валют

    Бесплатный тестовый период VPS-OpenVZ

    Попробовать

Административные YaTQA / Yet another TeamSpeak 3 Query App 3.7.3-beta

"Еще одно TeamSpeak 3 Query Admin приложение"

  1. "Еще одно TeamSpeak 3 Query Admin приложение"

    VJean
    • Changed domain for PlanetTeamSpeak API calls (YaTQA originally had its own subdomain because it doesn’t use SSL and the normal domain used to force SSL)
    • When selecting a value for virtualserver_hostmessage in the console, you can now use the WYSIWYG editor. (YaTQA Pro)
    • Added support for virtualserver_hostmessage to the “What’s This Value?” feature (YaTQA Pro)
    • Added full SSH support (YaTQA Pro)
      • Note: This feature requires plink.exe to be present in YaTQA’s folder (not the configuration one!). YaTQA will download it for you (requires you to run YaTQA as administrator) or guide you to PuTTY’s website. I decided to not ship it with YaTQA because only a few people will need this feature.
      • Note: To begin using this feature, you need to enable it and set up SSH profiles in the settings. If a profile’s and the server’s domain name match, the configured SSH tunnel is used. The way this is done is targeting ATHPs who sometimes have multiple instances on a server, so they only have to set up SSH tunnelling once per server. Additionally, I don’t want any more input boxes on the start screen and parameters for the -c command.
    • Added note to user graph saying that a timeframe of more than today and yesterday (UTC) requires a registration on PlanetTeamspeak.com
      • Note: There is currently no such registration. However, PlanetTeamspeak’s server and the official test server count as registered.
    • Added changing your meta data to self menu

    • Fixed a bug that caused empty results in SSH tunnel mode to cause one phantom result (with all strings empty and all numbers -1) [superseeded by the next change]
    • Set telnet to character mode instead of line mode, removing the limit of 4095 bytes per command (easily exceeded by restoring snapshots and some mass permission editing functions) and fixing the ambiguity of SSH returning all the input
      • Note: There is still the limit of 9203 bytes (strange number in a computing context) per command from TeamSpeak’s side (which I just got to know on 16 Jul). However, 13 of the 141 commands are allowed to exceed this: serversnapshotdeploy and the addperm/delperm commands. While it is important to have it here, there are more commands where it is very nasty. Especially channeledit/channelcreate. The following functions can be affected: permfind, permoverview, permget and permidgetbyname; ftdeletefile (affected in YaTQA, but rather unlikely) and ftgetfileinfo; clientmove/clientkick (both are affected in YaTQA, but you must be moving more people at once than even an NPL can handle).
    • Major internal changes to RedeemerTS3T
    • SSH now connects to 127.0.0.1 instead of localhost (some servers don’t appear to have this linked and it might also prevent telnet from running in IPv6 mode which is unsupported by the TS server)
    • Added feature to the console’s input box’s context menu that allows you to load a file of commands, edit it and then execute all commands (YaTQA Pro)
    • You can now see if the server whose stats you are viewing is registered on Planet TeamSpeak, allowing 31 days of statistics instead of just today and yesterday
    • Added link to this registration if required (unless the feature is running stand-alone)
    • Clicking the title now takes you to your server’s page on Planet TeamSpeak
    • Added a note to the window caption saying that you can save that chart
    • Updated registration info text to include the features added in 3.2 and 3.3
    • Installing plink.exe from YaTQA’s settings window now requires you to accept its license terms
    • Added joining and leaving all server groups
    • Fixed a bug that prevented changing one’s description via the Self menu from working
    • Fixed a bug that caused the channel kick event to lack the target channel
    • Added missing shortening of the machine ID
    • Global Select All hotkey now works with edit boxes and memos (workaround for a bug that exists for Windows XP only?); the corresponding functionality for WYSIWYG editors is provided by Windows
    • Fixed a bug that caused YaTQA to repeatedly load the icon cache from disk when visiting the virtual server stats tab after having selected the server by port or ID
    • Did some checks before loading sort settings (even though this happened to someone, I have no idea how it did that)
    • Unified some function that selected a server
    • Fixed a bug that caused deploying a snapshot with a file backup to select the created server twice
    • When creating a new server with the snapshot from a file backup, the name is now given in the top bar (because we had to retrieve a server list for creating the server anyway) and in this case YaTQA no longer has to switch the tab to retrieve the server UID.
    • Fixed a bug that prevented editing multiple servers from saving the selection
    • Added server template to mass editing
    • When restoring a channel tree, YaTQA now add the description via an additional command if the channelcreate command would be longer than 9203 bytes
    • Added missing autoresizing of the list view columns in the window for selecting multiple servers and fixed the same feature for the server groups window (they both now work in the same way as it has always been done for mass snapshot creation)
    • Added a feature to add multiple channels at once with an option to keep their settings and permissions
    • Added a feature to move multiple channels at once
    • Fixed a bug introduced with multi channel edit that prevented users from moving channel to the base level
    • Added custom parameters for plink.exe
    • Fixed missing server group names in error messages when assigning server groups via the server group window failed
    • If permission import runs in debug mode and you choose to exit after an error, the displayed information is updated like after a success
    • Replaced the Ignore/Abort buttons for error messages shown during the last (or only) item of most multi-target functions (e.g. deploying snapshots, creating channels) by a OK button and added an explanation (this was especially confusing if you selected only one item and it failed)
    • Made clear in the console's parameter help that the tokenid2 parameter for tokenadd/privilegekeyadd must be 0 for server groups (YaTQA Pro)
    • Improved the handling of the backspace key in console (YaTQA Pro)
    • Fixed a bug that caused some strange error messages when trying to select a value for UID-type parameters in the console caused by YaTQA not using the -uid for clientlist switch to actually retrieve the UIDs (YaTQA Pro)
    • Server tree now treats text without surrounding blanks as identical when renaming channels or yourself
    • Added character/byte limits for most strings input boxes as well as the WYSIWYG editor (because of complex calculation, this is not a hard limit but displayed on the right end of the toolbar if you wait for a fraction of a second for it to recalculate)
      • Note: This also applies to the console as long as the parameters are unique. Some parameters however are ambiguous and will not be limited:
        • name: groups (30 characters) and ban target (255 UTF-8 bytes)
        • msg: pokes (100 characters) and text messages (1024 UTF-8 bytes)
        • message: complaint (200 characters) and offline messages (4096 characters)
    • Increase time limit to include up to February 2016 (if all of the above are included)
    • For renaming stuff in the channel tree and setting a default nickname (but not the phonetic one), YaTQA now removes leading and trailing spaces (including non-breaking space) like the client does
    • Registration window now also removes leading and trailing non-breaking spaces

    This will most likely be the last version for a some months because of personal things and the lack of good feature requests.

    • Added a feature to start browsing the log from a certain position backwards by clicking in the diagramm
    • Fixed a bug that caused the ticks in the diagramm to be placed every 10 KB instead of the 10 KiB mentioned in its hint
    • Changed the text in the “Servers” tab when autostart slots cannot be determined (because not all are currently running) from 3 to only 1 question mark
    • Changed the “Servers” tab’s “in use” statistics’ descriptive labels into images to make more room for numbers of up to 6 digits (hover the icons for explantation of the icons)
    • No numbers are displayed in the “Slots” column now if server is offline (affects “Servers” tab as well as the mass snapshot and server editing windows)
    • Mаde local TS3 Client cache and chats accessible for any server via invitation link with server UID (via the “Home” tab’s left menu)
    • The TSDNS resolver can now be minimized if started from command line.
    • Added feature to change your channel to the “Self” menu (instance “Misc” tab)
    • Changed icon for “Away” in server tree view to one that’s similar to the official client’s one (the channel commander status is now displayed as the color of the clock)
    • Fixed missing translation for: new message when processing one of many items failed, new subtitles of Planet TeamSpeak statistics
    • Changed link in Planet TeamSpeak stats to say “Claim” instead of “Register” (which was a verbal translation from the term that is used in the German version caused by a lack of a good translation for “claim”)
Вернуться к списку обновлений...