I think there is a bug in the fletching portion of the script. I'd suggest (for now) just banking the logs which is still fairly profitable for a no-requirement script.
You could also go to the FletchEm function, find the very last portion of it. There should be a writeln saying "Waiting for last slot" or something like that. The loop under that has a "Antiban" and "ClosePopup" (I don't have Simba on this PC so I can't provide exact names, sorry). Comment both of those out (// before each one). That will make it sit doing nothing for the 45 seconds instead of antiban but I have a feeling those two functions are causing it to click and interrupt fletching, which causes it to think fletching failed. Instead of active "antiban" it will look like you go AFK doing nothing for 55 seconds (fletching duration), which seems like a legit thing someone would do.
If you can't work that out due to my awful instructions, I'll attempt to remember tomorrow evening if I have a minute.
Edit: I'm bored and have notepad available.
Find the following. It's inside the FletchEm function.
Simba Code:
while t.getTime() < timeOut do
begin
if tabBackpack.countDTM(logDTM) = 0 then Break;
wait(GaussRangeInt(1000,2000));
AntiBan;
if closeAdWindow() then // Add re-click here if closing ad window, have clicking and selecting be a separate function
end;
change it to:
Simba Code:
while t.getTime() < timeOut do
begin
if tabBackpack.countDTM(logDTM) = 0 then Break;
wait(GaussRangeInt(1000,2000));
//AntiBan;
//if closeAdWindow() then // Add re-click here if closing ad window, have clicking and selecting be a separate function
end;