search

scrom / Experiments

a NodeJS text adventure - deliberately coded badly to re-experience the pain of legacy code
http://mvta.herokuapp.com/
2 stars 0 forks source link

support custom wording around hidden exits #139

Open scrom opened 10 years ago

scrom commented 10 years ago

allow exits to carry their own descriptions and for these to be different depending on whether they're hidden or not. The description isn't mandatory.

scrom commented 9 years ago

Hidden exits from objects other than doors are in progress - they'll be a precursor to this.

scrom commented 9 years ago

an exit now has a "description". if a player "go"'s through an exit with a custom description, they'll get that added to the status.

we don't yet had custom wording for "discovering" an exit.

scrom commented 9 years ago

Hidden exits from non-doors now work - use the usual "search" type activities to find a hidden exit.

scrom commented 9 years ago

using any exit (hidden or not) will now return an optional exit description.

scrom commented 9 years ago

in order to get more than this, we'll need a "showDescription" and a "hideDescription" (both applied to the exit, not the owning object I think).

This is probably the point we need to start adding "attributes" to the exit constructor interface rather than manually adding even more parameters.