Hi,
after hours of debugging, I finally found an answer bug that was bugging me.(pun intended.
In handler.c
get_number is called for find_target_room. The issue here is if you use goto 9.king for example. It would corrupt the string, and all I would get is target not found.
After some serious debugging, I found that num would be 9, but the mobobjstr would return kngn.
I tried this on at, and anything that required get_number.
It did not affect anything such as 10.king or jupiter, 2.jupiter because the strings were longer.
Now honestly I always worry a little on a strcpy. After many debug statements I finally tracked down the bug to this little ole line...
strcpy(*name, ppos);
I replaced it with: *name = strdup(ppos);
Wallah! now you can do any type of x.king, and I validated it against all things that used find_target_room.
I am not sure some would consider this a bug, but when your immortals cannot goto a specific king when there are 30 of them, it bugs people. Then I heard about "at", and so on.
Just wanted to let others know this.
Cunning