-
Notifications
You must be signed in to change notification settings - Fork 17
Template ‐ FURNITURE
Furniture is anything the player can sit, lie (generally referred to as "recline") or stand on.
The template need to be sent a dictionary, with one or more of "sit", "recline", "stand". This example allows the player (or any NPCs) to sit on it or lie on it.
createItem("settee", FURNITURE({sit:true, recline:true}), {
loc:"dining_room",
examine:"A comfy-looking settee.",
})
By default, USE with furniture defaults to reclining, then sitting if available. Use "useCmd" to modify; for example we might want our settee to default to sitting:
createItem("settee", FURNITURE({sit:true, recline:true, useCmd:"SitOn"}), {
loc:"dining_room",
...
Furniture does not record who is on it; it is done with the characters. The character's "posture" attribute notes his posture, while "postureFurniture" has the furniture he is on. Note that the latter may be undefined
if, say, the player is sitting on the floor. If the player is standing on the floor (i.e., the default state) posture will be undefined
.
Before furniture is used, its "testPostureOn" will be called; if successful "afterPostureOn" is called. This settee will give a comment if the player (or other character) sits or lies on it.
createItem("settee", FURNITURE({sit:true, recline:true}), {
loc:"dining_room",
examine:"A comfy-looking settee.",
afterPostureOn:function(options) {
if (options.posture === "sitting") {
msg("The chair makes a strange noise when {nv:char:sit} on it.", options)
}
else {
msg("The settee makes a strange noise when {nv:char:lie} on it.", options)
}
},
});
More here.
If you want to add further postures, that should be possible, but you would probably be best creating your own template, and extending FURNITURE.
const EXTENDED_FURNITURE = function(options) {
const res = $.extend({}, FURNITURE(options))
if (options.sit) {
res.siton = function(isMultiple, char) {
return this.assumePosture(isMultiple, char, "sitting", 'sit');
};
}
return res
}
You would need to add to the language data (in code.js I suggest), as Quest will try to use lang.sit_on_successful.
lang.sit_on_successful = "{nv:char:sit:true} on {nm:item:the}.",
The posture of the player, and NPCs too, is in an attribute called "posture", and is a string set to one of "standing", "sitting" or "reclining". If the player is sitting or reclining on an item of furniture, then the attribute "postureFurniture" will contain the name of the item.
Tutorial
- First steps
- Rooms and Exits
- Items
- Templates
- Items and rooms again
- More items
- Locks
- Commands
- Complex mechanisms
- Uploading
QuestJS Basics
- General
- Settings
- Attributes for items
- Attributes for rooms
- Attributes for exits
- Naming Items and Rooms
- Restrictions, Messages and Reactions
- Creating objects on the fly
- String Functions
- Random Functions
- Array/List Functions
- The
respond
function - Other Functions
The Text Processor
Commands
- Introduction
- Basic commands (from the tutorial)
- Complex commands
- Example of creating a command (implementing SHOOT GUN AT HENRY)
- More on commands
- Shortcut for commands
- Modifying existing commands
- Custom parser types
- Note on command results
- Meta-Commands
- Neutral language (including alternatives to "you")
- The parser
- Command matching
- Vari-verbs (for verbs that are almost synonyms)
Templates for Items
- Introduction
- Takeable
- Openable
- Container and surface
- Locks and keys
- Wearable
- Furniture
- Button and Switch
- Readable
- Edible
- Vessel (handling liquids)
- Components
- Countable
- Consultable
- Rope
- Construction
- Backscene (walls, etc.)
- Merchandise (including how to create a shop)
- Shiftable (can be pushed from one room to another)
See also:
- Custom templates (and alternatives)
Handing NPCs
- Introduction
- Attributes
- Allowing the player to give commands
- Conversations
- Simple TALK TO
- SAY
- ASK and TELL
- Dynamic conversations with TALK TO
- TALK and DISCUSS
- Following an agenda
- Reactions
- Giving
- Followers
- Visibility
- Changing the player point-of-view
The User Experience (UI)
The main screen
- Basics
- Printing Text Functions
- Special Text Effects
- Output effects (including pausing)
- Hyperlinks
- User Input
The Side Panes
Multi-media (sounds, images, maps, etc.)
- Images
- Sounds
- Youtube Video (Contribution by KV)
- Adding a map
- Node-based maps
- Image-based maps
- Hex maps
- Adding a playing board
- Roulette!... in a grid
Dialogue boxes
- Character Creation
- Other example dialogs [See also "User Input"]
Other Elements
- Toolbar (status bar across the top)
- Custom UI Elements
Role-playing Games
- Introduction
- Getting started
- Items
- Characters (and Monsters!)
- Spawning Monsters and Items)
- Systema Naturae
- Who, When and How NPCs Attack
- Attributes for characters
- Attacking and guarding
- Communicating monsters
- Skills and Spells
- Limiting Magic
- Effects
- The Attack Object
- [Extra utility functions](https://github.com/ThePix/QuestJS/wiki/RPG-Library-%E2%80%90-Extra Functions)
- Randomly Generated Dungeon
- Quests for Quest
- User Interface
Web Basics
- HTML (the basic elements of a web page)
- CSS (how to style web pages)
- SVG (scalable vector graphics)
- Colours
- JavaScript
- Regular Expressions
How-to
Time
- Events (and Turnscripts)
- Date and Time (including custom calendars)
- Timed Events (i.e., real time, not game time)
Items
- Phone a Friend
- Using the USE verb
- Display Verbs
- Change Listeners
- Ensembles (grouping items)
- How to spit
Locations
- Large, open areas
- Region,s with sky, walls, etc.
- Dynamic Room Descriptions
- Transit system (lifts/elevators, buses, trains, simple vehicles)
- Rooms split into multiple locations
- Create rooms on the fly
- Handling weather
Exits
- Alternative Directions (eg, port and starboard)
- Destinations, Not Directions
Meta
- Customise Help
- Provide hints
- Include Achievements
- Add comments to your code
-
End The Game (
io.finish
)
Meta: About The Whole Game
- Translate from Quest 5
- Authoring Several Games at Once
- Chaining Several Games Together
- Competition Entry
- Walk-throughs
- Unit testing
- Debugging (trouble-shooting)
Releasing Your Game
Reference
- The Language File
- List of settings
- Scope
- The Output Queue
- Security
- Implementation notes (initialisation order, data structures)
- Files
- Code guidelines
- Save/load
- UNDO
- The editor
- The Cloak of Darkness
- Versions
- Quest 6 or QuestJS
- The other Folders
- Choose your own adventure