Stealth CORE [Multi-Threaded Bot] PUBLIC

[j03]

Been getting this unhandled exception when running once-a-day-dailies on multiple accounts at the same time. Seems to only occur when viewing the Program Activity log.

Please log in to view spoilers.

Very strange. Do you do anything in the log tab that triggers this error? I've never had it happen for me.

Hi Joe, I mark the tasks I want, but when I start the program, nothing happens.

Please check the first post, there is a walk-through. Sounds like you aren't scheduling any tasks to run. You're probably only configuring the settings.

[nataurs]

Very strange. Do you do anything in the log tab that triggers this error? I've never had it happen for me.



Please check the first post, there is a walk-through. Sounds like you aren't scheduling any tasks to run. You're probably only configuring the settings.

Nope, not doing anything apart from looking at the log. It seems to happen when multiple accounts are simultaneously running either the lottery, coconut shy or bagatelle together.

Edit: im talking around 15-20 accounts at the same time

[nataurs]

Also got this today while running Kiss the Morthog, Dice-a-roo and Lever of Doom AP on three seperate accounts:

Please log in to view spoilers.

Please log in to view spoilers.

Edit: I found the problem of this issue, I had accidentally selected the schedule to repeat these tasks after 2hrs while it was still running.

[Painwheel]

Please log in to view spoilers.

Got this error, any clue? D: Anyone have the same problem?

[Bat]

That looks like a StackPath block page response, @(you need an account to see links). You may be able to clear it by fulling closing Stealth CORE, then re-opening and logging back in. If you receive that error message again, then you're blocked from accessing the Neopet site for a while. If you're using a proxy or a VPN, then you can work around the block by changing your IP address. If not, then you may have to wait it out for a while. Some StackPath blocks are only cookie-based, and will go away if you close our program. Others can be server-based, and require a different outgoing IP address to work around.

[Painwheel]

That looks like a StackPath block page response, @(you need an account to see links). You may be able to clear it by fulling closing Stealth CORE, then re-opening and logging back in. If you receive that error message again, then you're blocked from accessing the Neopet site for a while. If you're using a proxy or a VPN, then you can work around the block by changing your IP address. If not, then you may have to wait it out for a while. Some StackPath blocks are only cookie-based, and will go away if you close our program. Others can be server-based, and require a different outgoing IP address to work around.

It worked by closing and opening again the Stealth Score Thanks!

[♥ Sneasel ♥]

Hello there,
I hope you can help me. Stealth Core won't open to me anymore. I don't get an error or anything.
It worked fine the other day. When I double click the Desktop Icon, I get the Window to confirm the execution from an unknown source, but after accept nothing happens.
Any idea?

[j03]

Hello there,
I hope you can help me. Stealth Core won't open to me anymore. I don't get an error or anything.
It worked fine the other day. When I double click the Desktop Icon, I get the Window to confirm the execution from an unknown source, but after accept nothing happens.
Any idea?

My guess is it's your antivirus?

[♥ Sneasel ♥]

My guess is it's your antivirus?

Hey J03, thanks for the super fast answer.
Yes, that would be my guess, too. But I don't have any antivirus programm installed, only windows defender. Is there a way to find out?

[j03]

Hey J03, thanks for the super fast answer.
Yes, that would be my guess, too. But I don't have any antivirus programm installed, only windows defender. Is there a way to find out?

You have to find out yourself what's on your computer... Windows Defender is an AV program, but I also have that and have never had issues.

Think about what you did differently from before. Did you change the language setting?

SC is working fine on my end and for plenty others according to our homepage statistics.