Leopr786 wrote:Here is a slightly updated version. I can't do much now since I got 5 nodes updating.
Sorry for taking a while to get back to you (I'm helping multiple people all the time, plus working on other posts and things so I didn't have time to reply until now)
, but if your network is still roughly the same, specifically still Core 11, then here's what you could try. You'll need to get rid of 3 of your Server Farms and 1 of your B-Coin Mines in order to make any variation of the following layout I made for you, which requires you to get a 4th Code Gate, 3rd Sentry, 3rd Scanner, and 3rd Program Library.
#1 Occasional Kraken
Here's the network flat. You may use this as better reference for attaching everything correctly. The Core is positioned after only one leveled Code Gate. High level Krakens can melt your Code Gates as they're not sufficiently high leveled to slow them down enough, so leaving the Core before your highest Code Gates is a good way to keep your Core safe while not giving too much power to the occasional Kraken users.
#2 Occasional Kraken (Folded)
Here's the network with the tail folded on top, or below, other nodes. Folding a network helps make nodes harder to select from certain angles. Also makes it harder to follow a path in maelstroms, but for this layout the purpose it serves is to separate the sides of the network to make multitasking more cumbersome for the opponent. Whether the tail is folded or not, the layout is pretty much the same, but the fold gives that slight advantage, so I always recommend you fold your network's tail.
You can attach the Core to the first Scanner to counter Kraken. Level 1 Code Gates barely stall during brute force at your level, so it really doesn't matter much if they Kraken through it.
If you don't want the Kraken to go through even your level 1 Code Gate, then leaving the Core as you have it now can also work.
#5 Core At 1st Step
You can attach the Core to the netC like this so if they use Shurikens, they still have to go through your Core first before attacking your Code Gate, just like Beam (n00b) Cannon users would. Attach the 3rd Library to the Core so it has higher priority than the Code Gate (I realized I forgot to attach the library in the screenshot)
, or attach it to the final two Code Gates to create the following version.
#6 Compiler Stall
You can stall a couple of seconds longer before they target your Guardian by attaching your Compiler to the security nodes with the highest priority. If the Black ICE is not targeted last, then you'd attach it to the Compiler.
This will only work as long as your Guardian has less firewall than your Compiler.
If Krakens aren't a concern for you, then you can position the Core at the 9th step like this to keep it safer.
#8 Farm At 9th Step
Alternatively you could leave the compiler where it appears in the previous variations, and attach the Server Farm to it. It's always good to have the resources be the last thing they capture.
#9 Beetle Extended Range
- Can regenerate the firewall of more nodes.
- Having to heal more nodes at a time means it will be less effective.
It all depends on whether they decide to take both sides at the same time or they focus on one side at a time.
I put the 3rd Library on the Beetle, but your Compiler would be better as you can attach it before the Farm, so that the compiler is attacked first. The Library would only have higher attack priority than the Farm if you upgraded it to level 20.
One of the Black ICE at the Guardian choke point represents your 4th Turret. The Sentry at the Guardian choke point represents your sentry level 1. The Sentry at the Squid choke point is your low level Sentry. The Sentry by the AI nodes is your highest leveled Sentry. The Guardian choke point represents the level 1 Guardian you got. Also, you can delete the Squid and add it back in to make it a better choke point.
The reason the last Code Gates are linked via another node, is to help the high level Sentry spread to the other side. It can be cut off otherwise if the opponent reaches your second Code Gate before it gets a chance to spread. The level 1 Sentry can spread its AV much faster with 3 nodes uploading the AV to the Squid and after that it slows down again, but should be quick enough to let the AV spread out to the other nodes, which will then be overwritten by the highest Sentry AV.
I could go on with different variations of the layout, but that should be sufficient options for you to choose from, depending on what your focus is. Want to protect your reputation? I recommend #7. Often deal with Krakens? I recommend #3. Want an in between? Use #2 then. Try whichever one of these variations works out best for your needs. These layouts are more dependent on you having two leveled Scanners, so better focus your building threads on getting those done first. Let me know how they work out for you and if you need an updated version whenever you upgrade your Core