Workaround mania supplementary findings! This allows you to make a simple CMS in the DBS. This method will also let you make custom one-line messages that don't advance until the user presses Enter. How to Make it Work 1. Make battle backgrounds that show each possible position of your menu, including the cursor. 2. Make a battle event that first waits for 0.5 seconds, then changes the battle background to the first position on your menu, then calls the common event described below. 3. Make a Common Event that uses Key Input Processing to handle the CMS, as you would for a normal CMS, except that "wait until key pressed" must NOT be checked. If it is, your battle will freeze. Change your Common Event to handle the key input appropriately. Once your common event captures a valid cursor movement, pass control back to the battle event.* 4. Check to see what the value of the variable is. Change the battle background to the position that matches the new value. 5. Call the common event again. 6. Repeat steps 4 and 5 many times (you can't use Labels or Loops in a battle event, so you need to repeat this a large number of times so that the player could reasonably select an option). 7. Be sure to include code that bypasses all these checks if an option is selected. 8. Once an option is selected, change the battle background back to what it should be and react to the choice. * This explanation assumes knowledge of basic picture-based CMS construction. If you don't know how to do that, then learn that first. Limitations and Caveats - Since you're using battle backgrounds, the menu can't be under any character or monster sprites. - As mentioned above, this is sort of a "hack". A player who moves the cursor a lot without making a selection will exhaust the battle event. Be sure to handle this possibility in your code. - This is not a general-use hack. It is best used for planned encounters where you know what the battle background will be. Otherwise, you would have to make menu sets for every battle background.