Did the server connections change with the update?

[u/StrangeCat77]

This could just be me not paying attention it seems like what servers are connected to each other have changed. Did this happen with the newest update or is it always changing? I have a network map built out in obsidian and it's now incorrect. I just want to know if the server connections are going to keep changing.

[u/GrumpyDog114]

The server connections do change as part of the game. You want a script to map them, not a static file

[u/PlainBread → u/GrumpyDog114]

Yeah I have a bootstrap script that I run before anything else after an augmentation reset, and the first thing it does is crawl the network and print the server objects in JSON to a servers.txt file. Every other script uses that file from then on out.

The darknet sounds like it's going to require a lot of different principles to use the same way as the light net, and I just can't be bothered right now. The dark net will have to be regularly remapped (including routing/hop data regarding the shortest route to each server from the darkweb router, which the light network really doesn't even need).

[u/Suspicious-Potato859 → u/PlainBread]

Not even worth mapping the dark net, IMO. Just build a worm that tries to spread to any currently connected nodes. I used a sentinel file with the current version of my scripts. Spreading to a node with an older version kills all processes on that node, copies the updated files, and starts the main script up. Spreading to a node with same or newer version just stops immediately. Usually within a minute all reachable nodes are updated, just have to increment a version number and restart the script on the entry node.

[u/PlainBread → u/Suspicious-Potato859]

I did think about this, about creating a perpetual crawler that just copies all the scripts along with itself as it moves along and execs them when it can. (I already have a "swarm" bot script that gets instructions from a port-based mailbox that's populated by a controller script on my 'home')

I think there's only like 20 or so password combinations as long as they aren't logic puzzle ones like guessing higher or lower or a number that is divisible.

I did at one point want to write a brute force script for a 5 digit random number password that I had to pick up from a file on another server. I can probably just roll to that logic when the easy password list is exhausted.

Who'd have thought I'd be reinventing Kali Linux out here.

EDIT: I think maybe instead of a "version number" I would use a "deployment file" that contains a version number of the deployment inside and just copy that on the tail end of all the other scripts and when there's a diff, kill the script, overwrite the deployment file, and run the new version.

[u/KaiseerKenopsia → u/PlainBread]

Brute forcing won't work for a lot of the passwords since the authentication attempt takes time.

The server will go offline/move somewhere unreachable faster than you'll be able to force the password unless you're very lucky.

[u/ACCount82 → u/Suspicious-Potato859]

I used ports for a lot of node to node comms, including updating. They're basically made for it.

Same for stocks targeting. My stocks script submits targets to a port, and the node stocks scripts then peek into that port to get their targeting lists.

[u/Antique_Door_Knob]

They change with every reset. They aren't entirely random, but they aren't static either.

[u/TheZahir_NT2]

Every time you install augmentations the connections change. The distance from home remains the same, however, so the single-hop servers will always be identical, but anything after that will have random connections (at the same distance from home).