YaTQA Changelog
Starting in early 2015, YaTQA development consists of major releases released in January/February and July/August each year. The reason for this schedule is explained here.
This changelog lists changes to the most recent major release (released in February and August each year) and its smaller releases, as well as coming updates. For the latter, this text is sometimes not being updated for some weeks, especially while development happens primarily on my laptop. Additionally, it is possible for some changes to not be in the development snapshot from the FAQ yet.
Older changelogs can be found in the archive and there’s also a log with only the changes in the engine.
Summer Release 2017
3.7.3-beta (17 Jun 2017)
- Added a feature to Users tab to change a user’s channel group in every selected channel (e.g. make that user channel admin)
- When creating new channels, you can now copy permissions from a channel but not copy (normal) channel properties.
- When creating a new channel, you can now copy non-default channel group memberships from a channel.
- Fixed a bug that caused YaTQA to copy channel permissions from the channel selected in the tree rather than the channel selected in the channel creation window
- When creating new channels, channel names are checked for length and collisions.
- When creating new channels, empty lines and leading/trailing whitespace characters are now ignored.
- Made the BBcode encoder use the names for the following colors, as they are shorter than the corresponding hex color codes: azure, beige, bisque, brown, coral, gold, gray (an encoder only needs to know one of the two spellings), green, indigo, ivory, khaki, linen, maroon, navy, olive, orange, orchid, peru, pink, plum, purple, red, salmon, sienna, silver, snow, tan, teal, tomato, violet, wheat.
- Moved file list feature to unregistered version
- Changed update checker link to a another domain because I cannot turn off logging on the webspace used before (I hate logging and wanted to keep that consistent with yat.qa which doesn’t have any logging either)
- Added Android beta 3.1.3 (3.1.2.2 is not available for selection because selecting it would block every other version of TeamSpeak released prior to 2170)
- Fixed channel creation window not closing on OK
- Moved the spawning point of the permission editing popup menu in permission comparison a few pixels, so triple-clicking will open the window to edit the permission
- Added progress and cancel feature to executing multiple custom commands
- Added support for downscaling high-res icons
- Note: SVG support is set to be added at a later time, I still have to think about how to add it. Maybe I won’t even add it.
- Added 3.1.5 beta versions
3.7.4-beta (10 Aug 2017)
Skipped 3.7.3-final because of beta client release today.
- Added some more client versions
- Added preliminary support for Blacklist2 (found in Servers tab context menu)
- Added support for server nicknames
- Note: The Blacklist2 feature uses a tunnel server because YaTQA does not support HTTPS whereas the nickname feature does not use a tunnel server, although it does use HTTPS as well. The reason for this is that the query for nicknames is so simple that I can use a Windows function for it, that saves the result in a file (
servernickname.txt
in your INI’s folder).
- Note: The Blacklist2 feature uses a tunnel server because YaTQA does not support HTTPS whereas the nickname feature does not use a tunnel server, although it does use HTTPS as well. The reason for this is that the query for nicknames is so simple that I can use a Windows function for it, that saves the result in a file (
- Added four more client versions
3.7.4-beta2 (11 Aug 2017)
- Added new badges
- Added feature to download a certain number of log lines (given in iterations of
logview
command, equivalent to hectolines) - Added support for new SSH host keys (YaTQA Pro)
- Improved error texts in SSH mode (YaTQA Pro)
- Added copying
ts3image
andts3file
links - In the menu that appears when attempting to change an already set Host Banner and Host Button graphics, the View feature now supports the
ts3image
protocol - Added the port of the checked server to the Blacklist2 result message
Thanks to a fellow user, I could update the Blacklist2 API tunnel to support greylisting. This is a serverside change and needs no update. Please report running servers blacklisted on Blacklist2.
3.8-pre (14 Aug 2017)
- Fixed Blacklist2 menu item not being disabled when there wasn’t one server selected
- Added feature that displays all users who currently have client or channel client permissions alongside with a list of permissions they have
- Fixed Blacklist2 not working when connected to an IPv6 address without using a domain name
3.8 (21 Aug 2017)
- Added new client versions
- Added features to the new user permissions list to select all users, server permissions or channel permissions
- Internal changes to handling list selections
- Significantly improved performance of the Ctrl+A shortcut
- Increased time limit to include up to February 2018
- Major SSH tunnel rework: Removed requirements for
telnet
andbash
and improved performance.
Autumn/Winter Release 2017/18
3.9-beta (23 Aug 2017)
- Fix BBCode/X-Pixmap color interpretation for six-digit hex codes
- Added SVG support
- Note: YaTQA uses a minimalist SVG engine I made for fun in the last few days. That explains why the download got only 24 KiB bigger and the extracted file is only 90 KiB more. Most of which is most likely the table of XML entities. RedeemerSVG is currently in beta, but should give you nice results for most SVGTiny 2.0 images (SVGTiny 2.0 is also the level supported by TeamSpeak). Notable features that are not supported and will most likely never be:
- Partial transparency
- Gradients (only draws first stop color)
Arc(full support added in 3.9-beta5), Catmull-Rom and Bearing commands- Animations (I don’t think that supported by TeamSpeak either)
- Note: YaTQA uses a minimalist SVG engine I made for fun in the last few days. That explains why the download got only 24 KiB bigger and the extracted file is only 90 KiB more. Most of which is most likely the table of XML entities. RedeemerSVG is currently in beta, but should give you nice results for most SVGTiny 2.0 images (SVGTiny 2.0 is also the level supported by TeamSpeak). Notable features that are not supported and will most likely never be:
3.9-beta2 (26 Aug 2017, unreleased)
This update likely broke SVG support in the Windows XP image selection windows. (Image format support is determined by the operating system on newer versions of Windows.)
- Updated RedeemerSVG to 0.2b-alpha with compatibility and huge performance improvements
3.9-beta2b (01 Sep 2017)
- Updated RedeemerSVG to 0.2b-alpha with compatibility improvements
3.9-beta3 (10 Sep 2017)
If the beta2 series broke SVG support on Windows XP, this update fixed it.
- Fixed a bug that prevented users from keeping the keypair when a new server had to be created (as a workaround for older versions, please use the 1-slot server that is still being created and try again)
- Updated RedeemerSVG to 0.3-alpha with compatibility improvements and some performance improvements as well
3.9-beta3b (unreleased, 23 Sep 2017)
- Optimizations in my custom image formats support classes
3.9-beta3c (30 Sep 2017)
- Fixed a lot of memory leaks
- Optimizations
3.9-beta4 (should have been released on 14 Oct 2017)
- Fixed setting channel icons with a name of 2 Gibi and more in server tree
- Fixed a bug that prevented users from joining IPv6 hosts accessed by hostname
- Fixed a bug displayed the chat input box if one tried to add a new chat target but clicked on Cancel in the target selection window (YaTQA Pro)
- Fixed a bug introduced in 3c that casued a freeze when using most features that “change” something
- Updated RedeemerSVG to 0.4-alpha with compatibility improvements
3.9-beta5 (17 Oct 2017)
- Updated RedeemerSVG to 0.5-beta with compatibility improvements
- Updated badges (new 4Netplayers badge and updated GC2017 description)
YaTQA 3.9-rc will be released within a few hours/days after the release of the TeamSpeak server 3.1 beta. 3.9 final will come with the final server and will likely be the final Winter Release 2018. 4.0 will likely be the final Summer Release 2018. I consider removing registration again in the final 4.0 release.
3.9-beta5b (05 Nov 2017)
Since 4 Nov 2017, YaTQA is now officially tested on Windows 10. The device is a GPD Win.
- Fixed incomplete list of server groups when choosing a value for the
sgid
parameters (YaTQA Pro) - For timeframes displayed in several places, units are no longer displayed if no larger unit is in use either (e.g. 60 seconds will display as “1m 0s” now instead of “0d 0h 1m 0s”)
- Uptime column in Servers tab aligned to the right
- Removed uptime from offline servers
- Fixed a bug that prevented parsing of custom query command results and notify events when viewing their parameters (YaTQA Pro)
- Fixed a bug that showed a scroll bar in that window (YaTQA Pro)
- When searching for clients by their last nickname, the client DB now uses an undocumented feature to display more information without having to query each client for more information than just the
cldbid
. - Some text improvements related to that feature
- Improved description of anti-flood tick reduce property
- Fixed text result window not closing with Esc if input box had the focus
- Pressing Enter in console with no input now displays the last command’s result.
- Using the console’s “Choose a value” feature for the
apikey
parameter now inserts your API Key (YaTQA Pro). Other than for all other parameters, there is no confirmation or something, it just inserts the key. - Small offline message related typo fix (German version only)
- Fixed some interface images not loading in non-Aero mode
- Fixed from issues with the Refresh menu in the server tree (not YaTQA Pro)
- Fixed missing translation in Clients With Permissions context menu
- Fix Details button in users DB not updating list
- Channel groups by clients tab: Context menu disable
- Completely redesigned the dialog that lets you choose a client after entering an ambiguous client nickname (or used wildcards)
- Updated RedeemerSVG to 0.5b-beta with compatibility and stability improvements
3.9-beta5c (19 Nov 2017)
- Building the client cache server list now takes the
cache
’s subfolders into account, not just the ones inchats
(so YaTQA now works with all chat logging disabled, though no server names will be displayed) - Fixed handling of unexpected subfolders in those folders
- Updated parameters in autocomplete (YaTQA Pro)
- Removed flags that ip2location cannot return (flags were originally made to support Maxmind, not knowing that TeamSpeak actually uses ip2location)
- Changed flag of Saint-Barthélemy and Saint-Martin to be the same as France’s (previously, the flag of the respective Municipality was displayed)
- Added a feature to show users details for the All Client Permissions feature
- Some small fixes for the All Client Permissions feature
- Adjusted security level computation estimations to the current client’s (some higher durations were linked to higher levels, though Moore’s Law would imply lesser levels)
- Fixed a lesser glitch with that window’s up-down control
- Improved readibility of debug log in non-tunnel mode (like in tunnel mode, the log no longer includes carriage returns)
- If the received text window’s memo box has the focus, the window now closes as soon as you hit Esc, not as soon as you release it.
- Added Rocket Beans badge
- Changed default sort of Client Cache server list from name ascending to last modified date descending
- Fixed marking of query groups in Select window being displayed incorrectly
- Changed default DNS resolver server from Google to Quad9
- Note: YaTQA uses Quad9’s unsecure mode (which does not block malware websites) because false-positive blocking of a domain will be annoying and confusing for users. Only TSDNS servers could attack YaTQA (because they are the only non-DNS connection in that feature), but it’s unlikely that a) people will write a malicious TSDNS server b) secure Quad9 will make a difference and block it and c) YaTQA has any security issues because it only displays a string and does not execute any code.
- Fix Client Cache avatar list failing with illegally large and SVG avatars
- Updated RedeemerSVG to 0.5c-beta with small compatibility and stability improvements
- Removed sending a server chat message from offline message tab in order to improve the way offline messages are displayed
- Note: Please send server chat messages from the Users tab.
- Note: The reason why this feature was originally added there was that the Users tab was not yet available in 0.1-alpha and 0.2-alpha, but the offline message tab did exist in these versions.
- Renamed the menu item accordingly
- Changed JN-GAMES logo in About dialog from PNG to SVG
- Note: This is just a first step. The whole application will gradually move to SVG until 4.0. Next things will be the badges, console event types (YaTQA Pro) and OS icons which will be included in some 3.9 version.
3.9-beta5c2 (08 Dec 2017)
- Fixed several bugs/glitches when querying for server nicknames that did not exist
- Fixed console memory leak (YaTQA Pro)
- Fix a bug that causes deploying channel trees to search for channel name collisions globally, when it should only look for path collisions
- Fixed the same bug for creating new channels as well
- Because the “keep keypair” feature’s behaviour is significantly different depending on whether you are on a virtual server or not, the latter situation is set to be renamed to “create new keypair” (YaTQA Pro)
- Instance Misc tab is now cleared when selecting a new server
- Self menu in instance Misc now disappears when not on a server
- Swapped position of Self and Scripts buttons in instance Misc tab
- Added new client version 3.1.7-beta
3.9-beta5c3 (11 Dec 2017)
- Updated params of banclient to match research
- Fixed semaphore bug in case of errors in snapshot deploy (RedeemerTS3A, introduced in 3.9-beta3c)
- Added pseudo snapshot feature
- Note: Pseudo snapshots are snapshots that can be created with the usual Server Admin permission set. They can be used to move a server to a new location, given that you have full permissions on the target instance. If you want to move to an instance where you don’t have full permissions, please ask your hoster to deploy a snapshot for you. If they don’t, choose a host with better service.
- Note: Please note that your UID cannot be retained because the server does not allow retrieving the keypair (for security reasons), so your server identity will change. A high number of commands will be required which will be displayed when you choose the data to include. If all checkbox are checked, there are only two things a pseudo snapshot does not (and cannot) contain: Server identity and each client’s number of unread offline messages. The latter is entirely pointless because snapshots don’t include offline messages either.
- Important warning: These snapshots may not be used outside of YaTQA. They can destroy the target server.
- Fixed snapshot feature broken in beta5c2
- Improved text on deploying/restoring server snapshots (not depends on whether you are on a server or not)
- Added new Android version 3.1.7 (beta?)
3.9-rc1 (21 Jan 2018)
It is recommended to use this version with servers updated to 3.1.0, even though the only additions that require it are a new permission and a new virtual server property.
- Fixed pseudo snapshots not working with minimal channel details
- You can now choose whether you want the client DB included or not.
- Changes in the pseudo snapshot window to match the last change
- Internal changes to RedeemerTS3 (error handling is no longer overridden in RedeemerTS3P)
- YaTQA now ignores accounting errors (e.g. not enough slots, not enough virtual servers) when deploying snapshots.
- Fixed incorrect displaying of some info when overwriting servers with snapshots, deploying a pseudo snapshot or (in YaTQA Pro) creating a new server with a new keypair
- Fixed a recently-introduced bug that truncated the last character in an event notification
- Fixed MIFCOM badge not displaying its description properly (Delphi uses the vertical bar to divide hints into short and long hints, so the Latin letter dental click is used instead now)
- Fixed semaphore bug with
permidgetbyname
when finding unused icons or looking up a permission in the console (RedeemerTS3A, introduced in 3.9-beta3c) - Added new client versions
- Internal changes to SHA1 and Base64 functions
- Added entering the new server nickname (3.1.0 required)
- Fixed “Set all power permissions” menu item not being disabled if the list was empty
- Updated permissions to version 20 (added nickname)
- Removed limit of 3 badges (only works on client version 3.1.8-beta1 or older, newer clients however will display only the first 3 badges)
- Now uses Windows’ SHA-1 features in advapi32.dll (available under Windows XP as well)
- Added note to pseudo snapshot window that these snapshots are for use with YaTQA 3.9-beta5c or newer only (registered users of the older version
- Added a feature to change the password of server and channels when your server snapshot would be deployed with another keypair (wish was used to salt the hashed passwords stored in the snapshot)
- Updated copyright year
- Some small visual improvements to badges window (significantly larger now as we have more badges)
- Replaced the question window about disabling timeout with a checkbox
3.9 (15 Feb 2018)
- Fixed joining servers to a certain channel
- (RedeemerTS3) [Test/Debug] Added a possible fix for YaTQA becoming unresponsive when shutting down the operating system
- (RedeemerTS3) [Test/Debug] Internal changes, maybe fixing some issues when connecting to localhost on some systems
- Fixed a bug that limited names of copied groups to 30 UTF-16 entities rather than characters (only affects entering non-BMP (UCS-2) characters)
- Note: Group names are the only (known) place where the TeamSpeak server has full Unicode support. Other functions will remove non-BMP characters prior to doing anything.
- Note: The bug fixed here also exists in the client, with the difference that the client’s clipping behaviour of too long strings is non-standard (produces a half surrogate entity, which doesn’t make any sense).
- Note: This bug was also fixed everywhere else, however, entering non-BMP (UCS-2) characters won’t make any sense when YaTQA is used with TeamSpeak, as it doesn’t support them there.
- Note: This bug did not exist when renaming groups (and also did not exist for creating new groups due to another bug which prevented new groups’ names from being checked, see next change).
- Fixed a bug that prevented the max length check from affecting the names of new groups to be created
- Updated server version below which YaTQA will suggest an update to 3.1.0-final
- Updated client versions
- Removed client versions not compatible with 3.1.0 server (3.1.7-beta is not compatible, 3.1.7 is)
- Increased time limit to August 2018
3.9b (18 Feb 2018)
- Fixed client details not updating
- Fixed client details always updating on window resize
- Fixed position of text in the right status box in client details
- Fixed overwolf status not displaying in client details
- Fixed incorrect scaling of large portrait (h < w) icons
- Fixed incorrect scaling of the alpha channel of PNG mode 4 (grayscale alpha) images
- Changed operating system icons to SVG files (Apple is from Wikipedia, the rest I drew myself)
3.9c (19 Feb 2018)
- Fixed error when loading uncached icons in Users tab
- Replaced badges with their SVG versions
3.9d (01 Mar 2018)
- Fixed typecast error when copying groups
- Updated supported server version
3.9e (02 Mar 2018)
- Fixed error with badges in Users tab
- Fixed a bug that incorrectly calculated the text length when replacing a selected max length text in input boxes (or in case of the default query client nickname, exceeds the max length by far)
3.9.1-beta (15 Mar 2018, unofficial release, snapshots only)
- Fixed blacklist2 check (serverside change, affects all blacklist2-enabled versions without the need for an update)
- Added support for more details in blacklist2 check (you can now how the server is blacklisted, e.g. by IP or domain/nickname)
- Completely changed the file transfer system (internal change only, please report possible bugs)
- Fixed a bug that when you tried to download multiple files from the Users tab, among which were uncompleted uploads, they were’t downloaded but added to the queue size (incomplete files cannot currently be added)
- Added feature to file list / file backup window to download a file
- When doubleclicking a non-image file in the file list window (not in file backup), downloading it is now the action for non-image files (instead of previously just displaying an error that made no sense).
- Fixed strange error message when trying to open a local file backup file with no extension (now simply nothing happens if you try that)
- Updated blacklist2 result message
- ––– German development snapshot updated here, see below for download –––
3.9.2-beta (TBA)
- Updated blacklist2 result message
- Several big changes in the RedeemerTS3 engine for easier inheritance and adding of different
- Pseudo Snapshots now work without
permissionlist
permission - ––– English development snapshot [“testing” folder] updated here, see below for download –––
- ––– internal progress until here –––
- Made auto refresh work better with slow connections (interval now resets)
- Add blacklist2 check to serverinfo tab
- Add button to copy server UID
- Fix incorrect display (or only scaling?) of indexed transparent PNGs
Roadmap
There are plans from TeaSpeak to include SSL/TLS. Adding support for that requires me to purchase quite an expensive Delphi extension (upper three digits in euros) will make YaTQA around 80% bigger. I’m not sure if I want to do that solely for TeaSpeak. I might add preliminary support that requires OpenSSL until TeamSpeak maybe adds a similar feature. I plan to be able to make a decision here before the release of the 2018 Summer Release.
4.0 is set to change the design to a line-based design. I’m currently working on the design and evaluate the need for purchasing some of the required icons. Icon dimensions will increase by 20% (32 to 38 pixels). The default width will increase by 48 pixels. The font will change to Segoe UI (which is wider than Tahoma and therefore couldn’t be used before).
5.0 will change YaTQA to support high-DPI displays.
You can download development snapshots in German and sometimes English.
The German snapshot (without the suffix) is updated more frequently than the English one, because the original language of YaTQA is German and the translation is only created periodically. The date given on the linked website is the date the file was either compiled or updated (depending on the software I used for uploading it) in German time. Snapshots can sometimes be older than the current stable release. The last upload of each snapshot is also listed in the changelog.
Sometimes, snapshots are a bit bigger than the release versions because they contain some stuff that is useless for stand-alone applications and therefore removed before release (see here for technical details). I also remove the ugly default images as YaTQA uses its own ones, which are prettier.