[RM2K3] TEST PLAY SHORTCUTS?

Posts

Pages: 1
When I am in Test Play, I did some key combinations to see if I can skip a fight to watch a cutscene play. Nothing worked out. Is there like a list of some shortcuts to do certain things while in Test Play?
Hi XiconDestoroyah,

The main way to do this is to set up Debug/Test Play detection within your own game. When you are test-playing, set a switch that signifies that to ON, and have a lot of conditional branches that check to see whether this switch is ON or not. This way, you can quickly skip segments of your own code, if you want to.

The only built-in way to do this is by holding down Ctrl when walking around on the map, which will skip random encounters and impassible tiles.
LockeZ
I'd really like to get rid of LockeZ. His play style is way too unpredictable. He's always like this too. If he ran a country, he'd just kill and imprison people at random until crime stopped.
5958
Zach is wrong, there are a couple other hotkeys that you can use in test play, which are much more straightforward.

F9 lets you change any switch or variable in your game. It starts out on switches, but if you press left on the first page, it goes to the variables instead.

F11 lets you save anywhere.

The shift key makes text boxes show up instantly. This won't really let you sequence break or anything, but it definitely speeds up cut scenes.
Corfaisus
"It's frustrating because - as much as Corf is otherwise an irredeemable person - his 2k/3 mapping is on point." ~ psy_wombats
7874
If you want to watch a part of a cutscene, either copy-paste that section of the scene into a separate testing map or remove the battle temporarily. If you have a map that has several autoplay/parallel process events sequenced up, you can also set up different switches that you know aren't activated yet as a temporary block and remove the switch condition of the page you want to test.

It's all in what you need for that moment specifically.
For testing, I always include on my main character some ability that's free and instantly kills all enemies so that I can skip battles if I want to. Though really, holding down CTRL is probably the better solution.

Also, setting a variable when test playing is super helpful if you want to add custom debug features. You can set the variable by having an auto-start common event which sets it, and then simply have your New Game code remove it. That way if you start a new game, debug = false, but otherwise debug = true.
I'm going to take Corfaisus's since I just realized how easy it is. Thank you guys for taking consideration in replying. :)
Pages: 1