20,365
edits
Customizing/Binding: Difference between revisions
m
mentioned the use of film-jumping in speedruns
(overall copy-edit; clarified how Dev Mode interacts with key bindings and corrected misstatement that film keys only work in Dev Mode) |
m (mentioned the use of film-jumping in speedruns) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
In the absence of a control settings screen within Oni, most players set their key bindings manually by editing '''key_config.txt''', though there are GUI solutions like [[Oni Key Editor]] and [[KeyConfig]]. | In the absence of a control settings screen within Oni, most players set their key bindings manually by editing '''[[key_config.txt]]''', though there are GUI solutions like [[Oni Key Editor]] and [[KeyConfig]]. | ||
{{UpdatedForOniX|1.0.0}} | {{UpdatedForOniX|1.0.0}} | ||
{{TOClimit}} | {{TOClimit}} | ||
| Line 8: | Line 8: | ||
bind *key* to *action* | bind *key* to *action* | ||
So if you wanted to | So if you wanted to kick with the '/' key, you would type: | ||
bind slash to kick | bind slash to kick | ||
| Line 229: | Line 229: | ||
===screenshot=== | ===screenshot=== | ||
*This stores a screenshot in BMP format (uncompressed) in Oni's folder with the name '''screen_shot#####.bmp'''. | *This stores a screenshot in BMP format (an uncompressed bitmap) in Oni's folder with the name '''screen_shot#####.bmp'''. | ||
*The size of the screenshot is normally the resolution specified in '''Options''', but you can set the runtime variable <tt>gs_screen_shot_reduce</tt> | *The size of the screenshot is normally the resolution of the game, as specified in '''Options''', but you can set the runtime variable <tt>gs_screen_shot_reduce</tt> using the Developer Mode console to downsample the bitmap by a power of 2.<br>Thus, if you play Oni in 640x480, the bitmaps you'll get will be: | ||
**640x480 if <tt>gs_screen_shot_reduce=0</tt> (default) | **640x480 if <tt>gs_screen_shot_reduce=0</tt> (default) | ||
**320x240 if <tt>gs_screen_shot_reduce=1</tt> | **320x240 if <tt>gs_screen_shot_reduce=1</tt> | ||
**160x120 if <tt>gs_screen_shot_reduce=2</tt>.... | **160x120 if <tt>gs_screen_shot_reduce=2</tt>.... | ||
*See the [[:Category:Screenshots]] page for tips on taking screenshots efficiently and without the HUD in the way. | |||
===start_record, stop_record, play_record=== | ===start_record, stop_record, play_record=== | ||
| Line 245: | Line 246: | ||
====What you can use it for==== | ====What you can use it for==== | ||
*You can use this feature to "teleport" back to a place where you've already been. "Plant" a "teleporter" by pressing <tt>start_record</tt> then <tt>stop_record</tt> right afterwards; at any later time, pressing <tt>play_record</tt> will bring you back to the last "teleporter" you have thus "planted". | *You can use this feature to "teleport" back to a place where you've already been. "Plant" a "teleporter" by pressing <tt>start_record</tt> then <tt>stop_record</tt> right afterwards; at any later time, pressing <tt>play_record</tt> will bring you back to the last "teleporter" you have thus "planted". | ||
*Expert gamers have used the above "teleporting" technique to perform so-called "film-jumping". | *Expert gamers have used the above "teleporting" technique to perform so-called "film-jumping", which is abused in [[Videos#any%|any% speedruns]]. | ||
===cutscene1, cutscene2=== | ===cutscene1, cutscene2=== | ||