.configure //commands for dream seeker
delay #
sound on/off
last-url //no idea, if you type just .configure, it'll show this as the last world you visited
query-files on/off
query-links on/off
echo-commands on/off
graphics-hwmode on/off
debug on/off
.hub //pager commands(you can also type JUST $ for this)
add-ban
add-friend
add-game
list-friends
list-games
ping
remove-ban
remove-friend
remove-game
resume
write
.debug //debug stuff lul
profile
reboot
resume
status
trace-client
.key //changing keys during run time(you can also type JUST @ for this)
//all your keys from your keys.txt file
create-key
download-key
resume
roving-key
.script // run a script file to define command aliases
.quit
.logout //disconnect without closing the window
.reconnect
.url //connect to another world in the same window by typing .url byond://bleh:bleh
.winset "[control.param=value;...]" // Sets parameters in response to a menu or button command (or a manually typed command). You can set more than one by separating them with semicolons.
.options // Shows the Options and Messages box.
.reboot // Reboots the world.
.host // Opens hosting options box.
.profile // Profiles the running time of procs.
.screenshot // Saves a screenshot of the map.
.screenshot auto // Saves a screenshot of the map, but does not prompt for a filename. The file will be saved in the client's user directory in BYOND/screenshots.
.command // Prompts the user to enter a command, which can be one of these commands as well.
.resume
.prompt
.ping
//movement
.center .southwest .southeast .northwest .northeast .west .east .south .north .walk
//mouse functions
.mouse-over .mouse-drag .mouse-drop .mouse-down .mouse-up .dblclick .click
If you get stuck, as in unable to use a command bar after doing any of these just type resume (or $/@resume) and it'll work.
Some games will allow you to press space, to auto complete and see the list of commands and stuffs
they all have some extra parameters and stuffs, but they're not all documented, and the BYOND staff says they're so old they don't give a flying poo about them. Most of them are documented inside of the byondcore.dll, however they the descriptions of them, and the defining of the commands aren't in any real order.
!OTHER FANCY STUFF ALSO RELATED TO THE ABOVE!
Pre-defined topic calls? This is an example, of one.
You can do byond://?debug=status which is what .debug status calls. Through this, you get a list of client connections, and the time the server has been running, I also think there's other things that show up, but there have to be specific requirements. When you click the links, they are also topic calls...we're able to mimic them like in this example:
Click(o)
world << "<a href=byond://?\ref[url_encode(o)]_debug>[o]</a>"
You may also emulate the debug profiler in the same way, these commands make the profiler open in the default browser. You CAN disable these commands even if you have debug on by overwriting the "debug" topic data or whatever and not calling ..() in client/Topic
byond://?debug=profile
byond://?debug=profile;avg=0 or byond://?debug=profile;avg=1
byond://?debug=profile;switch=on or byond://?debug=profile;switch=off
byond://?debug=profile;clear=1
byond://?debug=profile;clear=1;avg=1 and so on