Some conversation~dialogue help~guide links:
http://docs.textadventures.co.uk/quest/guides/http://docs.textadventures.co.uk/quest/scripts/ask.htmlhttp://docs.textadventures.co.uk/quest/ ... tion1.htmlhttp://docs.textadventures.co.uk/quest/ ... tion2.htmlhttp://docs.textadventures.co.uk/quest/ ... ktell.htmlhttp://docs.textadventures.co.uk/quest/ ... stion.htmlhttp://docs.textadventures.co.uk/quest/ ... tions.htmlhttp://docs.textadventures.co.uk/quest/ ... tions.htmlhttp://docs.textadventures.co.uk/quest/ ... swers.htmlhttp://docs.textadventures.co.uk/quest/ ... _menu.htmlhttp://docs.textadventures.co.uk/quest/ ... witch.htmlhttp://docs.textadventures.co.uk/quest/ ... cript.htmlhttp://docs.textadventures.co.uk/quest/ ... _case.htmlhttp://docs.textadventures.co.uk/quest/ ... tiple.htmlhttp://docs.textadventures.co.uk/quest/ ... lates.htmlInstead, for now, you might want to use the built-in 'ask~ask a question (whatever it is called)' Function:http://docs.textadventures.co.uk/quest/scripts/ask.htmlhttp://docs.textadventures.co.uk/quest/ ... tion1.htmlhttp://docs.textadventures.co.uk/quest/ ... tion2.htmlas it sets up the scripting for you (in code it looks like this):
http://docs.textadventures.co.uk/quest/scripts/ask.html(you don't need the '=true' and '=false', see the link above for writing the code without my use of '=true' and =false', as Jay hates me doing it, but I like to show what's fully happening in the code, so people new to coding can see and understand it better, and also for me, it helps with the organization even if it does make the code more messy~cumbersome, as I know what each code line is doing, esepcially when that 'else' code line is many lines down from what it is an 'else' of, so I can properly code it for the right thing. Though coders understand what's going on with the code, so they like to 'keep it simple', which is a good creed, so long as you already understand what and how the coding works and can code it properly)
msg ("The soft, female tones of your alarm clock drift into your subconcious. /"Good morning, sir, this is your eight am wake-up call. Would you like breakfast this morning?/"") {
// you choose 'yes' (true) or 'no' (false)
// internally it converts your choice of 'yes' into true or 'no' into false
if (result = true) {
// for your thread topic: goto 'pageX'
} else if (result = false) {
// for your thread topic: goto 'pageY'
}
}
----------------
a day of trying to figure out how to code, do something (in code or via the GUI~Editor) for~in quest, is quite normal, laughs.
you've no idea how many minimum of 6 hours I've spent on doing just 1 single simple thing in code, laughs. Let alone trying to do coding that takes me 3 days to a week to finally figure out... argh! (then Jay or the other programmers come around and do it in 5 minutes, and it's so much more efficient, clean, and clear coding, GRRR! lol
)
(it's taken me 2-3 years to be at where I am now... it is really a SLOW process, you're trying to do too much and too advanced stuff... try to take a lot more slow and do small and simple things. Don't try to figure out how to do something on your own right now, that's why it's taking you 3 hrs, instead pick something that is already done for you, and learn it, understand it, be able to do it yourself from memory. Build up your knowledge from others first, then you'll be able to figure out stuff on your own, unlike now, as you don't have a knowledge base to help you with figuring out how to do stuff)