I've been really curious to see a complete list of the default commands/verbs that players can enter (use, look, take, etc.) which offers some kind of definition for them or they're structure, but I didn't see anything in the documentation, or here in the forums.

The problem is, I've been really afraid of making new verbs or commands that might conflict with, overwrite, or simply be "wastefully similar" to the predefined set. So, I've been wanting to just look over them all and see how they work. Am I severely over-thinking the way adding custom verbs and commands works? And is there a document that in some way defines the existing ones? I mean, even if I have to open up a library file to check out the code directly, that would be fine, but I don't even know what file that would be.

EDIT: If someone would like me to construct such a list for the documentation, I'd be happy to do so, once I get a look at the definitions.

open~start up a game file, and in the GUI (editor) mode, on the left pane with the objects' tree, at the bottom (so lower left corner of the editor~GUI screen), is "FILTER", click on this and select the "show library elements", this reveals all of the core~default stuff in the above left pane objects' tree (they're lightly greyed fonted).

Also, I'm pretty sure that if you do make a custom verb or command, that has the same name as one of the built in verbs, commands, and~or etc, then it'll notify you, and prevent you from making it with an error.

if you want to change those default things, then (after you revealed them via the filter -> show library elements), you just click on whatever you want to change (you can also change the stuff in~under the "advanced" too, but becareful as these are more of your fundamental stuff so it has much wider range of what it effects), and then you just on the right side, there now should be an option to "copy" so that you don't change the actual core~default stuff, but are able to change a copied version for use in your game file (or as in, if you're making, a library game file, so that you can add it too another game of yours).

and yes, it would be nice if someone would put these onto the wiki, if anyone would be so kind, to take the time, to do so, lol.

Alex made quest so that you can't mess up the actual quest files. You can only mess up your own specific game files, hehe.

Oh, wow, thank you! If I hadn't known to look there, I never would have figured out the dang task bar was covering it.

the core library code that alex uses is interesting for us noobs to learn some more code of how things are done, but it's still a bit beyond me at the moment, though it's still really neat to see how the code works to set up all the base core stuff for you to work with.