Moveable actor tracks forces in sets rather than lists, so we don't need to worry about duplicating connections (if I've implemented hashCode() correctly...)
Changed how point and scan actors handle their connections: they don't build the force connections themselves, rather they expect to have them passed through.  This way we don't have a conflict with actors not existing when the connections are expected to exist.
hide a warning.