It looks good but maybe pull it out of the define and run it in a separate Ubot so you can see what is running (the node that is currently running has a purple highlight so use light theme if using X).

unibotsi says: It is an older Version (5) from a friend, which i use to check if ubot is the go-to tool for me - before investing almost 1k of dineros :-)

Sounds a little suspicious... maybe you got the version of ubot that can detect that it has been cracked and as a defense it provides erratic results so that you cannot profit from it without first paying for it.

I see a couple of things wrong you may want to address before you continue.

1- you call for a browser wait event before you even call the browser....so you'll want to put that immediately after the navigate call... This isn't something that will cause a break, but it is useless the way you have it displayed via your posted code.

2- the next thing that comes to my attention is an if statement on the page.... you have it as: [if] #variable [then]..... that isn't how things work. Instead, you need to give the [if] statement something to work with... like, "contains", or "comparison", or "exists", else, I don't think it would ever save your file.

Though it is hard to "reproduce", as i do not know where you are referring to

1. If you are referring to the first wait event - this one looks weird, but it follows a navigate from the previous step.

2. I guess you are referring to the #botfolder variable - this one is a true or false variable (checking if the save folder is available) which i use very often, so i did store the value as boolean. All files are saving perfect.

Btw, do you use Ubot X?

Using it "brutally" since some hours, have to restart very often now as it crashes a lot

2- the next thing that comes to my attention is an if statement on the page.... you have it as: [if] #variable [then]..... that isn't how things work. Instead, you need to give the [if] statement something to work with... like, "contains", or "comparison", or "exists", else, I don't think it would ever save your file.

You must call a custom command/function after you define it to use it. You can (and probably should) define your custom commands in other tabs which are labeled and organized and then call them from the main script.

Example:

comment("This part is ran")
MyCommand()
divider
divider
comment("You can call this as many times as you want")
MyCommand()
divider
divider
divider
divider
comment("This is the defined code
it is only ran when you call MyCommand
not when the script gets here (then it is skipped)")
define MyCommand {
alert("hi")
}