ID:1767725
![]() Jan 21 2015, 3:27 pm (Edited on Apr 14 2020, 8:01 pm)
|
|||||||||||||
Resolved
| |||||||||||||
.
|
Sounds to me like the issue is with your macros and movement, rather than alert(). Since I won't be able to get to this right away, I think you need to put in some debugging to narrow down what the actual problem is. Take a look at when your movement routines are being called (and how) in DS and in the webclient, and when Bump() is called.
Again, the webclient will have zero impact on Bump() directly, but it could have an impact on how movement keys in your game are interpreted. Even then, the webclient has been tested quite a lot with macros in many different projects, so I wonder if your movement system is doing something different than most others I've seen. |
Cloud Magic wrote:
There isn't an issue with my macros, I have customized macros that work properly in Dream Maker but improperly in the Web Client. My Macros are set so that when I hold Two things: First, Dream Maker is the editor; Dream Seeker plays the games. Second, I don't really follow what you're saying about the arrow keys. Is your movement system setup so that you press North and East independently and it combines to move northeast? The error is that when bump is called it goes into a loop. That's what it is outputting when I bump into the mob. That's what I was trying to tell you to test out, walk the mob into the green NPC and see that Bump() is called not once but endless times. Then run it in Dream Maker, it will only be called once. A .dmi file is an icon file, not code; that's .dm. The webclient has been tested with FA's lib, but when I can I'll take a look and see what's going on in your code. Offhand, I'm wondering if maybe the problem is that the key is not registering as having released. This is something you should be able to test on your own before I check it out. |
I did take a quick look at your code, and from the looks of it I think I'm right about my hunch. This has nothing to do with alert(), and everything to do with macros. I still recommend you add debugging so you can see if the keys have been properly released or not, because that's the place to look.
|
Cloud Magic wrote:
But why would this bug only occur in the web client? Is something wrong with macros in 5.7 possibly? There's almost certainly a bug involved. My concern is narrowing down the actual cause. I believe the true cause is that when an alert appears--or probably any other prompt--key releases aren't registering properly. I know DS can clear the key map outright; JavaScript doesn't have the option of checking the current key-down state, but it still should be able to register the key-up. I added debugs lummox so you can observe what the issue is because I'm not finding it exactly, it looks like when movement keys are called and I bump the NPC mob, the bump output is still being outputted tons of times. I would recommend also adding output for when a key is released. I'll need to do that when I get to looking at this issue anyway (I'm on site work for the moment), but if you can confirm my theory it would help a lot. If I'm wasting your time, terribly sorry. Nope, you're not. I don't have time to get to this right away so I'm just hoping we can get more specific info so I'll know better where to look when the time comes. |
I don't use a @byond.com email address. My address is [email protected], so you should resend the file there.
I strongly recommend however that you isolate alert() to tell if it's the issue directly or not. Using the webclient will not make any difference when it comes to Bump() behavior, which is strictly server-side.