TS 5: Feature requests (collection thread)

[Rokolell]

It'd be really useful if you could use Teamspeak on devices like the Raspberry Pi which is ARM based but there are no ARM TS builds... so some ARM support for TS 5 would be nice.

[MagicWater]

that would even be my most favorite function for running ts5 server on my raspi

[numma_cway]

There won't be a "ts5 server". The TeamSpeak 5 server software is called TeamSpeak 3.

[JordanDev]

Hello,

I must admit, I'm quite excited for TeamSpeak 5. I've always had little ideas for TeamSpeak, but never really submitted them, so here goes.


Further Hotkey support + native joystick / button box support:

What I mean by "Hotkey" support is add more possible key assignments, like "Modify Permission Value" I think this would be
really beneficial for larger servers, because when you make a server, you are often changing the same values, but modifying the
permission power (Also I think TS5, should keep the current permission system, or add an optional advanced / basic one).

Also Button Box / Joystick button support should 100% be native in TS5.

Better SDK (or more friendly one)

There should be easier implementation of bots (i.e server query), you should have a base api that can be expanded on (like
the current implementation), just don't make it difficult to implement, all of the current Wrappers are either over
complicated, or just don't work anymore.

(I'd say improve the client api, though I haven't messed with it yet so I can't really comment on it).

Improve the user interface (or allow further customization)

You guys should implement base themes, one's that are native with the client (like a Dark Theme, etc). And allow CSS to be
used for the UI. It would allow further modifications. I'm all for letting programmers handle it, but realistically you
want it to be more accessible for everyone (by this I mean don't make it in an addon form, make a easy to use selector).

Expand the offline messaging support

Offline messaging support works. I'd recommend using the current MyTeamSpeak implementation and include a messenger,
some people only use TeamSpeak, and it would be good to be able to message others without them having to join a server.

Expand the current implementation of MyTeamSpeak on servers

I've used TeamSpeak for years, and have never switched, but I think the idea of allowing users to implement MyTeamSpeak on the server end is useful, and a great idea. Expand the use of TeamSpeak, allow for custom commands, etc. Without using 3rd party stuff, like SinusBot, JTServerMod, etc. (What I mean by this, is expand the API on the server end more than ServerQuery.)

Addons

The "addon" download area should be put directly into the client. Having to have you're users goto an external site, then download a file from you're site, then have them install it, is a bit much (if you ask me), it would be much easier, and probably a lot faster if this "marketplace" was brought directly into TeamSpeak, and you didn't have to download it from the site, but rather you could download it directly from the client.

Permissions
This is gonna be a long one.

I love the current permission system to an extent. I think there are missing features. TeamSpeak's "basic" permission system doesn't to it for the majority. Which makes it not user friendly, which often turns people away. TS5 should have a basic permission system that works, and does everything the advanced one does, without complications. The advanced system on TS3 is great, and should be carried over to TS5 but should just give more options, mainly for the people who want to expand on the basic one.

Server Group Channel Permissions

TeamSpeak 3 has Client Channel Permissions, why not Server Group Channel Permissions? This would add SO many more options. Especially for the larger groups. Even if you guys don't implement everything else, PLEASE IMPLEMENT THIS.

Mobile

The mobile version of TeamSpeak should be free, why is the Desktop version free, and the mobile one not? It doesn't make much sense in my opinion.

-----------------------------------------------
Closing

Thanks for reading, these are just some of the ideas I could think off, and I'll probably have more that i'll submit.

[numma_cway]

Many of your points are about the server. The TeamSpeak 5 server is called TeamSpeak 3.

Better SDK (or more friendly one)

There should be easier implementation of bots (i.e server query), you should have a base api that can be expanded on (like
the current implementation), just don't make it difficult to implement, all of the current Wrappers are either over
complicated, or just don't work anymore.

(I'd say improve the client api, though I haven't messed with it yet so I can't really comment on it).

SDK and query are different things. If you don't like existing wrappers, make your own one like I did. Sadly, I have noone to blame if something doesn't work.

Improve the user interface (or allow further customization)

You guys should implement base themes, one's that are native with the client (like a Dark Theme, etc). And allow CSS to be
used for the UI. It would allow further modifications. I'm all for letting programmers handle it, but realistically you
want it to be more accessible for everyone (by this I mean don't make it in an addon form, make a easy to use selector).

TS3 skins are currently created using CSS.

Expand the offline messaging support

Offline messaging support works. I'd recommend using the current MyTeamSpeak implementation and include a messenger,
some people only use TeamSpeak, and it would be good to be able to message others without them having to join a server.

This was announced on gamescom.

Expand the current implementation of MyTeamSpeak on servers

I've used TeamSpeak for years, and have never switched, but I think the idea of allowing users to implement MyTeamSpeak on the server end is useful, and a great idea. Expand the use of TeamSpeak, allow for custom commands, etc. Without using 3rd party stuff, like SinusBot, JTServerMod, etc. (What I mean by this, is expand the API on the server end more than ServerQuery.)

What "API on the server end"?

Addons

The "addon" download area should be put directly into the client. Having to have you're users goto an external site, then download a file from you're site, then have them install it, is a bit much (if you ask me), it would be much easier, and probably a lot faster if this "marketplace" was brought directly into TeamSpeak, and you didn't have to download it from the site, but rather you could download it directly from the client.

Please update to TeamSpeak 3.1 or newer.

Permissions
This is gonna be a long one.

I love the current permission system to an extent. I think there are missing features. TeamSpeak's "basic" permission system doesn't to it for the majority. Which makes it not user friendly, which often turns people away. TS5 should have a basic permission system that works, and does everything the advanced one does, without complications.

If the "basic permission system [...] does everything", why would you need an advanced permission system? I don't get it.
Beside that, the sentence "improve permission system" is not a good suggestion. Tell them how.

Server Group Channel Permissions

TeamSpeak 3 has Client Channel Permissions, why not Server Group Channel Permissions? This would add SO many more options. Especially for the larger groups. Even if you guys don't implement everything else, PLEASE IMPLEMENT THIS.

Backing this.

[AGamer]

Many of your points are about the server. The TeamSpeak 5 server is called TeamSpeak 3.
SDK and query are different things. If you don't like existing wrappers, make your own one like I did. Sadly, I have noone to blame if something doesn't work.

TS3 skins are currently created using CSS.

This was announced on gamescom.

What "API on the server end"?

Please update to TeamSpeak 3.1 or newer.

If the "basic permission system [...] does everything", why would you need an advanced permission system? I don't get it.
Beside that, the sentence "improve permission system" is not a good suggestion. Tell them how.

Backing this.

I hope Teamspeak does away with these pointless numerical notations, and just call the product Teamspeak, nothing else is needed. I'm not talking about version numbers, just the whole Teamspeak 2/3 5 etc..

I agree with:

Server Group Channel Permissions

TeamSpeak 3 has Client Channel Permissions, why not Server Group Channel Permissions? This would add SO many more options. Especially for the larger groups. Even if you guys don't implement everything else, PLEASE IMPLEMENT THIS.

and

Mobile

The mobile version of TeamSpeak should be free, why is the Desktop version free, and the mobile one not? It doesn't make much sense in my opinion.

[fspower]

What "API on the server end"?

Probably some REST style interface. Would be nice, arguably better then the telnet query.

[preterive]

I think a feature to share the screen would be great.

[IL_Messia]

So TS5 will be just an update?

Anyway, I think that offline messages will be more useful with a popup when you open the client or join a server

[numma_cway]

Probably some REST style interface. Would be nice, arguably better then the telnet query.

Why exactly?

[maggy]

The TeamSpeak 5 server is called TeamSpeak 3.

Do you have a source for this?

[AndryGabry]

Add:
-ban for hardware id or an id that does not change over time and can not be changed
-can hide server message (<user x to deleted channel x>) related to a specific user («example a bot»)

[MeltDownPlayer]

-ban for hardware id or an id that does not change over time and can not be changed

everything can be changed, even the hardware id

-can hide server message (<user x to deleted channel x>) related to a specific user («example a bot»)

they already said they wont do that and i understand why.

[Well_Skilled]

That would be nice to which server my friends are actually connected if I got them in friends list.
Greetings.

[cydolo]

Then TeamSpeak would have to redevelop a complete friend system, simply add one as a friend and seeing where he is, is a bit creepy