Things about the "Show Choices..." event

[Shiny Umbreon]

I have two questions regarding the "Show Choices..." event:

First, I know it creates the choices in the same area as the message as long as it fits (or it is two lines or something like that); otherwise, the message will disappear and a new window will appear only for the choices. I want to know how can I make the choices appear even if they are a lot or the text is long. The second thing is about the text of the choices. I know the cursor thing is created in the Window_Message script, but I can't find where the text itself is scripted. Specifically, I would like to know where is the 'x' and 'y' of this text are placed so that I can change them. Changing the 'x' and 'y' from the Window_Command script doesn't work.

All this through scripting, obviously. Thanks in advance for the help.

 

[Brewmeister]

The text for a Choice is drawn by the same statement as the text for a message.
The cool thing here is you can use \N[1], \N[2] for choices, and the other message formatting commands.

Line 144 in Window_Message

If you move the choices, you will also have to adjust the update_cursor_rect method to match.

Be Well

 

[Shiny Umbreon]

Problem 1:
I already checked, and, when your lines of text and the number of choices exceed 4, a new window is used for the choices. Does anybody know how do I undo this? I want the choices to be placed in the same window always.

Edit: I fixed everything regarding problem 2 so my ony trouble now is with problem 1. You were right about the "\n" thing; I just needed to understand it better.

 

[Shiny Umbreon]

Bumping. I just need to disable what makes the choices appear in a new window. Any help is appreciated. Thanks.

 

[Sarkilas]

Unless you don't want to change your message script, you might wanna try the UMS. It fixes this perfectly, with an extra window for choices even if the text fills the whole box. Not to mention it also has a lot of extra features you might wanna look into.

Take care.

 

[Shiny Umbreon]

I just needed to change something in Interpreter 3, and I hadn't noticed, then tweak a few things. It works perfectly now. Thanks, anyway, FireRaven. This can be locked now, I guess.