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 🙏

© 2025 – Pkg Stats / Ryan Hefner

@antivivi/jjt-difficulties

v1.3.0

Published

Dumbest package

Downloads

12

Readme

@antivivi/jjt-difficulties

A library for managing and interacting with a collection of custom difficulties for a game or application. This package provides a structured way to define, organize, and retrieve difficulty levels, complete with metadata such as names, images, colors, and ratings.

Installation

Install the package via npm:

npm install @antivivi/jjt-difficulties

Do ensure to properly configure the @antivivi organization.

  1. Rojo project configuration should include @antivivi in rbxts_include:
"rbxts_include": {
    "$path": "include",
    "node_modules": {
        "$className": "Folder",
        "@rbxts": {
            "$path": "node_modules/@rbxts"
        },
        "@antivivi": {
            "$path": "node_modules/@antivivi"
        }
    }
}
  1. tsconfig.json should include @antivivi in typeRoots.
"typeRoots": [
    "node_modules/@rbxts",
    "node_modules/@antivivi"
]

Usage

Importing the Library

import Difficulty from "@antivivi/jjt-difficulties";

Accessing Predefined Difficulties

You can access predefined difficulties directly as static properties of the Difficulty class:

const firstDifficulty = Difficulty.TheFirstDifficulty;
console.log(firstDifficulty.name); // "The First Difficulty"
console.log(firstDifficulty.rating); // -10000010

Retrieving Difficulties by ID

Use the get method to retrieve a difficulty by its unique ID:

const difficulty = Difficulty.get("TheLowerGap");
if (difficulty) {
    console.log(difficulty.name); // "The Lower Gap"
}

Creating Custom Difficulties

You can create custom difficulties by chaining the provided methods:

const customDifficulty = new Difficulty()
    .setName("Custom Difficulty")
    .setImage(1234567890)
    .setColor(Color3.fromRGB(255, 0, 0))
    .setRating(42)
    .setClass(1);
const id = "CustomDifficulty";
Difficulty.set(id, customDifficulty);

Development

Prerequisites

  • Node.js
  • npm
  • Roblox TypeScript (roblox-ts)

Setup

  1. Clone the repository:
git clone https://github.com/evilbocchi/jjt-difficulties.git
cd jjt-difficulties
  1. Install dependencies
npm install
  1. Build the project:
npm run build

Contributing

Contributions are welcome! Please follow these steps:

  1. Fork the repository.
  2. Create a new branch for your feature or bugfix.
  3. Commit your changes and push the branch.
  4. Open a pull request.

License

This project is licensed under the ISC License. See the LICENSE file for details.