May I suggest my solution for maximizing the efficiency of neighborly visits? First of all, it is my understanding that the game developers want players to actually visit another player's city to give neighborly help, as opposed to something super-efficient, like clicking a "Polish Culture" or "Motivate Builders" icon next to a player's name in the Members tab of the Fellowship dialog. I presume this is to keep the "visit" in the picture. Fair enough. Given that requirement, then I suggest the following solution. Simply center the fellowship shield in the Player Profile and add an outward-facing arrow on either side of the shield, like this:
Fellows are presented in the
Members tab in ranked order according to points. Clicking on the left arrow would take you directly to the city of the fellow in this list preceding the player whose city you are currently viewing. Clicking the right arrow would take you directly to the city of the next fellow in the list. The list would be continuous over the first and last player, so that if you were at the city of the last player in the list, then clicking on the right arrow would take you to the city of the first player in the list, and vice versa. Ideally, when the mouse is hovered over one of these arrows, it would display a text box showing the destination of the visit, like this:
The beauty of this solution is that one click takes you to the next (or previous) city in your fellowship. The developers' requirement that a visit actually takes place is satisfied, and the cries of so many players to minimize the clicks required for these visits is also satisfied.
A similar solution can be incorporated into the Bottom Menu around the World Map icon, like this:
These arrows surrounding the World Map icon would behave in a similar manner to those of the fellowship visit in that hovering the mouse over the arrows would provide a text box hint that tells who would be visited by clicking that arrow. I will leave it to the developers to identify a suitable ordering of discovered players that the arrows would traverse. It could be as simple as listing the discovered players alphabetically, or it could be based on ring distance, etc.
As I am reviewing the other posts in this thread, I am realizing that what I have presented here appears to be part of what astoon mentioned above in #17.