QuestNet Server 3.0 Beta 1 Now Available

  Axe Software Forums
  QuestNet Forum
  QuestNet Server 3.0 Beta 1 Now Available

profile | register | faq

Author Topic:   QuestNet Server 3.0 Beta 1 Now Available

Alex posted 29-08-2002 00:29 BST
QuestNet Server 3.0 Beta 1 is now available! Get it from http://www.axeuk.com/quest/questnet.htm .
Computer Whizz posted 29-08-2002 02:55 BST
May I first say that thank you Alex, this Quest Server feel's better explained IMO.
Just by reading the Arena.asl file for the first time I feel that the way you made that file was very good!
Now, my Questions:
So #null# (from <pay #null#>) means null exactly or could you put anything there (like <pay #whatever#>).
That is a very useful invention if #null# does mean null, since you could check for various things being blank so easily without putting an if statement.... nice.
[Define Options]
So what are these? Are they a way to turn these functions off?
I wouldn't exactly think people would want to turn the server message off (messages from the server) but that's just me (like, an announcement that the server's about to shutdown/get disconnected/maintanance/ect...).
And that's all my questions.... fin.
I only have this to say:
QuestNet does have a way to go: Passwords, proper Admin functions (and probably good GUI, with text-based commands to save time or whatever.... personally I'd go for mostly text based.), access levels for users (so you can apoint certain people as Admins/semi-admins, ect...) and only a few other things.
But already, most of this is possible through our programming (although we need to think about it) simply because ASL is such a dynamic and good language.
But although QuestNet is a journey away I know you'll get there and complete the product.
Good-job Alex.
Computer Whizz
Alex posted 29-08-2002 18:41 BST
#null# is just a variable name - you could use #whatever# if you wanted. I only called it #null# because I never check the contents of the variable, so effectively it's just a dummy variable.
The "servermsg" option only suppresses a small message at the top of the game window which says that the server is running a beta of QuestNet Server - obviously turning off *all* server messages would result in a pretty empty window!
If you want to send a message out saying the server is about to go down, use the MSG command in the admin window, e.g. "msg This server will be closing down for maintenance in five minutes". This message will then be sent to all users.
There is on other text command INFO in this release, which does the same as clicking the Info button to give information about a player. The next release will have a DISCONNECT command as well. At the moment there aren't many other commands you could need.

Hop to:

Contact Us | Axe Software

Powered by: Ultimate Bulletin Board, Freeware Version 2000a
Purchase our Licensed Version- which adds many more features!
© Infopop Corporation (formerly Madrona Park, Inc.), 1998 - 2000.

Author	Topic: QuestNet Server 3.0 Beta 1 Now Available
Alex	posted 29-08-2002 00:29 BST QuestNet Server 3.0 Beta 1 is now available! Get it from http://www.axeuk.com/quest/questnet.htm .
Computer Whizz	posted 29-08-2002 02:55 BST May I first say that thank you Alex, this Quest Server feel's better explained IMO. Just by reading the Arena.asl file for the first time I feel that the way you made that file was very good! Now, my Questions: So #null# (from <pay #null#>) means null exactly or could you put anything there (like <pay #whatever#>). That is a very useful invention if #null# does mean null, since you could check for various things being blank so easily without putting an if statement.... nice. [Define Options] So what are these? Are they a way to turn these functions off? I wouldn't exactly think people would want to turn the server message off (messages from the server) but that's just me (like, an announcement that the server's about to shutdown/get disconnected/maintanance/ect...). And that's all my questions.... fin. I only have this to say: QuestNet does have a way to go: Passwords, proper Admin functions (and probably good GUI, with text-based commands to save time or whatever.... personally I'd go for mostly text based.), access levels for users (so you can apoint certain people as Admins/semi-admins, ect...) and only a few other things. But already, most of this is possible through our programming (although we need to think about it) simply because ASL is such a dynamic and good language. But although QuestNet is a journey away I know you'll get there and complete the product. Good-job Alex. Computer Whizz
Alex	posted 29-08-2002 18:41 BST #null# is just a variable name - you could use #whatever# if you wanted. I only called it #null# because I never check the contents of the variable, so effectively it's just a dummy variable. The "servermsg" option only suppresses a small message at the top of the game window which says that the server is running a beta of QuestNet Server - obviously turning off all server messages would result in a pretty empty window! If you want to send a message out saying the server is about to go down, use the MSG command in the admin window, e.g. "msg This server will be closing down for maintenance in five minutes". This message will then be sent to all users. There is on other text command INFO in this release, which does the same as clicking the Info button to give information about a player. The next release will have a DISCONNECT command as well. At the moment there aren't many other commands you could need.