Status
Not open for further replies.

Mercedes90

Veteran
Veteran
Joined
May 7, 2021
Messages
105
Reaction score
27
First Language
English
Primarily Uses
RMMV
Sorry. I did mean that my posting was an error not yours. I was reading your code and hit reply by mistake. Truly I didn't mean to be offensive, especially when I made the mistake, not you. The forum doesn't allow users to delete their post, so I just wanted to apologize for my mistake. I do wish you well with your project, and, again, I apologize.

No worries, it was my fault. I should've asked you what you meant by it first. <3
 

Mercedes90

Veteran
Veteran
Joined
May 7, 2021
Messages
105
Reaction score
27
First Language
English
Primarily Uses
RMMV
Again, I am not reading the replies.

You have reverted your common event and added back some bad code that you originally took out.

There should be nothing in the Else branches except Jump to Label. The "wrong number" processing should be right at the end of the common event, underneath the Wrong Number label.

Please look carefully at my first example again, and compare with yours.

I made a copy of the Common Event and compared yours to mine and dialed both numbers, and both worked this time. So, no worries. I've added the "bad code" because I didn't know exactly how to expand my Phone Call event.

So, since it works when nothing should be after the Jump to Labels commands, then I'll follow this formula.
So, I'm not going to point any fingers, as to why I removed the Jump to Labels commands because as you said you don't wanna read the replies, but I'd rather wanna continue this conversation peacefully.
 

Shaz

Global Moderators
Global Mod
Joined
Mar 2, 2012
Messages
44,178
Reaction score
15,543
First Language
English
Primarily Uses
RMMV
The first example I gave you should be all that is required. I specifically pointed out which block of code should be duplicated for all the different phone numbers. The Label at the bottom contained all the "wrong number" logic as I assumed you wanted exactly the same thing to happen, regardless of what number was called.

You could have left out the Jump To Label / Label commands and put the "wrong number" code into every Else block (along with an Exit Event Processing), but that meant if you accidentally put the wrong SE in them, or decided you wanted a wait of 500 frames instead of 600, for example, you would have to go back and change every one (and if you had 100 numbers, that'd be a lot of changes). Using those commands simply allows you to put that in a single block of code and make all the wrong numbers go down there. Plus you needed one at the bottom anyway, just in case the player didn't dial any of the right numbers.


So is it all working now? Can this thread be closed?
 

Mercedes90

Veteran
Veteran
Joined
May 7, 2021
Messages
105
Reaction score
27
First Language
English
Primarily Uses
RMMV
So is it all working now? Can this thread be closed?

No, not yet, Shaz. Just gonna fix it first, then I'll get back to you.
 
Last edited:

ATT_Turan

Forewarner of the Black Wind
Veteran
Joined
Jul 2, 2014
Messages
2,805
Reaction score
1,642
First Language
English
Primarily Uses
RMMV
It looks like your code does something like this:
> if (first number) > do stuff : else > wrong number > if (second number)

Sooo, it checks if it's the first number, and if it's not it does the else (wrong number) and never gets to check if it's the second one. You could move the wrong number stuff from the else statements and into a variable check if it's not either of those numbers. Sorry I hope it makes sense!
No, there's a second conditional nested inside that the else is attached to, not the outer one. You're correct about moving the wrong number stuff into a section with labels.

So, I'm not going to point any fingers, as to why I removed the Jump to Labels commands because as you said you don't wanna read the replies, but I'd rather wanna continue this conversation peacefully.
I said you should remove them if you were writing out the code they were supposed to jump to - the purpose of them is to avoid rewriting code repeatedly, which you were doing anyway. And your screenshots were not showing any portion of the event that actually had those labels, so as far as I could see they were erroneous.

I'm glad you got it working the way you want.
 
Last edited:

Mercedes90

Veteran
Veteran
Joined
May 7, 2021
Messages
105
Reaction score
27
First Language
English
Primarily Uses
RMMV
I appreciate it a lot that you all took the time to help me out with this. I'm getting a hang of it now on how to use the Variables and a part of Conditional Branch.
Again, thanks to everyone for your help.
I'm leaving a video here, demonstrating the Phone Call event in the game:
 

slimmmeiske2

Little Red Riding Hood
Global Mod
Joined
Sep 6, 2012
Messages
9,115
Reaction score
5,969
First Language
Dutch
Primarily Uses
RMXP

This thread is being closed, due to being solved. If for some reason you would like this thread re-opened, please report this post and leave a message why. Thank you.

 
Status
Not open for further replies.

Latest Threads

Latest Posts

Latest Profile Posts

My new 49" monitor has been dispatched from the warehouse. Will it arrive tomorrow? The day after? I love that we can track packages now, even if it does only tell me when it's left that end and when it's arrived at the local centre. As long as it doesn't end up in Melbourne again, which has happened before ...
My friend's doing a surprise stream of my game Origin Hunt on Twitch here ! Feel free to stop by :yhappy:
Me, designing it a long time ago: Having an optional boss fight as a random chance to trigger when you fish in a certain spot with a certain type of bait is fun! Cool idea!
Me, trying to playtest everything again: oh god just let me see the boss, my bag is so full of fish!
both love and pain have no boundaries

Forum statistics

Threads
117,219
Messages
1,105,589
Members
153,367
Latest member
icemar
Top