Possible scamming bug

I'm not entirely sure this is a game bug but I think it has happened 3 times to me in the past couple days and I think it's a bug on torn's end, but it's confusing between the script I'm currently using for scamming and the log not differentiating the 3-nerve actions in the log at all, and the page completely refreshing itself whenever I get attacked and me having to reload the page and go back to look and remember, purely by memory, what the job was at before I got hit.

So here's how it appears to be happening:

(I will try to find more examples if I can later)

I'm doing scamming jobs

I click an action and it gets interrupted? (I thought the action didn't go through the first 2 times this happened, but the 3rd time it happened the action did go through, I think, even though the page refreshed into the "you are being attacked" page when I tried to do it)

After this happens, the script now shows a green question mark, instead of a green check mark, on what it thinks I should do. Example where the middle job is one that got interrupted:

Load image

That's just a script bug as far as I can tell.

But then I med out and reload the scamming page.

I go back to the same job.

I try to move the cursor with strong forward, small forward, or backward... and the cursor doesn't move. The nerve is taken and shows up in my log, but the cursor doesn't appear to move. This has happened 3 times and I'm not 100% sure on what exactly has happened every time, but I'm 100% sure the nerve is taken and I'm pretty sure nothing is done with it.

After that, the job works again, I can move or collect the money on whatever spot the cursor appears to move to, so I don't think it's any kind of visual bug with the script, it's just that previous action seemed to have disappeared into the ether.

16:40:29 - 06/02/26 You used 3 nerve successfully responding to a Prize Scam target

I think that log specifically is the most recent one to have bugged (it was immediately after medding out from being attacked) but it's hard to tell once more things happen in the log. Also, the move before/during being attacked was a small forward and put me past the green. The move after medding out, shown in that log, was a small backward (didn't work). Then I had to small backward again and got in the green.

I assume I'll get it again sooner or later so I'll try disabling my script next time the script bugs Load image: dizzy

Not sure if I can record what happens before being attacked because it's pretty rare and seems to only happen when I get attacked right as I'm doing an action but I should be able to record after the script bugs again next time when I assume the next action won't work.

This time it happened because my tab crashed rather than an attack, but I think it was the same bug.

I started a new job.

I selected accelerate

I selected strong forward (tab crashed as I was clicking it)

The cursor moved, landed on orange, and didn't count as a yellow fail? (I also now think this part may not have cost any nerve but I'm not sure)

I disabled my scamming script and started a screen recording

[image: i.ibb.co]

I went back to the scamming page

I clicked soft forward

The cursor didn't move, 3 nerve was used, the job counted as immediately landing on the spot it was already in from a strong forward, and started the orange failure timer.

Sorry about the ass quality I don't have any video editing software on my computer right now.

Not sure if this helps but from looking at the recording i think the issue might be before you click Respond. 

Notice the the indicator is currently already on the Hesitant (yellow) area.

If you are in the yellow area, you shouldn't be able to select and option and response. 

If you were in the yellow area but you have waited the duration, the yellow area should disappear. 

Since the indicator looks to be in the incorrect place, when you do click respond, the indicator doesn't move. (Just watch the placement of the black marker throughout the process). 

I suspect that the indicator at the start of the recording is in the incorrect place. The range is based on the incorrect placement. After responding moves to this location and triggered the Hesitation. Which makes it look like it hasn't moved. 

Thanks, 

Dilz 

Yeah but what's weird is apparently the landing spot is already determined and the nerve hasn't been used yet I think, it either hasn't been used yet or it gets used twice, but I think it just hasn't been used yet. Originally I did think it was getting used twice, but the last time it happened I didn't see the first try in my log.

It makes me wonder if I could have just abandoned the job after it landed on yellow and not get the penalty I was supposed to.