Reply to Re: Weird issue with screenlocks.
If you don't have an account, just leave the password field blank.
Add a wait(1) at the top and it should work. Currently, the script runs before Dink's coordinates are updated for the new screen, so his Y will be what it was on the bottom of the above screen (something like 401). Same thing with X, it's gonna be 620+ on the left side of the screen, and below zero on the right side.
That actually works without the wait(1); command. But just tried it and it doesn't fix this problem. I think you might've misunderstood the issue. It's that if you come from either the right or the left screen, the script somehow reverses itself. If I want the screenlock to appear when I enter the screen above its halfway point, and not when I enter below its halfway point, it'll work just fine entering from the above and the below screens. However, if I enter from the left- or the right-side screen, the screenlock will now appear if I enter below the halfway point, but not if I enter above it.
Actually, now that I looked at it, the reversal only seems to happen entering from the right-side screen. Entering from the left-side screen will cause screenlock no matter what Y position you'll enter. Not sure if this is just some weird issue only I'm running into, or if it's actually a real fault from the original game.
EDIT: Nevermind. You were right, Scratcher. I literally did nothing different this time, and the wait(1); command suddenly started working. Also fixed the whole "greater than"/"lesser than" problem, which hadn't crossed my mind for some reason. Weird how it didn't work at first. Thanks for solving this mystery for me.
That actually works without the wait(1); command. But just tried it and it doesn't fix this problem. I think you might've misunderstood the issue. It's that if you come from either the right or the left screen, the script somehow reverses itself. If I want the screenlock to appear when I enter the screen above its halfway point, and not when I enter below its halfway point, it'll work just fine entering from the above and the below screens. However, if I enter from the left- or the right-side screen, the screenlock will now appear if I enter below the halfway point, but not if I enter above it.
Actually, now that I looked at it, the reversal only seems to happen entering from the right-side screen. Entering from the left-side screen will cause screenlock no matter what Y position you'll enter. Not sure if this is just some weird issue only I'm running into, or if it's actually a real fault from the original game.
EDIT: Nevermind. You were right, Scratcher. I literally did nothing different this time, and the wait(1); command suddenly started working. Also fixed the whole "greater than"/"lesser than" problem, which hadn't crossed my mind for some reason. Weird how it didn't work at first. Thanks for solving this mystery for me.
