q3ext
Anonymous
30 Jul 2003, 20:13Hello,
the q3ext library is not documented in the help file.
I've tried to use Quest Beta 3.5 and I created an object this way :
define object <ring>
look <A simple but nice ring in gold>
take
examine <There are some texts engraved in it>
use on <Eric> {
playmidi <wedmarch.mid; >
playerwin
}
give to <Eric> {
playmidi <wedmarch.mid; >
playerwin
}
end define
I set !include <q3ext.qlb> at the beginning (I thought it could be good)
What is strange is when I play if I give this ring to Eric I got an error message "Hard as you try, you find you cannot do that."
If I use the ring on Eric, it works.
And if I remove this q3ext from the source, it works correctly for both use and give.
the q3ext library is not documented in the help file.
I've tried to use Quest Beta 3.5 and I created an object this way :
define object <ring>
look <A simple but nice ring in gold>
take
examine <There are some texts engraved in it>
use on <Eric> {
playmidi <wedmarch.mid; >
playerwin
}
give to <Eric> {
playmidi <wedmarch.mid; >
playerwin
}
end define
I set !include <q3ext.qlb> at the beginning (I thought it could be good)
What is strange is when I play if I give this ring to Eric I got an error message "Hard as you try, you find you cannot do that."
If I use the ring on Eric, it works.
And if I remove this q3ext from the source, it works correctly for both use and give.
Anonymous
30 Jul 2003, 20:20sorry I didn't noticed the pdf file provided with Quest about this q3ext.qlb
MaDbRiT
31 Jul 2003, 05:45Hi Favardin
As you have now noticed, Q3EXT.QLB isn't actually an 'official Axe Software' library, and so not part of Quest's documentation. It is a library I wrote to add some functionality for my own purposes and released for others to use if they chose to do so.
The reason it doesn't seem to work in your example is that you have to 'set things up a bit' at the outset, (see the pdf manual) but once you do so, the library keeps track of an inventory for each non-player actor and allows use of containers etc. Such niceties as examining a non player character and being told what he is holding as part of his description are handled automatically (once set up) in this way.
Basic approach is that if you include the library, as it overrides most of the Quest standard commands you need to make sure you use the object types it provides, or things can get a little confusing to say the least.
One other point - Q3EXT.QLB is actually obsolete. I've written a better, more powerful and easier to use replacement library which is called "typelib.qlb" and has been available (albeit a beta release) from my website since Sept 2002.
The website beta version of 'typelib.qlb' is as far as I know pretty stable, and is due (shortly) to be replaced by a further enhanced second beta release - actually it is so much improved it might be wiser to give it a different name, the beta test jury is out on that one at the moment.
Al
As you have now noticed, Q3EXT.QLB isn't actually an 'official Axe Software' library, and so not part of Quest's documentation. It is a library I wrote to add some functionality for my own purposes and released for others to use if they chose to do so.
The reason it doesn't seem to work in your example is that you have to 'set things up a bit' at the outset, (see the pdf manual) but once you do so, the library keeps track of an inventory for each non-player actor and allows use of containers etc. Such niceties as examining a non player character and being told what he is holding as part of his description are handled automatically (once set up) in this way.
Basic approach is that if you include the library, as it overrides most of the Quest standard commands you need to make sure you use the object types it provides, or things can get a little confusing to say the least.
One other point - Q3EXT.QLB is actually obsolete. I've written a better, more powerful and easier to use replacement library which is called "typelib.qlb" and has been available (albeit a beta release) from my website since Sept 2002.
The website beta version of 'typelib.qlb' is as far as I know pretty stable, and is due (shortly) to be replaced by a further enhanced second beta release - actually it is so much improved it might be wiser to give it a different name, the beta test jury is out on that one at the moment.
Al
Anonymous
02 Aug 2003, 07:30Ok, thank you for your precisions. I've found your improved library at http://members.aol.com/agbampton/html/qtips.html
At the moment I'm looking for how to use Quest with the french langage, so if there is not too much work to do, maybe I'd be interested in translating this typelib into french later (but it's not certain because of lack of time), and I don't wish also this translation would be obsolete with a new release of this lib.
Anyway, this lib. seems to be powerfull
At the moment I'm looking for how to use Quest with the french langage, so if there is not too much work to do, maybe I'd be interested in translating this typelib into french later (but it's not certain because of lack of time), and I don't wish also this translation would be obsolete with a new release of this lib.
Anyway, this lib. seems to be powerfull
Farvardin
05 Aug 2003, 12:30I'm using now your Typelib library, it's very usefull and easy to use in QDK.
It shows also to those who state Quest is limited in comparison to other IF system that it's not the case at all, and it only lack all the many libraries available on other system.
It shows also to those who state Quest is limited in comparison to other IF system that it's not the case at all, and it only lack all the many libraries available on other system.