A new problem emerges!(New)

ID:264847
 
Dec 15 2010, 6:43 am (Edited on Dec 15 2010, 1:28 pm)
Code:
client/Move(d)
    if(src.controlling)
        step(src.controlling,d)
        return 0
    else if(lock)
        return 0
    else ..()


Problem description:
So it seems to work fine, I can use the verb it lets me control the selected persons movement however they can still control their movement, any ideas?

Dec 15 2010, 10:55 am
Add a 'controlled' var to a mob, and when they're being controlled, trigger it. In the client direction procs, check if their mob is being controlled, and if it is, keep them from moving.
Dec 15 2010, 12:16 pm
In response to Warlord Fred
Why not just use the client.lock variable he already has? When the player is being controlled by someone else, just set src.controlling.client.lock = 1 (or wherever you are initiating your procedure to grant control over another mob).
Dec 15 2010, 1:02 pm
You need to be overriding client/Move(), not mob/Move(). This is a change in how input is handled, not a change in how mobs literally are moved from location to location.
Dec 19 2010, 6:20 am
In response to Garthor
But what if he wants players to be able to control NPCs and not just other players? :\
Dec 19 2010, 2:09 pm
In response to Spunky_Girl
That has nothing to do with anything. To prevent NPCs from moving themselves, you would change their AI procedure to, you know, not make them move.
Dec 19 2010, 2:24 pm
In response to Garthor
Ohhh, I see. My mind was thinking, why not kill two birds with one stone. Or in this case, handle it all by programming it for all mobs rather than just for clients. Didn't think of doing it within the AI. o.O
Dec 23 2010, 9:53 am
In response to CauTi0N
I agree, adding another variable would just be useless.