MoveToShard: Maximizing it's effectiveness

MoveToShard()

Getting started

Traveler will cache portals found in Memory.Traveler for reference when using this function. In order to maximize it's effectiveness and reduce travel distance. Scouting is not needed as the script will pull all shard portal info from LOAN.

What it doesn't do

-Manage your creeps memory after it moves to a different shard (that is on you!).

Limitations

Currently (as of Dec 2020) Shard 2 and 3 have limited portals only going to a mirrored room on the other room; Shard 3 Room W30N30 will go to Shard 2 W30N30. This makes the pathing from these shards rather linear and there isn't much room for play. However, Shard 1 usually has multiple portals going to vastly different areas of Shard 0 and this allows traveler to skip around the map to find the optimal route when headed to Shard 0. With all that being said there may be times where traveling from S0 to S1 and back my be faster but due to travelers inability to access intershardMemory to pull portal information from another shard, it is unlikely you will see this logic from traveler. More support for this will be added in the future, but I am unwilling to build intershardMemory into traveler as it may overwrite what the user is doing. In the end, this will fall to the user and they will have to push those portals information to traveler. More to come.