I'm rather confused by this. I was playing around in a custom quest that was most recently saved in b319 but had most of the work done in earlier versions, and for some reason, I can't use Potions. They simply don't show up in the subscreen at all. The Letter shows up fine, and when it's used, it changed to the Letter (used), sprite and all (inconsistent with earlier versions, forcing tile 0 to appear on old quests) - and potion shops begin their selling. However, no matter what I do, the Potions don't appear as if though I never had them. Even grabbing a potion item without ever having had the letter causes the game to act like it's nothing. I checked the subscreen, and it's set to "Original" with no modifications. I can't replicate this in a new quest either; I'm really baffled.
This is the quest:
http://files.filefront.com//;7622315;;/
For general convenience, there's a Blue Potion one screen right of the player's starting position and the Letter one screen left.
Not really a bug; your item properties are messed up. Find the two potions in the item editor, and make sure "Equipment item" is checked. That should fix your problems.
I'm not sure why "Reset defaults" doesn't work in this case; that's definitely a bug. Investigating.
"Default" button is fixed in the next build.
On that note, I never edited the potions in the item editor at all. I remember my triforce got messed up too for that matter; is there a general bug in the way quests from older builds are saved in the newer builds when converting to the new item editor, and was that fixed with this bugfix?
I have no idea; if you get any new information about that, please do let me know.
What I suspect is that an earlier build was buggy and corrupted some item data in some quests; people then saved their quests without noticing. I don't think the bug is still around now: if it were, then loading old quests to play them would also be buggy, and so far that hasn't been reported.
Quest corruption bugs are always very sneaky because they rarely can be reproduced on demand; for now I just have to hope that the bug has disappeared or that new clues as to what's causing the bug will turn up :shrug: