WaW Console Emulator

I had said before that this wouldn't be too accurate, but now it should. In fact, it should perfectly mirror the results you'd get in WaW. If it doesn't let me know on the Forum, and I'll be back here to fix it up! If you're confused by any of this, you can check out the tutorial here

Having to rehash and resign and then load up a savegame just to test some code can be quite a hassle, so this tool should help you make sure things are in working order before doing so. Usage should be very simple. If you scroll down, you'll see an input box with the label "Execute Command"; you can type or paste a command here and see the result in the box below. For example, if you type "set mydvar myvalue", you will see that it tells you that a dvar was set... You can also use many of the other commands such as vstr, toggle, bind, etc. If you're new to modding, this should be somewhat helpful on its own, but I know a lot of people will be using this to check their menus. So, to load dvars, you can paste them into the large text input below and press "parse code", but make sure you choose the correct format! This will load the dvars similar to how WaW does when it reads a config.cfg or savegame file. WaW does something extra though - it executes the code in activeaction, so go ahead and type "vstr activeaction" and execute the command! There are two logs, one which displays some helpful information about what your code did or didn't do, and one that should display only the menu. The top one will display only the unknown command messages or, if you choose "con_minicon" as your menu type, only the "say" commands. Additionally, clicking the top box will enable you to use the keyboard controls (listed at the bottom of the page) and navigate the menu to some extent.

Additionally, I've added some commands that aren't in WaW to help you debug your code:

pressEmulate a button press. Ex: "Press button_back"
printPrint the values for a dvar
printbPrint the binds for a button (bind and bind2 binds)

Format:

  • Non-Quoted -

    The first word can be any of the set commands (seta, setu, sets), the second word is the dvar (only letters, numbers, and underscores), and everything after the space after the dvar is considered the value of the dvar. Code looks like:

    seta dvar cmd1;cmd2;cmd3
    seta dvar2 setperk "random player" specialty_quick_revive
    set dvar3 god;noclip

    Notice that the dvar values aren't quoted. In this format, the quotes aren't optional, they shouldn't be there. This is because in the savegame, the dvar values are not quoted, and thus the first level of quotation isn't escaped. This is actually better, as it allows a greater level of control in your code.

  • Line by Line -

    This was a commony recommended code format, so I've decided to add it. In this format, the dvars and their values are each on separate lines. Code looks like:

    activeaction
    bind button_start "god;noclip;vstr a";vstr b
    a
    notarget
    b
    player_sustainammo 1

    Make sure there aren't any empty lines or trailing white space at the end of the lines.

  • One to One -

    Another popoular format. Each line has a dvar, a space, and then the dvar's value.

    activeaction bind button_start "god;noclip;vstr a";vstr b
    a notarget
    b player_sustainammo 1

    In this format as well, you need to avoid empty lines or trailing blank spaces.

  • Other -

    Want to use a different format? Make a post on the Forum

Format:






Get Dvar Value:

Value:


Menu type:


Execute Command:


Keyboard controls:

button_backbackspace
button_starts
button_aa or spacebar
button_bb
button_xx
button_yy
dpad_leftleft arrow key
dpad_upup arrow key
dpad_rightright arrow key
dpad_downdown arrow key
button_lbl
button_rbr