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

dark-forest-game

v0.8.2

Published

Dark Forest board game logic

Downloads

93

Readme

Version Tests Coverage Downloads License

Dark Forest Game Logic Library

This is a state engine for playing a game of Dark Forest. I'm working on a UI for this, but at a minimal level every client and player should agree on the rules expressed by these state transforms. Keeping state-transition logic separate from UI should also make it simpler to build an offline trainer algorithm to develop a model to play the game against.

Each game state should start out with a state

import { initialState, GameState } from 'dark-forest-game'

const s0: GameState = initialState

initialState is the root game state that all games begin from. From here, any number of moves can be done, and the proper order of which is specified by the game itself, but it must conform to this flow, where any given string will process into another GameState.

import { reducer, GameState } from 'dark-forest-game'

const s1 = reducer(s0, ['START', 10]) as GameState
// create player 0 at sol 8
const s2 = reducer(s1, ['SPAWN', 0, 8]) as GameState
// create player 1 at sol 4
const s2 = reducer(s1, ['SPAWN', 1, 4]) as GameState
  • completion - a list of strings which could be the prefix of the next command from the user.
  • partial - The current list of params for the current move. "" is included in this list, then the current partial command could be sent as-is. If this list is empty, the given partial command is invalid.