Search results

I couldn't start anymore the bot since today I rebooted and here is the log when trying to start: I restored a backup from July, on previous version 1.0.0-beta.16-ba60e37, and it could start properly. Not sure what happened I could restart the bot correctly recently. Ubuntu 22 here.

Thank you the bot is now working on all TS server under my hands with beta 16 (deleted the cache folder directly didn't attempt without deleting it). I will try to edit the server back to where it was regarding its settings and see if something breaks. I will edit this post accordingly. //EDIT...

What I don't understand on my side is why I can't have it to work on my TS server when it works on my friend's TS (two bot instances). My TS server is up to date 3.13.6, his TS server is on older version 3.8.0. If I switch TS server IP on bots instances, his bot then doesn't work on my TS so...

Thanks, I will try to mess with these settings. So far no luck. //EDIT: yep I can't have it t owork on my own TS server, but it works on my friend's TS server with similar settings. Tried to recreate the bot Instance, same issue. I'm on the new updated version linked above though.

I updated and my scripts still are not working at all on this new version. They work when I restart the bot and when it connects it triggers one of the scripts as intended, but then it instantly stops working. Can you elaborate on how to get it work again?

Thanks for proper link my bot wouldn't start today because it was outdated but I downloaded from the ressource page as it was the only place I could think of to download. Is there something to subscribe to notification for the future beta updates? I'll now use the link...

I really recommend to use better program than notepad, like Notepad++ (download it here) it will make life easier to better view source code ;) with syntax hilighting for many languages. I made an updated version of the script, this one is on the old API. If you prefer to have my script updated...

I'm getting closer, by modifying the logging, I got this: engine.log(ev.fromChannel); EDIT: woooohhoooooo!! I got it! ev.fromChannel.id() gives me the channel ID :) Here is the working script with all I needed, now I will just expand it to match my old full script, thanks all for the help...

Here is the progress so far, all this is working, but it is not exactly what I need because there is still no comparision with the original channel the client is moving from: registerPlugin({ name: 'Client Leave Music or Sentence', version: '2', description: 'Script to play track or...

Hello guy! Thanks for all the replies, I will look into it as soon as possible but I recently had big internet issues and until everything is not sorted on this side I will not work on this. I think I can have it to work now with all the suggestion in your replies, it is really different than...

Hello there, so first I would like to say I'm not a coder. I took lot of time before to create a few scripts for my personal use, looking how other scripts were made, on the older API version. Most of my scripts still work, but the last one I created had weird bugs. Someone here (where I linked...

Thanks for the reply. I will try to update my script with the new stuff and see if it now works :) I'll let you know.

Here is another similar thread which did not receive any reply to this day. https://forum.sinusbot.com/threads/scripts-wrong-data-in-clientmove-event-when-clients-leave.1492/#post-8096

Operating System: Linux Ubuntu 14.04 SinusBot Version: 0.9.18-8499d2c TS3 Version: 3.0.19.4 Problem Description I have a script I made which is supposed to play a track or say a sentence when someone leaves the channel where the bot is. Problem is that it only works sometimes as intended (play...

Nice :) Hope my script will still work :D and that updating to this new version will not break anything in the bot itself (already had a few problems in the past while updating, one have been solved with the help of Flyth and a magic parameter in the config file, the other needed full reinstall...

OK from my testing, it seems that &volume=-90 in my script means the same volume as !volume 10 in the bot chat. &volume=-80 seems to be like !volume 20 &volume=-50 seems to be very loud and above seems to be the same volume (LOUD lol)

Just for my knowledge, is there a variable for the current volume in the bot, or is there a way to grab the current bot volume value to put it in a variable (and use it then with the ephemeral thing)? //edit: what I needed was getVolume()

Ho great I'll have some tests with that so. Thanks for the tip ;)

UP anyone?

Hi all! I'm using the latest Sinusbot beta build. I have a problem with a script. I would like to know if it is possible to control the volume at which a track plays with the ephemeral parameter on true? I mean when I play a track with my script...