Go in item editor in both candles (1 and 2).
In action tab, Flame Sprite drop down needs to be set to flame. The defaults button doesn't change anything, please record in the defaults for that drop down box.
Update the default template and all proposed quests.
Well, I've just edited the defaults... not sure if the template also needs changing, though...
It shouldn't, as long as the quest loading code was updated to set it correctly at load time.
I was checking if my 2.10 quest that had the candle flame set correctly, was compatible, and guess what. The flame appeared as something else. I think there's a backward compatibility issue with the new settings for the candle flames.
It doesn't see the default setting for the older versions.
I shall fix that as well!
660:
Okay, you had only programmed the defaults. Now fix the proposed quests and the default template.
If those are broken, old quests are almost certainly broken too.
zcAmazing wrote:660:Okay, you had only programmed the defaults. Now fix the proposed quests and the default template.
Would you believe I was just about to commit that change?
Anyway, Mr. Dragon is correct: it isn't the template, but the quest loader code.
yea zcamazing was oblivious to the post directly above his :P
_L_ wrote:Would you believe I was just about to commit that change?Anyway, Mr. Dragon is correct: it isn't the template, but the quest loader code.
I understand all about this.
When the loading code is fixed, the backwards-compatablilty to older version quests is restored then? You'll turn it to a sick bug when it is fixed?
I will wait. Hope the next newer build doesn't corrupt custom quests...
read rocksfan13's last post and L's post directly after it and you will see why only part of the problem was fixed in build 660. people here push for builds to be compiled quickly thus giving developers less time to fix stuff up in each build.
Thanks for the notice, Dark Nation.
Bug still exists in 660, the most recent alpha.
The backward compatibility works though. The tile for the candle flame is correct in my quest. Which is a 2.10 quest incidentally.
zcAmazing wrote:Bug still exists in 660, the most recent alpha.
Well, okay, I suppose I forgot something.
Fixed!