PushTravelerclass | travel.t[3314], en_us.t[2842] |
Superclass Tree | Subclass Tree | Global Objects | Property Summary | Method Summary | Property Details | Method Details |
For the most part, we refer Traveler methods to the underlying Traveler. We override a few methods to provide special handling.
Modified in en_us.t[2842]:
English-specific PushTraveler changes
class
PushTraveler : object
canTravelVia
construct
explainNoTravelVia
propNotDefined
travelerName
travelerTravelTo
travelerTravelWithin
obj_ | travel.t[3323] |
traveler_ | travel.t[3329] |
canTravelVia (connector, dest) | travel.t[3400] |
construct (obj, traveler) | travel.t[3315] |
explainNoTravelVia (connector, dest) | travel.t[3412] |
propNotDefined (prop, [args]) | travel.t[3421] |
travelerName (arriving) | en_us.t[2848] |
travelerTravelTo (dest, connector, backConnector) | travel.t[3337] |
travelerTravelWithin (actor, dest) | travel.t[3389] |
To allow pushing an object between nested rooms, override this in parallel with travelerTravelTo(). Note that you'll have to call travelerTravelWithin() on the underlying traveler (which will generally be the actor), and you'll probably want to set up a new set of notifiers parallel to beforeMovePushable() and movePushable(). You'll probably particularly need to customize the report in your parallel for movePushable() - the default ("you push x into the area") isn't very good when nested rooms are involved, and you'll probably want something more specific.