npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

hyperfy-dialog

v1.0.4

Published

This schema defines the structure for creating a dialog flow in a text-based game. The conversation is broken down into a series of views, with each view containing a main text box and options for the player to choose from.

Downloads

6

Readme

Hyperfy Schema for Dialog Flow

This schema defines the structure for creating a dialog flow in a text-based game. The conversation is broken down into a series of views, with each view containing a main text box and options for the player to choose from.

Schema Definition

Schema = {
  id: String
  origin: String
  views: {
    [name]: View
  }
}

Schema Fields

  • id: A unique identifier for the dialog flow. This can be used to store and retrieve the conversation history for a particular NPC or character.
  • origin: The name of the view that the conversation should start from. views: An object containing all the views in the conversation flow, where each view is identified by a unique name.

View Definition

View = {
  text: String
  event: String
  origin: String
  goto: String
  options: [...Option]
}

View Fields

  • text: The text to display in the main box of the view. Note that space is limited, so the text should be concise and to the point.
  • event: The event to emit when this view is shown. This can be used to trigger custom logic or actions when the view is displayed.
  • origin: The name of the view that the player will return to if they leave the conversation and come back later.
  • goto: The name of the next view to go to when the player clicks on the dialog box. This is usually set to the name of the next view in the conversation flow.
  • options: An array of options that the player can choose from. Each option is defined using the Option schema.

Option Definition

Option = {
  require: String
  text: String
  event: String
  origin: String
  goto: String
}

Option Fields

  • require: An optional key that is needed to show this option. This can be used to conditionally show or hide options based on the state of the game or the player's choices.
  • text: The text to display on the button for this option. Again, space is limited, so keep the text short and to the point.
  • event: The event to emit when the player clicks on this option. This can be used to trigger custom logic or actions.
  • origin: The name of the view that the player will return to if they leave the conversation and come back later.
  • goto: The name of the next view to go to when the player clicks on this option. This is usually set to the name of the next view in the