You can compare and find what rule changed it, I tried a few like diagonal walking and links position fix in dungeons etc. and didn't figure it out.
Go left 2x
down 1x
right all the way
down 1x
left all the way
go inside and get the money
follow instructions in reverse to reach the first shop which sells bombs.
http://www.mediafire.com/file/zhkdgzwzbwf/A Link To The Darkness 3 original.qst
http://www.mediafire.com/file/zzwnj0wyztm/A Link To The Darkness 3 upgraded.qst
Well, the bug doesn't occur when I take the original file and immediately save it without touching anything else. So it isn't really a bug, I think.
It seems to be that the shop's table has been made solid, whereas originally it was walkable.
Look at the upgraded version, all I did was change some rules and add diagonal walking. I would not think any of the rule changes would stop shops from working but it does.
Ah, right, sorry, I got confused.
EDIT: This is actually a consequence of hard-coded behaviour in Diagonal Movement. You'll probably just have to adjust that screen if you want to use Diagonal Movement in that quest.
I disabled Zelda 3 "diagonal" movement and still can't pickup items from that shop.
Well, this isn't my day at all.
It's one of the rules I've enabled that is causing it, I'm not sure which and I did try disabling some but it's really, really tiring testing them. Is there a command line parameter to skip the AGN logo when starting Zelda Classic?
A straight upgrade without tinkering with rules doesn't affect shops in any negative way (that I could tell)
OK, I figured it out, finally. It's "No Position Offset Of Screen Items". That rule was only introduced recently so I forgot it existed.
_L_ wrote:OK, I figured it out, finally. It's "No Position Offset Of Screen Items". That rule was only introduced recently so I forgot it existed.
What does that rule do anyhow? I see no description for it in the change log.
This thread has the not a bug icon, does that mean it's been fixed, it doesn't exist or what?
It was narrowed down to a rule I had enabled. So yeah not a bug.