daemon.js: Appears to be using hacknet servers even when disabled.

[Spote1990]

I am uncertain of the cause, but the daemon is using hacknet servers for ram regardless of the true or false statement in the settings. Is there a way to disable daemon targeting hacknet servers as a temp fix? Bitnode 9 seems to stall hard if there isn't any hashes moving forward.

[herrxyz]

additional, sometimes the script uses only a few available servers (like "CSEC", but ignores "n00dles") - seems random to me. seems to happen when I used infiltration script to get like 13b at once (all stats low except hacking) - happened before SF4

[alainbryden]

additional, sometimes the script uses only a few available servers (like "CSEC", but ignores "n00dles") - seems random to me. seems to happen when I used infiltration script to get like 13b at once (all stats low except hacking) - happened before SF4

This is unrelated to the original bug report. Note that there's often no benefit in using 100% of all servers, especially when there is amble ram on home or a few purchased servers. Filling each individual server with low-thread-count hack scripts just adds latency without significantly improving income, so we just don't do it.

[alainbryden]

I am uncertain of the cause, but the daemon is using hacknet servers for ram regardless of the true or false statement in the settings. Is there a way to disable daemon targeting hacknet servers as a temp fix? Bitnode 9 seems to stall hard if there isn't any hashes moving forward.

@Spote1990 I know it's been over a year since you reported this, but if you happen to have a copy of your save file in which this is occurring, it would help.

From my reading of the code, it quite clearly filters out any hostname starting with "hacknet-server-" - and it does this by default unless you override it with "-n" or "--use-hacknet-servers". Double check that you don't have a daemon.js.config.txt file on your system which is overriding this consistently by default.

Note that the HUD will show "(excluding hacknet servers)" on hover if nothing is using RAM on any hacknet servers. If see this, you can be sure they're being left alone:

The only other thing I can think of is that maybe you didn't realize that several scripts use spend-hacknet-hashes.js to make purchases, so the number of hashes doesn't typically have a chance to build up.

[alainbryden]

I'm going to close this as fixed for now, because I can't reproduce the issue, but I've recently improved visibility in whether hacknets are being used in the mouse-over dialog:

If at any point you suspect this is happening, check that dialog and confirm, and then send a screenshot of your daemon.js startup log, which would tell you whether you've enabled this feature. The things circled in red are what you need to look out for: