So, apparently I just found out that there various other quest apps from
https://textadventures.co.uk/forum/quest/topic/qruunz-ezuwirsafirlgqq/user-error-issues-with-zone
mrangel: QuestKit, QuestJS, Quest6, and I'm sure there's been at least one other abandoned project along those lines)
If I get to design my quest app, it would be named Daeunquest, so people will know I made it =D
I can't wait for Daeunquest. I could use those extras. The examples of working script struck a chord. The trouble I went through editing Copilots script suggestions for some other software that wasn't Quest. And I am such a beginner coder, myself.
Lol, I am not good enough to make quest app, I am just starting a discussion so people can share their ideas, and maybe someone will make a quest app based on some of our ideas, making it come true
Implementing a working script via pressing a button and summoning a pop up example code text is relatively simple, however, seeing how there are so many internal functions hidden within the bottom left of quest app, filter, show library elements, it is going to take forever for someone to write out a demostration code for each function
But yes, perhaps we could just limit "working code examples" to only GUI functions which are not hidden as internal functions,
Also it would be great if they could expand on the number of GUI functions
1 great example is
http://textadventures.co.uk/forum/quest/topic/9-3xus0nt0yfsuyykyhlfg/external-popup-picture-over-the-gamewindow
K.V. successfully solved the issue of many pictures creating lag in quest app by making it external popup picture via external link, newbies wanting more pictures yet crashing their quest app without realizing why, are going to rage quit
But everything would be easily solved if K.V.'s code is implemented into the GUI function that everyone can easily access