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

n3d-gamecore

v0.0.3-alpha

Published

3D multiplayer core functionality game engine component.

Downloads

18

Readme

n3d-gamecore (0.0.0-alpha1)

checkout the 'dev' branch for the most recent build, the codebase is considered ALPHA quality only, should be OK to use but is 'unstable' because the API will probably change without notice. If you pull updates from 'dev' branch and it breaks your code, its on you, thats your warning. Use at own risk.

You need will also need to have the Three.js library installed wherever you are hosting the server because it is not bundled with this component. See the website for more info.

####3D WebGL Multi-Player Game Engine (Node.js / Three.js / HTML5) Node.js websockets application that provides core functionality of a 3D multi-player game engine, most of the original 2D code remains, it has been re-purposed to provide the player mini-map overhead view, the client and server messaging subsystem implements client prediction and responds to client input with authoritative server update packets using socket.io (Express is included but its only doing basic routing to serve the 'public/' folder files at the moment) and all of the 3D scene rendering in the browser is provided by Three.js, all connected clients will need to be running a modern WebGL/HTML5 compatible browser (such as Chrome or Firefox)

This is not a fully functional game, it is intended to be a scalable realtime massively multi-player component to incorporate into your game project, my goal is to support up to 512k concurrent connections (at a future stage of the project). The concept will be to keep this core component as lean and efficient as possible without adding many additional features (i.e. sophisticated collision physics) but to also include a stable API so that those extra features can easily be provided by other Node.js modules.

Change history

Realtime Multiplayer In HTML5

Read the article here : http://buildnewgames.com/real-time-multiplayer/

Getting started (Using npm package.json)

  • Get node.js
  • run npm install inside the cloned folder
  • run node app.js inside the cloned folder
  • Visit http://localhost:8000/?debug

Getting started (Manual install)

  • Get node.js
  • Install socket.io npm install socket.io
  • Install node-udid npm install node-uuid
  • Install express npm install express
  • Run node app.js inside the cloned folder
  • Visit http://localhost:8000/?debug

MIT Licensed.