MUD
/mud117
mud.dev - a framework for building ambitious onchain applications
tons of good first issues to grab in MUD repo! https://github.com/latticexyz/mud/issues?q=is%3Aissue+is%3Aopen+label%3A%22good+first+issue%22
if you like space MMOs, modding, and want an excuse to try out MUD, I have good news
https://x.com/mud_dev/status/1834236841324855349
https://x.com/mud_dev/status/1834236841324855349
A little peek into some tricky cross-origin communication stuff we're doing to enable better observability for MUD apps: https://x.com/frolic/status/1833915569135108424
488
frolic
@frolic·09:58 07/08/2024
since MUD v2, a huge percentage of my engineering time is now spent on "how do we make this backwards compatible"
deep respect for teams like React for their work in easy upgrade paths
deep respect for teams like React for their work in easy upgrade paths
multiple namespace support has landed in MUD: https://github.com/latticexyz/mud/pull/2968
v2.1 release and announcement soon!
v2.1 release and announcement soon!
a more powerful successor to /mud's dev tools is coming sooooon
https://x.com/karooolis/status/1816850849886249241
https://x.com/karooolis/status/1816850849886249241
MUD config supports "shorthands" for defining things like tables.
This makes it easier for games that use the ECS pattern to define tables that only have one field.
This makes it easier for games that use the ECS pattern to define tables that only have one field.
we realized in MUD that creating a new project from an existing world using onchain data isn't as nice as it could be because the chain is still missing some data
specifically resource names, like tables and systems and namespaces, only exist inside resource IDs
specifically resource names, like tables and systems and namespaces, only exist inside resource IDs
_finally_ ditched all of the old MUD config code and compatibility layers! goodbye zod 👋
this clears the path towards expanding the config with support for multiple namespaces - stay tuned!
this clears the path towards expanding the config with support for multiple namespaces - stay tuned!
the MUD team is back from a short break and ready to rock!
next up is supporting multiple namespaces in your app, making it easier to build upon worlds
next up is supporting multiple namespaces in your app, making it easier to build upon worlds
Any fun onchain games to play this coming week?
no launcher downloading, no new wallet set up, just plain & simple & fun onchain games anyone?
no launcher downloading, no new wallet set up, just plain & simple & fun onchain games anyone?
488
frolic
@frolic·12:31 31/05/2024
the /mud team is hiring senior engineers!
we're making it wayyy easier to build onchain apps/games and there's a ton of fun stuff to work on
if that sounds interesting, let's chat!
we're making it wayyy easier to build onchain apps/games and there's a ton of fun stuff to work on
if that sounds interesting, let's chat!
This is a classic problem that Tevm makes pretty simple to solve
340666
t11s
@!340666·00:52 23/03/2024
An abstraction provided by the MUD sdk to simulate mutating calls generically and reindex + return the resulting table state would solve this, but seems fairly high complexity unfortunately.
Some exciting new MUD CLI in latest 2.0.7 release:
https://github.com/latticexyz/mud/blob/main/packages/cli/CHANGELOG.md
- Deploy a MUD world with an upgradeable world implementation
- Deploy a MUD world using an AWS KMS key signer
- Verify your MUD world with `mud verify`
https://github.com/latticexyz/mud/blob/main/packages/cli/CHANGELOG.md
- Deploy a MUD world with an upgradeable world implementation
- Deploy a MUD world using an AWS KMS key signer
- Verify your MUD world with `mud verify`
how much would you hate us if we changed field names from string to bytes32?
mud.dev/config
https://mud.dev/changelog#version-200-next18
As for the upgrade of MUD from v2.0.0-NEXT.17 to v2.0.0-NEXT.18 or latest(v2.0.1), migration was necessary
https://mud.dev/changelog#version-200-next18
As for the upgrade of MUD from v2.0.0-NEXT.17 to v2.0.0-NEXT.18 or latest(v2.0.1), migration was necessary
