Before you do anything else, make sure you have a safe backup of all the projects from the DroidScript folder in your main storage.
Just copying DroidScript to DroidScriptOld with your file manager will be fine for now but you must not ignore this step.
And of course we always recommend you keep regular offline backups of your projects
Unfortunately you didn't answer my previous questions so I am going to assume that you were using Android 10 or newer when you uninstalled DroidScript and then reinstalled a recent version.
If that is not the case, stop and post details of your Android version and the make and model of your phone/tablet where you are seeing the problem.
Now a brief explanation of what has happened.
It was caused by uninstalling DroidScript before reinstalling it.
I am not suggesting that was an unreasonable thing to do, just that it now has unexpected consequences.
Since Android apps have been forced to target Android 10, they are now forced to use Scoped Storage.
An exception was made for apps that are an update from a previous version but you broke that chain by uninstalling DroidScript.
Instead of being in the folder DroidScript in your internal storage, DroidScript is forced to use
Android/data/com.smartphoneremote.androidscriptfree/files/DroidScript in your internal storage
So you have 2 options
That should cause DroidScript to use traditional storage and your previous DroidScript file.
2) you can copy the contents of the old DroidScript file to the new DroidScript file using your file manager and starting from internal storage go to
Option 2 will allow you to continue using scoped storage, which will mean that apps in DroidScript will act more similarly to any APK you will build and run on Android 10+
Please note, taking either option could destroy your old DroidScript folder (though it may not) so please do not ignore the advice to make a copy first.