Wow, I'm glad I noticed this, this is a major one.
When I open my quest with b251's ZQuest, it resets many things back to the default. For example, Link's animation changed automatically from BS-Zelda to Original, all of the new custom subscreens I set for different DMaps changed back to the default ones (Passive Magic, Active No Magic etc)... oh and all the item properties changed to 0.
Things like that happened. So you can't work on your quests on this newest build because if you do, you have to go set all these things back to the way they used to be. 😞
!!
I'm not getting this with a small sample quest. Could you please send me the original (uncorrupted) quest to which all of this happened?
Hmm... weird, this bug only happens to me with the Lost Isle file I saved on build240. But when loading quests saved on earlier version, everything's ok. So I guess this bug affects only quests saved on b240.
But I can still send you (get on AIM or gimme your email add) the LI file saved on b240 if you want to experiment with it + you'd be able to see the Bombchu bug I'm so wanting see gone. :-/
Yeah, the loading code wasn't changed since 240, so I'm very curious about what's going on.
My email is 
.
Ouch.
I can't confirm everything, as I hadn't modified too many items or DMaps' subscreens, but I can confirm at least that Link's animation reverted to Original.
I checked my Rules (all fine), Subscreens (ditto), Strings (same), and Freeform combos (couldn't be better). So, it seems that the only difference I experienced is that Link's animation reverts to Original.
Edit: Oh, those item properties. Yeah, the Item Properties (sword, hookshot, healing stuff) all reset to 0.
Edita: If you make a new quest in 240, check the Item Properties (for example), they'll be fine. But, if you then save that quest, and load it into 251, you'll get this:
Opening...okay.
Reading Header...okay.
Reading Rules...okay.
Reading Strings...okay.
Reading Doors...okay.
Reading DMaps...okay.
Reading Misc. Data...okay.
Reading Misc. Colors...okay.
Reading Game Icons...okay.
Reading Items...okay.
Reading Weapons...okay.
Reading Maps...okay.
Reading Combos...okay.
Reading Combo Aliases...okay.
Reading Color Data...okay.
Reading Tiles...okay.
Reading MIDIs...okay.
Reading Cheat Codes...okay.
Reading Init. Data...okay.
Bad token! Searching...
found.
Reading Custom Guy Data...okay.
Reading Custom Link Sprite Data...okay.
Reading Custom Subscreen Data...okay.
Reading FF Script Data...okay.
Reading SFX Data...okay.
Done.
(Emphasis mine)
Hm. Would you send that to me, too? Same as my name here, plus @linuxmail.org.
I changed the quest loading code slightly to fix something foolish I did previously, but I can't imagine that's responible for this. Still, couldn't hurt to check.
http://ohrdev.com/testaga.zip - not my quest (it's 2.2 megs zipped, and dialup sucks), but it is a totally blank quest saved with b240 (actually, the QSU of one, as it zips smaller). Open it in 251, and the Item Properties are nulled.
Yep, the quests are for some reason failing to load init data. Investigating...
Yeah, quests saved in build 240 have build set to 18 and initdata's version set to 12, and so aren't loaded correctly. There's no easy fix unfortunately; to allow all 240 quests to load correctly and to avoid nasty surprises in the future, I went ahead and moved the current build back up to 18, and fixed the appropriate parts of the initdata loading code. Oh well 😉
Well, these are alphas, I know we should all try to report bugs, but for these kinds, shouln't we not worry? No one is going to use a build when 2.5 comes out (in all its shiny triforce-of-courage-like glory) If init data failed to load when going from 2.10 (.11 16c) -------> 251 then it should be considered MAJOR.
I'm looking at this from the wrong angle aren't I?
No, you're right. Heck, it even says in the package:
[quote="WARNING-READ.txt"]It is work in progress, released without careful inspection by the developers. It may be unstable, contain missing, partially implemented, or broken features, or corrupt your quests.[/quote]
Looks like the last part came true :S
But, not badly, luckily. Just a bunch of defaults that are rarely considered, much less touched (I had forgotten that that window even existed... Imagine my surprise when I would've discovered that my fairies no longer healed, and what not!)
majoras_wrath wrote:Well, these are alphas, I know we should all try to report bugs, but for these kinds, shouln't we not worry? No one is going to use a build when 2.5 comes out
Ahem... You're very wrong unfortunately. I'm not gonna sit and wait for a stable 2.5 because it may take literally forever for it to be released. 😞
And I happen to have an almost finished quest that was moved on the betas and now builds because I really want to get the quest released as soon as possible. But yeah, I admit it was stupid to move to the builds, but it's too late to go back now. Fortunately it was only a copy of Lost Isle that got corrupted, not the actual quest which I am still building on beta15, but all these new builds are very stable and I hope I can soon start building Lost Isle with them and release the quest for some of these new builds. 😊
Developers, you still want to take a look at the Lost Isle file that was saved on b240? It seems that this bug I reported is not a real problem anymore... though I think you guys deserve to take a look at the quest anyways because it will be the first 2.5 quest and you could see the Bombchu bug that I'm so frustrated about. 😉
EDIT - Oh and I understood that b251 doesn't have this wrong version problem b240 had? So it should be pretty safe to move LI to 251? (Yeah I know builds are never really safe, but the b251 ZQuest seems to be quite flawless after the heavy testing I've been doing with it).
If fixing the bombchu means LI will be released soon, by all means send it on over 😉
I noticed in 251 there was another quest load bug - koopa changed midi loading code slightly which broke ZC/ZQ when trying to load pre-211 quests - so I fixed the problem and silently released 254. Use that instead.
Ok, I'll get that 254 right now, thanks!
Oh and I sent the Lost Isle beta for both you DD and Saffith. 😉
Oh and as I've been saying, the Bombchu bug is really the only bug that's affecting LI + I noticed that the Spin Attack doesn't work properly either (see my topic at the Suggestion Forum). If those two bugs can be fixed anytime soon, it would make me extremely happy and LI would be 100% bugfree and stable, and that would make 2.5 look even more desirable. 😊
Yeah, we're both hoping (Petoe and I) that Lost Isle would almost be like a 'launch' title for 2.5. ^_^