shoes

Var Details

can_be_tied

Whether these shoes have laces that can be tied/untied

lace_time

How long it takes to lace/unlace these shoes

our_alert

any alerts we have active

tied

Are we currently tied? Can either be SHOES_UNTIED, SHOES_TIED, or SHOES_KNOTTED

Proc Details

adjust_laces

adjust_laces adjusts whether our shoes (assuming they can_be_tied) and tied, untied, or knotted

In addition to setting the state, it will deal with getting rid of alerts if they exist, as well as registering and unregistering the stepping signals

Arguments:

• state: SHOES_UNTIED, SHOES_TIED, or SHOES_KNOTTED, depending on what you want them to become
• user: used to check to see if we're the ones unknotting our own laces

check_trip

check_trip runs on each step to see if we fall over as a result of our lace status. Knotted laces are a guaranteed trip, while untied shoes are just a chance to stumble

handle_tying

handle_tying deals with all the actual tying/untying/knotting, inferring your intent from who you are in relation to the state of the laces

If you're the wearer, you want them to move towards tied-ness (knotted -> untied -> tied). If you're not, you're pranking them, so you're moving towards knotted-ness (tied -> untied -> knotted)

Arguments:

• user: who is the person interacting with the shoes?

still_shoed

our_guy here is the wearer, if one exists (and he must exist, or we don't care) checking to make sure we're still on the person we're supposed to be, for lacing do_after's