Dear fellow engineers,
I'm sincerely seeking your advice on an issue I've encountered. When I use BAS software to compile a script I've created and then run the compiled executable on another computer, it downloads the required support files in the background. After making minor modifications to the script and recompiling it, I find that running the second compiled executable triggers another download of these support files, which consumes a significant amount of time. Is there any way to make the second compiled executable reuse the support files already downloaded from the first compilation?
Thank you all very much for your help and suggestions!
💻 Work with Reputation, Speed, and Quality
🤙 Telegram : https://t.me/basvietnam
💻 Website : https://basvietnam.com/
🎦 Youtube : https://www.youtube.com/@basvietnam/videos
@l3092923 said in How to avoid re-downloading support files after recompiling a BAS script?:
Dear fellow engineers,
I'm sincerely seeking your advice on an issue I've encountered. When I use BAS software to compile a script I've created and then run the compiled executable on another computer, it downloads the required support files in the background. After making minor modifications to the script and recompiling it, I find that running the second compiled executable triggers another download of these support files, which consumes a significant amount of time. Is there any way to make the second compiled executable reuse the support files already downloaded from the first compilation?
Thank you all very much for your help and suggestions!
If you did not change the BAS version in the source script, then additional files will not be downloaded in the compiled script
@BAS-Viet-Nam said in How to avoid re-downloading support files after recompiling a BAS script?:
@l3092923 Did you select this option when compiling the script?
This option is needed to save hard disk space in a situation where you have a lot of compiled scripts
@BAS-Viet-Nam Thank you, BAS-Viet-Nam. I would like to ask, what is the function of checking this option? Should I check it during the first compilation or the second compilation? Thank you very much for your reply!
@l3092923 Each BAS version uses a different "engine" file.
When you first launch BOT, it downloads the necessary "engine" files.
If you do not enable this option, BOT will always download the "engine" file from the server the first time you run any BOT. Therefore, if your internet connection is slow, this process can take a considerable amount of time.
However, when you enable this option, BOT automatically creates a dedicated folder to store the "engine" file for each BAS version. As a result, for all bots using the same BAS version on that computer, instead of downloading the "engine" file from the server again, BAS copies the previously saved "engine" file into the bot's folder. This makes the startup process very fast—only taking a few seconds to launch your bot.
Additionally, if you previously created a bot on BAS version 28.9.0 but later update and run it on BAS version 28.9.1, when you launch the bot again, BAS will need to spend time downloading the new "engine" file corresponding to version 28.9.1.
@l3092923 said in How to avoid re-downloading support files after recompiling a BAS script?:
@Fox Do you mean that when I compile for the first time, I enter the version as 1.0.0, and when I compile the second time, even if I change the name, as long as the version remains 1.0.0, it won't re-download the background files?
No, if you are creating a script in the 29.1.0 version of BAS (for example), then the compiled script will download the necessary files for the 29.1.0 version once. If you make changes to the script on version BAS 29.1.0, it will not download new files, however, if you change the script in the different version of BAS, the script will be forced to download the necessary files for the version of BAS on which you made the changes.
@BAS-Viet-Nam Alright, thank you so much, sir, for your reply. You are truly kind-hearted and very friendly to beginners like me!
