channel creation parent channel not applied after update

[essem]

Just updated to 1.0.0-beta.1 and encountered a problem with the channel creation now: the channel got created but below the whole channeltree, previously it was created as a subchannel while using this code:

//...
                var currentchannel = client.getChannels()[0];
                if(currentchannel == undefined) return;
                if(client == undefined) return;
                var channelparams = {};
                channelparams.name = ""+client.name()+"'s channel";
                channelparams.parent = currentchannel;
                channelparams.semiPermanent = true;
                channelparams.encrypted = true;
                channelparams.codec = 4;
                channelparams.codecQuality = 6;
                channelparams.maxClients = -1;
                channelparams.permanent = false;

                var channel = backend.createChannel(channelparams);
                if(channel == undefined) {
                    engine.log("Could not create private channel for some reason.");
                    return;
                }
//...

if anyone can confirm this behaviour or point out an error is on my side it would be much appreciated

 

[djalmasi03]

This is the same error for me. I have been suffering for more than an hour because I just couldn't understand what's wrong ... then I realized that the new version of sinusbot.

 

[DrWarpMan]

I already reported this bug, and @flyth told me he will check it.

 

[essem]

Thank you @DrWarpMan

hope the bug with deleteDelay not working (since about 2 years) will also be fixed. It will fail to create a channel if this parameter is set with the message "Could not create channel: invalid parameter"

litterally the only line added:

channelparams.deleteDelay = 100;

Related doc.: https://sinusbot.github.io/scripting-docs/#channelparams

 

[TwentyFour]

deleteDelay is working fine for me.

Can you describe your problem?

 

[essem]

@TwentyFour
if i run the following code it returns an undefined channel with the message "Could not create channel: invalid parameter" (and my custom message), however if i comment the deleteDelay line out it creates the channel. I can't spot a problem in my code. (Bot version: 1.0.0-beta.1-06a54d7)

                var channelparams = {};
                channelparams.name = ""+client.name()+"'s channel";
                channelparams.parent = currentchannel;
                channelparams.semiPermanent = true;
                channelparams.encrypted = true;
                channelparams.codec = 4;
                channelparams.codecQuality = 6;
                channelparams.maxClients = -1;
                channelparams.permanent = false;
                channelparams.deleteDelay = 100; //this line

                var channel = backend.createChannel(channelparams);
                if(channel == undefined) {
                    engine.log("Could not create private channel for some reason.");
                    return;
                }

 

[TwentyFour]

channelparams.semiPermanent = true;
channelparams.deleteDelay = 100; //this line

I think those two parameter collide. Only a temporary channel can have a deleteDelay, semi-permanent ones will just get deleted on server restart.
Have you tried it with a just temporary channel?

 

[essem]

@TwentyFour yeah noticed it too, now i just get the problem that the bot will move to the created channel. i hope to find a solution for it

 

[TwentyFour]

Intented behavior by TeamSpeak.
Create the channel as permanent first, the way you're doing already, then use the update function afterwards to set it back to temporary + the delay. That way you avoid the move

var chanToCreate = backend.createChannel({ name: possibleChanName, parent: homeChannel, password: password, permanent: true, codecQuality: 6 });

if (chanToCreate != undefined) {
                    chanToCreate.update({ permanent: false, deleteDelay: tempDeleteDelay });
                    }

 

[essem]

maybe they should write stuff like only for temporary into the docs.
also just found a workaround for the parent issue: use the channel-id instead of the raw channel