subscreen.qst made by dn contains errors in the z3 lttp subscreen. for instance the triforce area is screwed and the animated box that surrounds the currently highlited b button item/weapon doesnt appear correct also i havnt managed to get the arrow counter to show. do i need the bow itself before the counter appears?
subscreen.qst made by dn
You know....
I thought I opened the wrong quest, but I beleive this happened to me too, and I closed it and reopened it and it was then correct.
It seems that all subscreens are messed up in all quests.
Elise beat Castle Haunt II in the B6 and exited and opened the quest again and she still had all her items but was back to 3 hearts and link was green again, but the subscreen that had been showing a triforce in the dungeons all through the first game had changed to the big dungeon map.
thanks for the confirmation freedom.
um no freedom thats a diff. issue i never beat the game... (for this issue to occur) the error occurs straght away meaning dn made some mistakes when he designed the subscreen, as to me it is screwed compared to snortisias quests subscreen. (which is perfect aside from the items visually disapearing when you pick up the triforce fragment)
I'm aware the example I gave is a different situation, my point was that the subscreens are screwed up.... every type in every version, and very unstable, which means they are changing for no apparent reason in different situations. 😉
What seems to work one time, doesn't work the next.
Freedom wrote:I'm aware the example I gave is a different situation, my point was that the subscreens are screwed up.... every type in every version, and very unstable, which means they are changing for no apparent reason in different situations. 😉
What seems to work one time, doesn't work the next.
thanks for clarifying that freedom
EDIT: solved the issue completely, it seems that dn forgot to set the subscreen to the lttp one (he left it on bs subscreen) and he forgot to tick the true arrows rule.
if those are fixed then dn's subscreen.qst would actually be of useful initialy to people rather then people having to edit the quest themselves slightly.
*bump*
i think with the true arrows the counter should work even if you dont have the bow, arrows and quiver. (at the moment it sits at zero till you have the bow, arrows and quiver.)
what was the quest in question? (link please?)
I think all those subscreen corruption errors referred to here were resolved.
I don't know about the LTTP subscreen design of DN's.
Is that what you are wanting to check, to see if his subscreen design is accurate?
yes, either A) he made a mistake himself in the QST file or B) the version of Zelda Classic and ZQuest corrupted the quest while it is being played/viewed.
hope these still work, I'm just copy/pasting these from a notepad
subscreen_info_urls.txt
Z3 subscreen described in detail
THe top link to info seems dead but it looks like you can grab the quest.
your first link needs to be updated to the new format, http://www.armageddongames.net/forums/showpost.php?p=1051090&postcount=9
this is still botched, so i guess its the quest itself and not the program?
cool, thanks, link fixed.
Also bumped up 2 threads in open beta bugs for you.
I don't know, I'll move this back to open beta bugs so it will be sure to be seen.
I guess DN rally needs to decide.
I'll try to look at it this weekend. Is it just that quest that's messed up or are the default Z3 subscreen types messed up, too?
im 99% sure its just the quest it self, i believe there were heavy changes made at some point on how the subscreens worked which rendered your quest layout inappropriate.
if it is a bug with the Z3 subscreen, im sure it would already be posted about.
Reminder to myself to fix this.
this is outta my hands unless you already fixed it. plus i think the quest file itself really is to blame because there has indeed been quite a vast number of differences made to the subscreen system.
It *IS* an issue with the quest file itself. So, technically, not a bug. If anyone wants to take a stab at fixing it (and doesn't want to wait for lazy DN to do so), then by all means...