feat(world): SnapSync config plugin

[Kooshaba]

No description provided.

[holic]

just as a general note, I think this is the first time the mud config has had an option that could effect network code

since we're passing in the mud config to the network config, maybe should just use this key to determine if snap sync should be used?

[holic]

this approach looks like it wouldn't allow for composability of plugins

@dk1a is this how we're expected to create/use plugins?

[dk1a]

this should work well, and it's the approach I use for world the plugin. It just means this plugin can't be used without store and world, and implicitly registers those so you can skip em (or you can still import em).
Here I guess it just looks a bit weird/misleading

[dk1a]

maybe keep import { mudConfig } from "@latticexyz/world/register"; and have snapSync be 2nd?

[dk1a]

a more explicit requirement of world being registered could work instead, but we don't really have a good way to check that atm (plugin ids?)
on the other hand you don't need a good way to check if world plugin is used, you can just check that tables and modules exist

[dk1a]

should the plugin code be in src/ts/plugins, or #584?
modules are more like things that can be created/used by plugins

[alvrs]

for now probably in src/ts/plugins, and later in its own package (or 584)

[Kooshaba]

is there another plugins dir i don't know about or do you just mean one here?

[dk1a]

currently there is no plugins dir at all, I just meant to add one in packages/world/src/ts/plugins (temporarily, until we separate it as its own plugin)