[UNSUPPORTED] NeoQuester! - Fully Automated Neoquest 1 Completer

[HiroiSekai]

You're welcome to join our Discord where people often talk about whether SP is being aggressive or not on site, under the #cheating channel Also, lots to talk about with others!

(you need an account to see links)

I actually have filled my limit for Discord servers, the joys of jumping communities on Twitch. Regardless, I had a brief moment earlier today where the script actually let me through. It played for a little bit and then hasn't been allowed back in since.

[HiroiSekai]

Well regardless, here and there I've been able to slip in by just test running the script. It runs much faster than other scripts so I'd say it doesn't take nearly as long as the NeoQuest II auto scripts to run towards the trophies. Haven't had any trouble running it, in case others were still looking at it. This is the only script I could find that actively plays for you on NQ1, so big thanks to the dev for making it.

[maizono]

Thank you methrend for this amazing program! I've just started using it and it's going well.

For the Dank Cave pathing issue: before you run the program, make this edit so it paths correctly.

Open up the classes/NQLoop.py file. You can open it in Notepad or any other text editor.
Ctrl+F "148" (no quotes)
There will be a long number string a few lines below in "move.go(self, self.acc, NUMBER)"
Replace the number with this one:

2146777787855558853222222112214444444466677777777858855555555555322323222222211221441144644444444

This will NOT fix the problem if you're already stuck. So make the edit when you first start the game.

This is the only error I've come across so far. If there are more I'll add my fixes to this post as well.

[HiroiSekai]

Thank you methrend for this amazing program! I've just started using it and it's going well.

For the Dank Cave pathing issue: before you run the program, make this edit so it paths correctly.

Open up the classes/NQLoop.py file. You can open it in Notepad or any other text editor.
Ctrl+F "148" (no quotes)
There will be a long number string a few lines below in "move.go(self, self.acc, NUMBER)"
Replace the number with this one:

2146777787855558853222222112214444444466677777777858855555555555322323222222211221441144644444444

This will NOT fix the problem if you're already stuck. So make the edit when you first start the game.

This is the only error I've come across so far. If there are more I'll add my fixes to this post as well.

Thanks for pointing this out! I've been slowly squeaking through the few small moments when StackPath lets the bot through, and I haven't run across the issue completing on Normal and Evil difficulties. However, seeing as the bot only can play a small chunk at a time before getting booted, so I definitely don't want that happening halfway through the Insane difficulty.

I can confirm that besides StackPath returning a "Login Failed - Frozen - Exiting" message about 95% of the time, there's no actual errors I've come across while the bot itself runs. It's really just been about leaving cmd open and running the script whenever I can think of it to see if it'll pass through the security. If I come across any findings, I'll add them here as well.

[r56]

So it's just stackpath when it's claiming the user is frozen, and when SP isn't being so aggressive I should be able to run this?

[HiroiSekai]

So it's just stackpath when it's claiming the user is frozen, and when SP isn't being so aggressive I should be able to run this?

Yes, that's correct. The small pockets I've had it run, it seems StackPath wasn't aggressively kicking the script out during the login check. However, I've had it successfully run, but then just kind of stop partially through, so it seems StackPath can still get in the way even while the script is running. Nowadays, I haven't honestly been able to get it to connect once over the last 3 months or so though, so I wouldn't necessarily keep up super high hopes. Keep running it here and there just in case, moreso.

Kinda sucks because I got right up to the Insane difficulty and it stopped being able to get through since. I just need it to make that one last hurrah to get it to the end and never think about it again.

[DarkSkies]

Yes, that's correct. The small pockets I've had it run, it seems StackPath wasn't aggressively kicking the script out during the login check. However, I've had it successfully run, but then just kind of stop partially through, so it seems StackPath can still get in the way even while the script is running. Nowadays, I haven't honestly been able to get it to connect once over the last 3 months or so though, so I wouldn't necessarily keep up super high hopes. Keep running it here and there just in case, moreso.

Kinda sucks because I got right up to the Insane difficulty and it stopped being able to get through since. I just need it to make that one last hurrah to get it to the end and never think about it again.

I'm not sure if the https change may have affected also, I've stopped trying this one because I couldn't login but I should keep trying again.

If anyone can get to pass the login recently let us know here please

[j03]

I'm not sure if the https change may have affected also, I've stopped trying this one because I couldn't login but I should keep trying again.

If anyone can get to pass the login recently let us know here please

You’d need to add https support if you haven’t already, and also a proper SP bypass to get this functioning.

[sallys]

You’d need to add https support if you haven’t already, and also a proper SP bypass to get this functioning.

Hello, Joe. How could I bypass the StackPath, do you mean by using a VPN?

[j03]

Hello, Joe. How could I bypass the StackPath, do you mean by using a VPN?

A VPN helps you change your IP address. Sadly, you can't bypass StackPath with that.