27 May, 2015, quixadhal wrote in the 21st comment:
Votes: 0
You also don't NEED to traverse the filesystem. You can easily code a daemon to handle such things.

> clone sword
ID Description Pathname Count
– ——————– ——————– —–
1 an iron shortsword /d/foo/sword.c 0
2 an iron longsword /d/foo/longsword.c 1
3 an iron shortsword /d/blah/shortsword.c 0
4 a silver broadsword /d/foo/silversword.c 0
5 a silver shortsword /d/blah/silversword.c 0

Which sword do you want to load a copy of? 3
/d/blah/shortsword cloned.


clone is just a player command that calls clone() on the filename argument. You could easily replace it with a request to a daemon, or even augment it so typing the pathname would just do it directly.
27 May, 2015, Roobiki wrote in the 22nd comment:
Votes: 0
That could definitely work well, giving the builder the best of both worlds if you don't remove the functionality of referring directly to the VNUM (or identifier) and aren't *forced* to scan through a list every time you want to load an item.
20.0/22