buying - Axe Software Forums

  Axe Software Forums
  Quest Developer Forum
  buying

Author Topic:   buying

Goku45 posted 03-03-2001 16:38 GMT
I'm trying to make something where you can buy items from a menu, but I can't figure out how to make it so if they don't have enough of the collectible "dollars" for instance, less than 5, thay won't get the item and 5 dollars won't be subtracted. How do i do this?
Alex posted 03-03-2001 17:40 GMT
Have a conditional action to check whether the player has more than five dollars - use the parameter
dollars; +5
In your "then" action, deduct five dollars and give the player the item; in the "else" action print a message telling the player they haven't got enough cash.

Alex Warren
Axe Software
Chris posted 22-03-2001 14:36 GMT
I had forgotten Quest was such a new programmer basis application, no wonder I outgrew it so fast.
Luridii posted 22-03-2001 18:12 GMT
Just a small query Chris, since u have outgrown Quest why r u still posting on this forum?
MaDbRiT posted 22-03-2001 21:14 GMT
Chris wrote;

quote:
I had forgotten Quest was such a new programmer basis application, no wonder I outgrew it so fast
Clearly Quest is eminently suitable for beginning level programmers to use, it is one of the easiest of the IF systems to write code for without a doubt, plus it has the Q.D.K. to make things even easier.
That Quest is easy to learn and attracts new coders is surely testimony to the fact it suceeds in its design aim - to provide an easy to use Text adventure authoring toolkit.
It's rather misleading to suggest one would as a matter of course 'outgrow' Quest. I personally code a lot of stuff in C++ these days - but I'm quite sure I don't want to use that for a Win based text I.F. game. Quest is perfectly capable, much easier to use and doesn't require me to re-invent the wheel. Unless I find something I really can't do with Quest, why make things harder than they need to be?
Just because "MicroSoft Word" is not great at performing accounting functions doesn't make it a bad word processor or provide a valid reason to critise/belittle it. It just means the user should have used an EXCEL spreadsheet which is MUCH more suitable to accountancy work - although it is pretty much useless for word processing.
"Pick your horses for courses."
Al

Author	Topic: buying
Goku45	posted 03-03-2001 16:38 GMT I'm trying to make something where you can buy items from a menu, but I can't figure out how to make it so if they don't have enough of the collectible "dollars" for instance, less than 5, thay won't get the item and 5 dollars won't be subtracted. How do i do this?
Alex	posted 03-03-2001 17:40 GMT Have a conditional action to check whether the player has more than five dollars - use the parameter dollars; +5 In your "then" action, deduct five dollars and give the player the item; in the "else" action print a message telling the player they haven't got enough cash. Alex Warren Axe Software
Chris	posted 22-03-2001 14:36 GMT I had forgotten Quest was such a new programmer basis application, no wonder I outgrew it so fast.
Luridii	posted 22-03-2001 18:12 GMT Just a small query Chris, since u have outgrown Quest why r u still posting on this forum?
MaDbRiT	posted 22-03-2001 21:14 GMT Chris wrote; quote: I had forgotten Quest was such a new programmer basis application, no wonder I outgrew it so fast Clearly Quest is eminently suitable for beginning level programmers to use, it is one of the easiest of the IF systems to write code for without a doubt, plus it has the Q.D.K. to make things even easier. That Quest is easy to learn and attracts new coders is surely testimony to the fact it suceeds in its design aim - to provide an easy to use Text adventure authoring toolkit. It's rather misleading to suggest one would as a matter of course 'outgrow' Quest. I personally code a lot of stuff in C++ these days - but I'm quite sure I don't want to use that for a Win based text I.F. game. Quest is perfectly capable, much easier to use and doesn't require me to re-invent the wheel. Unless I find something I really can't do with Quest, why make things harder than they need to be? Just because "MicroSoft Word" is not great at performing accounting functions doesn't make it a bad word processor or provide a valid reason to critise/belittle it. It just means the user should have used an EXCEL spreadsheet which is MUCH more suitable to accountancy work - although it is pretty much useless for word processing. "Pick your horses for courses." Al