If we're really talking about what "makes sense" in character, it doesn't make sense that you can only open a gate to a "room" if a "named" NPC or player is there.
If we were playing a tabletop rpg or writing a novel, I would say it makes sense for a character to be able to open a gate to any point he is familiar with in the world, regardless of who happens to be standing there. The "target" thing seems more like a coding limitation since it would be hard to allow players to type in the room they wished to gate to.
Anchors would be a great addition to the game though, adding a completely IC way of maintaining the historic functionality of gate and resolving recent problems.
Quote:
[Spells help] Transport Spells
Syntax: cast 'anchor' <name>
Anchor allows a skilled caster to focus the gate spell to specific areas. Anchor creates a magical beacon to which anyone, who knows the name specified on creation, can open a magical gate. The beacons may last for days or until affected by dispel magic.
Quote:
Obvious exits: e nw sw
A shimmering magical beacon is here.
A dull magical beacon is here.
o=======
oAffect: 'detect magic'
o00o00o00o00oo00
>look beacon
A magical beacon shimmers and swirls with a bright aura.
You are able to make out the word, "XXDULRIKSBEACON" as it flashes along the surface.
A shimmering magical beacon is made of energy and size tiny.
>look 2.beacon
A magical beacon absorbs ambient light in this area.
You are able to make out the word, "XXHAHAEVIL" as it flickers among the shadows on the surfice.
A dull magical beacon is made of energy and size tiny.
Ideally, a character would not be restricted to a single beacon per person. It would work like rift as far as duration, limits per room, dispel magic and concentration required.
In order to prevent abuse by attempting to mimic traditional gate targets with new beacons, the prefix "XX" could simply prefix all beacon names.
Anyone with access to detect magic would be able to see the name of the beacon.