![]() If the variable did not already exist in your q3config.cfg file, it will not be stored when closing the game. /set - Sets a cvar from console, even if it wasn't declared in C code.It works if the variable (also known as "cvar") was first declared in C source code, and usually it is the case, but sometimes you may need to use particular commands to set a variable: To set a variable, you can usually simply write \ in console. Usually, this file is continuously updated and is overwritten every time you launch OpenArena. ![]() It is placed to the "current folder" (usually, where OA executable is -your "basepath" folder-, but may differ) of course, it needs the user account which runs OpenArena has got write permission there. Creation or not of such file depends from the options SDL library has been compiled with. It gets standard text output generated by the game, typically the command console log, so it may be used as an alternate way to log console. Also, SDL library may automatically create a file named stderr.txt (along with a file named stdout.txt), not related to your "logfile" value ( stderr.txt is created by the SDL library, not by OpenArena engine).In some cases you may find a "crashlog.txt" file in your homepath\ after a crash.In some cases, if the game "crashes" forcedly shutting down itself, the window informing you of the error may ask you "Copy console log to clipboard?": if you select "yes", console log will be copied to your operating system clipboard, and you will be able to "paste" it into a text file, using a text editor program.If the game crashes on startup, you may find it useful to enable logfile directly from from OS command line/shortcut (e.g. It creates a log file named qconsole.log in your homepath\ folder. May be useful for debugging server crashes. "Buffered" means that the file on the disk is actually updated after a specific amount of data accumulated in memory: this allows to make less disk access, but may lose most recent lines of log in case of program crash. It is also possible to use /logfile to have the game start creating a text file containing all console output that will follow: 0=no log 1=buffered 2=continuous.For example, if you type \condump test.txt, a text file called test.txt will be created in your homepath\baseoa (or homepath\current_ mod) folder, containing all the messages you currently have in your console. You can export current console log to a text file, simply using the command \condump.You can scroll console log with PageUp/ PageDown keys, but sometimes it is useful to check its output in a text editor. Very useful to paste a server address:port to be used with /connect command. You can paste text from your Operating System clipboard into OA command console (e.g. You can press Insert ( Ins) keyboard key to switch between text insert and overtype modes. When using the specific dedicated server executable (oa_ded), instead, you do not need the slash before the command.Ĭommand names usually are case-insensitive (e.g.: both \map_restart and \MAP_RESTART will work), but some of them may be case sensitive. Note: make the command begin with / or \, or it will be considered a simple text message, like with the command "/say" (having no effect, but shown to other players). if you check them from main menu, before having entered a match, previous value stored in your config file may be erroneusly indicated as "default" one, and some variables could even be referred as not existent. Warning: you should check default values after starting a match. Writing a variable name without setting its value will return the present value, and often also its "default" value. ![]() ![]() For example, if you write /map and press tab, you will see there is also a command called map_restart if you write \map_r and press tab, the command will be completed to \map_restart if you write \map a and press tab, you will see the list of all the maps where the name begins with "a". You can use the "tab" key to autocomplete some commands. You can use Ctrl Home and Ctrl End keys to reach the top and the bottom of the log immediately. If you scrolled back the console, it will not scoll automatically when new messages are added (not even if you close and open it again): you have to scroll it to the bottom (to the last line), and it will return to act normally (showing the last messages as they are added). You can use PageUp/PageDown keys to scroll view (to see previous messages). You can use up and down arrows to see previously used commands. bind g say "Hello" (when you press 'g', you'll send a message "Hello")) Model head change: /seta headmodel "skelebot/red" Note: it has been reported that "Microsoft eHome" keyboard drivers could cause problems in pulling down the console. You might find other places that say press: ~, ', `, ½, ^, §, \ or æ but Shift Esc works on most keyboards. To "pull down" (show) the console press Shift Esc.
0 Comments
Leave a Reply. |