Page 1 of 1

Dev build/Linux: %loc not expanded (marked locaion confusion?) [RESOLVED]

Posted: Sat Dec 15, 2018 6:49 am
by pango
When asking for a quest's NPC location, town people may mark the location on the map but are unable to use the marked location's name in the conversation, as in
"Beggin' yer pardon XXX, but most folk know this. is west of where we're standing"
"Always glad ta help you, XXX. is a ways east of here"
loc not expanded.jpg
loc not expanded.jpg (283.46 KiB) Viewed 1527 times
PS: It doesn't seem consistent; It worked when I asked for the location of the quest giver

Re: Dev build/Linux: %loc not expanded (marked locaion confusion?)

Posted: Tue Jan 08, 2019 7:49 am
by Nystul
where is->location works a bit differently than where is->person
last one has a problem with %loc macro, yes.
the location name should be expanded with %loc macro - will take a look

but regarding just the general direction without map reveal, like (XXX being the pc name here):
pango wrote: Sat Dec 15, 2018 6:49 am "Always glad ta help you, XXX. is a ways east of here"
Vanilla expands this in just the same way without either the person nor the location name

edit: I just tested in dfunity and it seems to work fine for me:
Image

could you please countercheck?

Re: Dev build/Linux: %loc not expanded (marked locaion confusion?)

Posted: Thu Jan 31, 2019 9:00 pm
by Hazelnut
Closing this as unable to reproduce if no one gives more info in next day or two.

Re: Dev build/Linux: %loc not expanded (marked locaion confusion?)

Posted: Tue Feb 05, 2019 7:57 am
by Nystul
I think I know now after watching some of Steep's videos (https://www.youtube.com/playlist?list=P ... 1AosypKQ_D)
It does not work correctly for Residences (all other building types resolve correctly to their name)

I think this is a regression bug since I am pretty sure this worked already some time ago
Will take a look when I have some time

Re: Dev build/Linux: %loc not expanded (marked locaion confusion?)

Posted: Mon Mar 11, 2019 9:10 am
by Nystul
pr is issued solving this bug