List of default commands

Avantar
Hi all!

I was just wondering if there is somewhere where I can find a list of all the standard commands you can use in quest like:
look at, put...in.., take and so forth
Maybe I haven't looked hard enough, but I can't find it.

I am struggling in particular with the 'look in direction of' command - I have tried lookdir, but either I am using it wrong or it is not a command; since it states that it does not understand my command.

Thank you in advance

Let me amend my question a bit: Yes I would like a list of commands, but also: Can I have these commands work for both the object name and alias?
If I say: take letter or take Summons letter (which is the name of the letter), they should both work. This should apply for all standard commands. I believe that if you change your exit alias to something other than compass directions, it won't work either for 'Look'

The Pixie
Have a look in the English.aslx file in this folder to see what is there (not all commands will actually do anything):

C:\Program Files (x86)\Quest 5\Core\Languages

For looking in a certain direction, create an exit, then click on the exit itself. There is an option there to have it as only a look direction and also somewhere to type the text the player will see. The command (if to the north) is LOOK NORTH or LOOK N.

Avantar
Thank you Pixie,

I was not sure where to look in the core files.

HegemonKhan
you can see all of the default~"core" codings (commands, functions, and etc) in two ways:

1. the safe way:

using the GUI~Editor, on the left side in the "tree of stuff" (or just the lower left corner of the entire screen, lol), is the "filter" button. Either, move your mouse pointer over it or click on it, to make it pop up the "show library elements" button, which you click on (it's a bit difficult to do so, due to it's "flashing" pop up and disappear nature ~ at least on my computer anyways, lol).

Filter -> Show Library Elements

what this does is to reveal (unhide) the default coding (the default libraries: English.aslx and Core.aslx, actually it reveals all of your included libraries' code contents, such as if you included~added Pixie's numerous libraries, along with the default two libraries).

just look again in the "tree of stuff", as now you'll see a lot of light-grey text~font new stuff, this is the code content from your libraries, such as the default commands, functions, object types, and etc.

it's similar to how you can see the "inherited" attributes (also in light grey text~font) on the right side detail panels of objects.

2. UNsafe way (Pixie already mentions this way):

open up the actual library files of~from the actual quest program folder.

---------------------------

this default code content, is Alex' underlying code, that allows quest to work, such as your "take" command, and etc things. The "core" coding of quest, as it is aptly named.

I believe that the "core.aslx" library file, compiles all of the other (individual) library (.aslx) files into itself, so quest only has to load that single "core.aslx" library file, for quicker initialization of quest.

but, I don't really understand about how software programming works, as there's also the ".dll" files too. I'm just starting to learn quest's in-game coding, lol. Eventually~hopefully, I'll be able to learn about software progamming, and etc programming.

-------------------------

it would be very convenient~nice for this default code content to be on the wiki, but that is A LOT of work for someone to do.

------------------------

Alex does have a forum~board~site for open coding development of his quest software, but I haven't looked at it myself yet. So, I don't don't if Alex might have the core quest coding up for people to view, or if it's just the fancy software coding stuff.

The Pixie
There is actually two types of "core" code. One is the program itself, consisting of the quest.exe file and various .dll files. These are written using .NET in C# and Visual Basic, and then compiled into the .exe and .dll that you download. You can see the code here (good luck working out what it is doing!):

http://quest.codeplex.com/SourceControl ... #README.md

Then there is the Quest code. This is written in the same language that your game is, and is all on your hard drive in the program files folder (and can be viewed as HegemonKhan says from within Quest). What core.aslx does is to tell Quest to load in the other files Quest needs. I do not think it compiles anything. When you publish a game, all the code you have created is combioned with all the libraries that core pulls in and any others to make one big text file, which is compressed just as a .zip file (and I think you can even change the name so it ends .zip, and then open it up as any other .zip file).

In general script commands are defined in C#/Visual Basic to do the low level (fundamental) things. "Quest Functions" (as the Wiki calls them) are also defined in C#/Visual Basic, but "Core Functions" are defined in Quest code. You can overwrite Quest Functions and Core Functions, but not script commands, by the way.

Silver
HegemonKhan wrote:you can see all of the default~"core" codings (commands, functions, and etc) in two ways:

1. the safe way:

using the GUI~Editor, on the left side in the "tree of stuff" (or just the lower left corner of the entire screen, lol), is the "filter" button. Either, move your mouse pointer over it or click on it, to make it pop up the "show library elements" button, which you click on (it's a bit difficult to do so, due to it's "flashing" pop up and disappear nature ~ at least on my computer anyways, lol).

Filter -> Show Library Elements

what this does is to reveal (unhide) the default coding (the default libraries: English.aslx and Core.aslx, actually it reveals all of your included libraries' code contents, such as if you included~added Pixie's numerous libraries, along with the default two libraries).

just look again in the "tree of stuff", as now you'll see a lot of light-grey text~font new stuff, this is the code content from your libraries, such as the default commands, functions, object types, and etc.

it's similar to how you can see the "inherited" attributes (also in light grey text~font) on the right side detail panels of objects.


Wow, there's a lot of them. I wasn't expecting that many. :shock:

This topic is now closed. Topics are closed after 60 days of inactivity.

Support

Forums