6 replies to this topic

[Lynel Richie]

Alright! I am done.

Give me one more day clear up just a few things from the Beta Testers and you all can play.

Thank you all very much for all the help and inspiration. If someone told me I'd get chance to make my own Zelda quest when I was kid I would have said they were crazy. Here we are thought.

[Moosh]

Congrats on the finished quest! Seems like you just blew through development on this one where many would've slowed down. I'm excited to give it a try.

[Mani Kanina]

Yeah, GJ on wrapping up the project. I'm not sure if I will give it a spin personally, but I'm definitively interested in how the quest ended up being.

[Titanium Justice]

Congratulations on getting it done! I know when I finished my first quest it was an exciting and surreal experience, like a "I can't believe I actually did it!" kind of experience. I can imagine you're probably feeling something similar right about now.

 

I'll make sure to give it a go when it comes out.

[Aevin]

Congratulations! Finishing stuff is such a great feeling. I might give it a swing. Looking through the screenshots ... I must ask that you leave poor Will alone.

[Lynel Richie]

I put it at midnight. Have any of you tried it? Someone reported a runtime error and I'm freaking out. 

[Lüt]

Someone reported a runtime error and I'm freaking out. 

That'll happen if you open a 2.55 current-alpha quest in an older-alpha build.

 

The current alpha is 74. As a test, I opened the quest in alpha 28, and it also crashed with a runtime error. However, it loads in alpha 74 perfectly fine.

 

This is likely because quest file structure is still being expanded to accommodate more data amounts and more data types, so when older versions try to read amounts and types of data that they're not made to handle, they don't know what to do with it and have no other choice than to stop functioning.

 

Just be sure people are using the ZC version the quest was built in as their minimum program version and it should be fine.