It would solve the problem that the value is not stored in the database as it should.
But biggest problem now would be that the client isn't able to set a channel icon any longer.
We may overhaul this or the client or delay the change.
It would solve the problem that the value is not stored in the database as it should.
But biggest problem now would be that the client isn't able to set a channel icon any longer.
We may overhaul this or the client or delay the change.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
Back to this.
We evaluated if something would break. Everything works as expected.
Clients still can set icons via permission or channel create/edit dialog and the ServerQuery allows to set icons with command channeladdperm cid=x i_icon_id=x
Server 3.9.0 will no longer allow to use the channeledit command for this.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
Just to clarify the situation... the reason why we decided to prevent the icon ID from being set using channeledit is that is was inconsistent behavior. Other commands like serveredit and clientedit do not allow setting the icon ID either since it's supposed to be changed via permission. What happened before is that channeledit updated the read-only channel property... which might seem convenient, but actually was a bug and lead to a series of issues such as the permissions not being updated.
Anyway... we feel it's better to provide a consistent API to our users and there are a lot of other things we need to tackle in that area.
Do you have to channeldelperm each time to add a new perm or is there a way to edit it?
With my testing if you try to set a new value with channeladdperm it will error with:
channeladdperm cid=453 permsid=i_icon_id permvalue=2524640421
error id=1540 msg=convert\serror
as
channeledit cid=453 channel_icon_id=2524640421
Works consistently without any problems for me.
Last edited by Patrick1164; June 13th, 2019 at 02:26 PM.
No mention of the fix for channeladdperm being able to change icon if channel already has perm in 3.9 changelog, is this included?
There is no fix to set an icon with that command when a icon is set already.
That worked before and still works.
New is that you can use 2524640421 (Unsigned Int) or -1770326875 (Signed Int) to set an icon via permission commands.
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
I don't understand, this doesn't work.
I first set the channel with no icon perm to:
channeladdperm cid=453 permsid=i_icon_id permvalue=2101350922
error id=0 msg=ok
Then:
channeladdperm cid=453 permsid=i_icon_id permvalue=2524640421
error id=1540 msg=convert\serror
Third:
channeladdperm cid=453 permsid=i_icon_id permvalue=3373850627
error id=1540 msg=convert\serror
But if I then do:
channeladdperm cid=453 permsid=i_icon_id permvalue=-1770326875
error id=0 msg=ok
Is this fixed in 3.9?
Are you talking about 3.8.0 where you get the errors?
Yes this was changed (not fixed) for server 3.9.0 Beta1
When sending me private messages: Please make sure to include reference link to your forum thread or post.
TeamSpeak FAQ || What should i report, when i open a client thread?
Well you're disabling channel edit being able to set the icon, which I use in some code so I'm preparing for that change in 3.9, I wanted to know if this behaviour was changed so that you could set an icon via permission if the channel already has one.
Is this now possible in 3.9?
Using channeledit to set icons never worked properly, so you shouldn't have done it before. That's why this thread was created. And TeamSpeak now removed a feature that never worked. So I don't see the issue.
dante said that 3.9.0 accepts signed and unsigned integers.
There are currently 1 users browsing this thread. (0 members and 1 guests)