Open garrettec1 opened 2 years ago
I think we want to be careful about how quickly we grow since that strengthens the security dramatically. We need to grow slowly enough that the security is kept low and time to grow, weaken, hack, stay consistently low.
We probably also want to be cognisant of threads operating across servers not acting at cross purposes. Not sure how to achieve this.
We get special bonuses on our home computer. Our home computer should hack our highest value targets,
The logical conclusion of this kind of improvement is that we are writing a scheduler.
So, first off the launcher script needs to determine the basic resources it has available in terms of memory to run scripts and what the requirements are for growing, weakening and hacking all the exploitable targets are.
The memory pool should be in the form of objects that contain
The targets should have a full complement of information about them (including maybe all the stuff from getServer
)
There are two distinct phases to hacking a server. The initial growing and weakening to make it a juicy target, and then the steady state hacking to make a ton of money.
This is straightforward, just drop it to min security level.
This is a related rate with the server weakening function.
All three of these are related rates.
It’s good if money grows by a large amount, and it’s good if server security weakens by a large amount but it’s bad if the hack takes too much money at once because then a long time has to be spent growing the server back up and a lot more weakening needs to be done.
So grow and weaken should have lots of threads dedicated to them, and hack should have lots of scripts with small numbers of threads.