Versions / environment
- TeamSpeak 3: 3.6.2
- TeamSpeak 6: 6.0.0 Beta 3.4
- OS: Windows
Summary
There appears to be a difference in how TeamSpeak 3 and TeamSpeak 6 parse/normalize the path parameter in ts3image:// URLs used in BBCode [IMG].
In practice:
- TS3 works with
path=/Banners(no trailing slash) but TS6 fails - TS6 works with
path=/Banners/(trailing slash) but TS3 fails
This makes it impossible to post a single [IMG] ts3image://... tag that works on both clients, which breaks backward compatibility.
Reproduction (100% reproducible)
Case 1 — Works on TS3, fails on TS6
[IMG]ts3image://v6-1-3.gif?channel=10&path=/Banners[/IMG]
TS6 log:
[2026-02-17 17:02:45.246] [info] Error opening file "C:\Users\Hannib\AppData\Local\TeamSpeak\Cache\Default\images\443859304d596c7376326b4447564b38755772765256616d6c525578772f555a792f615268426c6c7056453d\10/Banners\v6-1-3.gif": The system cannot find the path specified.
Case 2 — Works on TS6, fails on TS3
[IMG]ts3image://v6-1-3.gif?channel=10&path=/Banners/[/IMG]
TS3 log:
17/02/2026 21:30:12 Info Failed to read image C:/Users/Hannib/AppData/Roaming/TS3Client/cache/remote/LwWmaxwocv7DJ410zAKBvYAJwwmOE7YVYeaRyD+6kJUS79ZP1dPqo+ujoOj5_B+vaFFOmKrSiEzKSVm+gEOSVw==
TS3 client console:
<22:24:58> Transfer "v6-1-3.gif" reports: (invalid file path)
Expected result
For backward compatibility, both clients (especially TS6) should accept both forms:
path=/Bannerspath=/Banners/
(i.e., normalize the trailing slash in path before resolving the cached/local file path)
Actual result
- TS6 fails unless
pathends with/ - TS3 fails when
pathends with/
Impact
Users on TS3 and TS6 cannot share the same ts3image:// image/banners tag reliably across both clients.