Forum

Regarding the movement between restricted locations. The rules only state that it cost two cubes if you go from an open location to a restricted. As I see it (and have played it so far), this means that it cost only one cube to move between two restricted locations. I will play it this way until Martin say something else. I do think it is the right interpretation tough.

Regarding the movement between restricted locations. The rules only state that it cost two cubes if you go from an open location to a restricted. As I see it (and have played it so far), this means that it cost only one cube to move between two restricted locations. I will play it this way until Martin say something else. I do think it is the right interpretation tough.

Agreed. With the exception of Location A, all Restricted Locations require Players to cross a body of water from the Open Locations - this would take more effort (waiting for ferry, etc.)

Martin just confirmed that my interpretation of the rules was right, it only cost two time cubes to go from open to restricted, not from restricted to restricted.

...Place the Machine on a Sectore NEARBY the Kid's current Location. Then move along the grid according to the Movement value on the Machine Sheet.

...Move the Machine's miniature to the same Location as the HACKER. It will now go with that Kid ,using Locations instead of the grid Sectors.

A hacked machine move together with the kid on the various locations, like your own little dog. If you do the machine ride action, the kid will take a ride with his machine. Now you move out the machine to a nearby sector and then you move the machine on the sectors up to the machines movement, where the kid will step off the machine to a nearby location and the machine will again start follow the kid (so it is also moved to the location). Other kids can for free move with the machine if they where on the location where the machine started (there is a limit how many kids can ride the machine at the same time).

So if a kid who is the lead hacker of a machine (so he controls it) moves from M to G, by bus, then he simply moves his standee from M to G and also moves the hacked machine to G. If he then decides to do a machine ride, he move the machine to a nearby sector (either C5, C6, D5 or D6), lets assume D5. From that sector he now moves the machine (with himself and possible others as riders) along the sectors just as a machine moves (so not diagonally), for example to D3 (two moves). From D3 he now has to disembark the machine into a location. He is nearby I and E, he chooses I. He move his standee and the machine to the location I (and any other kid that came along for the ride).

A hacked machine stay hacked until there is a reset. So it will follow his master home, staying outside in the bushes and if there is no reset (no firmware upgrade), then he will be there for another day. If there is a reset, the machine have moved during the night to his starting position (where he started the scenario from) with a new set of (unknown) firewall tokens.

A hacked machine stay hacked until there is a reset. So it will follow his master home, staying outside in the bushes and if there is no reset (no firmware upgrade), then he will be there for another day. If there is a reset, the machine have moved during the night to his starting position (where he started the scenario from) with a new set of (unknown) firewall tokens.

Awesome (I've been resetting them every night).

Also, is there ever a point when an ERRATIC Machine loses this condition (and returns to the normal RESPONSE card?
e.g. - if you successful HACK an ERRATIC Machine, when a FIRMWARE UPGRADE happens, will it also lose the ERRATIC condition during the RESET?

I don't think so. If a machine become erratic is controlled by diary cards. Firmware upgrade only reset hacked machines to their starting position (and you remove the firewall tokens), the response card remains.