Update

[Moonl1qht]

maybe this option is better?

AutoQuestComplete.plugin.js
const randomInterval = Math.floor(Math.random() * 4) + 6;

const timestamp = secondsDone + remain;

try {
const response = await api.post({ url: /quests/${quest.id}/video-progress, body: { timestamp: Math.min(secondsNeeded, timestamp) } });
isFinished = response.body.completed_at != null;
secondsDone = Math.min(secondsNeeded, timestamp);
Logger.info(this._config.info.name, Video progress: ${secondsDone}/${secondsNeeded} sec.);
} catch (err) {
Logger.error(this._config.info.name, "Error sending video progress, retrying in 5s...", err);
await new Promise(resolve => setTimeout(resolve, 5000));
continue;
}

if (timestamp >= secondsNeeded || isFinished) {
break;
}

catch (err)
variables inside onConfirm have been replaced with err.message and err.stack

[Moonl1qht]

I want to know your opinion.

[xenoncolt]

I am kind a bit confused but.. r u trying to say after request fail retry the loop again? and caught error (i mean report handler)?

[Moonl1qht]

Instead of adding random fractions of a second as "noise," I implemented a random delay (in whole seconds) for the submission. I checked the Discord console and matched the timing, which averages between 6 and 9 seconds. This makes the view count appear more natural and less like it was generated by a script. I also added a script restart function to handle unstable internet connections—such as a proxy failure—forcing the script to retry the process.

[Moonl1qht]

reduced risk of detection through human-like intervals and increased fault tolerance in the event of network or proxy failure

[xenoncolt]

Sry for the late reply,

I read it and i think it doesnt effect that much coz urs is 6 to 10
But mine is 7 to 8

which is same but ur is more faster.. and i have to test it before commit.

[Moonl1qht]

Will I send you all the changes to my code?

[xenoncolt]

Will I send you all the changes to my code?

No need..thank you.. i got it.. i will try to test it tmr on my alt account