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

@rbxts/matter-sync

v0.4.0

Published

Server-client sync library for Matter ECS

Downloads

22

Readme

matter-sync

Server to client data sync solution for the Matter ECS.

Basic Usage

Client:

const Effect = component("Effect")

addSyncComponent(Effect)

someRemotes.syncPayload.connect((payload) => {
    syncClient(world, payload)
})

someRemotes.hydratePayload.connect((payload) => {
    hydrateClient(world, payload)
})

Server:

// This is supposed to be a system
const result = useSyncPayload(world)
if (!result.isEmpty) {
    someRemotes.syncPayload.fireAll(result.payload)
}

for (const [_, player] of useEvent(Players, Players.PlayerAdded)) {
    const result = getHydratePayload(world)
    if (!result.isEmpty) {
        someRemotes.hydratePayload.fire(play, result.payload)
    }
}

It is important to note that if the module that contains the syncable components was never required by the client, then the client will never be able to get the syncable components data from the server. Consider using nested require solutions in this case.

Behavior

The client will only see the entity if any of it's current components are syncable. That means that there quite often will be the case when the entity is considered to be removed from the client side of view, which will not be the case for the server if this entity has other non-syncable components in it.