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

@chromeq/age

v2.3.0

Published

Abstract Gamification Engine

Downloads

109

Readme

AGE -- Abstract Gamification Engine.

This is a rewrite of rodw/age from coffeescript to TypeScript. Mostly it is the same but with some notable changes:

  1. Renamed all methods from snake_case to camelCase
  2. Achievement Rules are evaluated on event received rather than on getPlayerAchievements
  3. Achieved Achievements are also added to the player.history
  4. Transient rules are not yet implemented (TODO coming soon)
  5. Events are now an object with a name and optional <T>data
  6. History entries are objects with a timestamp Date, and Achievements are also added to player.history and have an achieved Date
  7. Methods return values rather than replying in Node style callbacks with errors

Installation

npm install @chromeq/age

# or
yarn add @chromeq/age

Examples

For a detailed example of how to use the AGE framework, visit the base project example docs.

Usage

Clients must:

  1. Initialise the GameEngine and register players. Further Docs
import { GameEngine } from '@chromeq/age';

// Create a new instance of the gamification engine
const engine = new GameEngine();

// Register the "player" -- any object that contains at least an `id`
const player = { id: 123 };
engine.addPlayer(player);
  1. Define achievement rules which define conditions that players must meet in order to earn the corresponding achievement. Further Docs
const rule = new AchievementRule({
    key: 'SessionCount',
    multiplicity: 1,
    transient: false,
    predicate: (player, engine) => {
        return sessionCount > 3; // Any logic required to evaluate to `boolean`
    },
});

// Add the achievemt rule to the engine -- Can also be defined first and provided to the GameEngine constructor
engine.addAchievementRule(rule);
  1. Publish events that represent actions or events that add to a player's event history.
// Add an event that happens -- Also has alias `trigger`, `triggerEvent`, `dispatch` or `dispatchEvent`
engine.addEvent(player, 'SessionCount'); // TODO: Add extra data to the event
  1. Subscribe to events or achievements
// Subscribe to `'achievement-achieved'` or `'event-occurred'` -- Also has alias `listen`, `addListner` or `addEventListner`

engine.on('event-occurred', (player, event) => {
    // Useful to "chain" events and you can call `engine.addEvent` again here
    console.log('EVENT OCCURRED', player, event);
});

engine.on('achievement-achieved', (player, achievement) => {
    // Congrats 🎉 - Show the appropriate UI or save state
    console.log('ACHIEVEMENT ACHIEVED', player, achievement);
});