Swimming delay
Posted: Wed Mar 02, 2011 12:50 pm
Ok, I am sure this has probably been covered elsewhere, but I can't find it or figure out how to fix it. When I use the mapper to speed walk into a room you would have to swim too, it keeps triggerring off "There's water ahead of you. You'll have to swim in that direction to make it through." and spamming the "swim dir" command over and over with the effect that I never swim anywhere. At first I thought that just adding a delay to it would be sufficient, then I recalled that that delay needed would vary based on network latency. Is there away to have it trigger the swim command once, and then wait until it receives the new %gmcp.room.info to send the next command?
Actually, in general is there a way to make it check for that before it moves every time? Not sure if that would be desirable or not, but I can't see why not. Hell, even just having the option would be nice. I am not certain if there is a new config xml file for the mapper floating around. I downloaded on that was linked here on the forums, but it seems pretty dated. I am using the Mudlet 2.0 though, so I don't think that is the issue.
Actually, in general is there a way to make it check for that before it moves every time? Not sure if that would be desirable or not, but I can't see why not. Hell, even just having the option would be nice. I am not certain if there is a new config xml file for the mapper floating around. I downloaded on that was linked here on the forums, but it seems pretty dated. I am using the Mudlet 2.0 though, so I don't think that is the issue.