Window size (RPGVXAce Editor)

[kerbew]

Hi,

I'm trying to create a event that is quite large, but I have problem with the tool (editor).

Is there a way to resize the window? I can't find any.

I need about 35 conditional branch, but now can't even see them after 10.

 

I also tried to copy even to txt-editor like notepad, but for some reason that does not work. That would make things much easier.

 

Thanks for the help.

 

[Andar]

No, there isn't.


But why do you need 35 branches nested?


With that many conditions, it's usually better to redefine the logic, and there are a lot ways how to do that depending on what those sonditions are...

 

[narcodis]

Yeah, what Andar said. What are you trying to do exactly? 35 nested conditional branches is definitely excessive, and I can almost guarantee there's a better way to do whatever you're doing.

 

[kerbew]

No, there isn't.

But why do you need 35 branches nested?

With that many conditions, it's usually better to redefine the logic, and there are a lot ways how to do that depending on what those sonditions are...

Thanks for the fast reply!

This is my first time with RPG Maker (or any other game creator). I try to create game for my kids that does not include any fighting.

There are monsters, but they attack with questions like "What is the capital of Ireland?". I was trying to create a monster that ask random question.

I was trying to create that with control variables & random numbe 0-34. Total of 35 question triggered with conditional branch == 0-34.

 

[narcodis]

Thanks for the fast reply!

This is my first time with RPG Maker (or any other game creator). I try to create game for my kids that does not include any fighting.

There are monsters, but they attack with questions like "What is the capital of Ireland?". I was trying to create a monster that randomly ask question.

I was trying to create that with control variables & random numbe 0-34. Total of 35 question triggered with conditional branch == 0-34.

To solve your problem, don't nest each condition into the "Else" of the previous condition. Just have each condition arranged one after the other like..

If var == 0

    question 0...

end

If var == 1

    question 1...

end

If var == 2...

etc.

That way it won't scroll beyond the window.

I will say it would be better to put all this code into a common event, and then have the monster event call that common event. That way if you ever feel the desire to edit the code, you won't have to edit a bunch of monster events, just the one Common event.

 

[kerbew]

To solve your problem, don't nest each condition into the "Else" of the previous condition. Just have each condition arranged one after the other like..

If var == 0

    question 0...

end

If var == 1

    question 1...

end

If var == 2...

etc.

That way it won't scroll beyond the window.

I will say it would be better to put all this code into a common event, and then have the monster event call that common event. That way if you ever feel the desire to edit the code, you won't have to edit a bunch of monster events, just the one Common event.

Thanks!

 

[kerbew]

New question.

First line (control variables randon no) is related to text area size, why? Line count randomly change because of that variable, but I cannot find the reason.

 

[narcodis]

That seems really strange to me. Are you using any scripts or anything that might interfere?

Try changing the variable and see if it still does it.

 

[kerbew]

I tried to fix the problem with this, but no help.

That seems really strange to me. Are you using any scripts or anything that might interfere?

Try changing the variable and see if it still does it.

Yes, I was using 

That seems really strange to me. Are you using any scripts or anything that might interfere?

Try changing the variable and see if it still does it.

There seems to be problem with Ace_Message_System.rb

https://raw.githubusercontent.com/Archeia/YEARepo/master/Core/Ace_Message_System.rb

I removed that and the problem is gone. Sad, I really liked Ace Message System. Maybe there is a fix, google help me!

narcodis, thanks for the help! 

 

[narcodis]

Ah, there's your problem. You don't need to remove the Ace Message System. The reason it was shrinking the window size is because of this line of code:

VARIABLE_ROWS = 21This made it so the variable 21 (ie the variable you were using) adjusted the number of rows in the message box. Looks like variable 22 will adjust the width, too.

If you don't want to use these features, change these lines of code to equal zero, so they look like this now:

# This variable adjusts the number of visible rows shown in the message # window. If you do not wish to use this feature, set this constant to 0. # If the row value is 0 or below, it will automatically default to 4 rows. VARIABLE_ROWS = 0 # This variable adjusts the width of the message window shown. If you do # not wish to use this feature, set this constant to 0. If the width value # is 0 or below, it will automatically default to the screen width. VARIABLE_WIDTH = 0Otherwise, just try using a different variable, and leave variables 21 and 22 reserved for the message system. Hope that helps. Cheers!

 

[kerbew]

Ah, there's your problem. You don't need to remove the Ace Message System. The reason it was shrinking the window size is because of this line of code:

VARIABLE_ROWS = 21This made it so the variable 21 (ie the variable you were using) adjusted the number of rows in the message box. Looks like variable 22 will adjust the width, too.

If you don't want to use these features, change these lines of code to equal zero, so they look like this now:

# This variable adjusts the number of visible rows shown in the message # window. If you do not wish to use this feature, set this constant to 0. # If the row value is 0 or below, it will automatically default to 4 rows. VARIABLE_ROWS = 0 # This variable adjusts the width of the message window shown. If you do # not wish to use this feature, set this constant to 0. If the width value # is 0 or below, it will automatically default to the screen width. VARIABLE_WIDTH = 0Otherwise, just try using a different variable, and leave variables 21 and 22 reserved for the message system. Hope that helps. Cheers!

You are too fast!

Just started to parse the Ace Message System.

Thanks, again

 

[Andar]

That is a common mistake made by a lot of people - and it's not limited to Yanfly's Message system (although I knew you were using it the second I read your bug report).


Whenever you add a script, FIRST READ it's description.


There are several scripts that use variables to communicate with events, and you need to configure and reserve those variables, or you will get strange effects whenever you use those variables for something else.